Palo Alto Networks · OpenAPI Overlay 1.0.0
API Evangelist conversational phrasing for Palo Alto Networks Users API
20 actions
20 updates
phrasing
extends
openapi/palo-alto-networks-users-api-openapi.yml
Generated by API Evangelist
Written by API Evangelist tooling for Palo Alto Networks's API. It is a proposal applied on top of the contract, not a document Palo Alto Networks publishes.
What the actions change
x-apievangelist-phrasing
Targets 20 · first 16 shown; the file carries all of them
$.info
$.paths['/seb-api/v1/users'].get
$.paths['/seb-api/v1/users/{id}'].get
$.paths['/seb-api/v1/users/suspend'].post
$.paths['/seb-api/v1/users/resume'].post
$.paths['/seb-api/v1/users/force-reauth'].post
$.paths['/api/v34.03/users'].get
$.paths['/api/v34.03/users'].put
$.paths['/api/v34.03/users'].post
$.paths['/api/v34.03/users/password'].put
$.paths['/api/v34.03/users/{id}'].delete
$.paths['/api/v34.04/users'].get
$.paths['/api/v34.04/users'].put
$.paths['/api/v34.04/users'].post
$.paths['/api/v34.04/users/password'].put
$.paths['/api/v34.04/users/{id}'].delete
OpenAPI Overlay
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
title: API Evangelist conversational phrasing for Palo Alto Networks Users API
version: 1.0.0
extends: openapi/palo-alto-networks-users-api-openapi.yml
actions:
- target: $.info
update:
x-apievangelist-phrasing:
method: generated
generated: '2026-09-26'
generator: build-phrasing.py
label: Generated by API Evangelist
operations: 19
- target: $.paths['/seb-api/v1/users'].get
update:
x-apievangelist-phrasing:
intent: List Prisma Browser users with filters
effect: read
questions:
- Which Prisma Browser users are currently suspended?
- Can I find browser users by email or by when they were last seen?
- Is it possible to include deleted users when listing Prisma Browser users?
instructions:
- text: List Prisma Browser users with status {status}.
slots:
status: query.user.status
- text: Find the Prisma Browser user whose email is {email}.
slots:
email: query.user.email
- text: Show Prisma Browser users first seen on or after {first_seen}, including deleted ones.
slots:
first_seen: query.user.first_seen_gte
method: generated
generated: '2026-09-26'
- target: $.paths['/seb-api/v1/users/{id}'].get
update:
x-apievangelist-phrasing:
intent: Get one Prisma Browser user by ID
effect: read
questions:
- How do I look up the details of a single Prisma Browser user by their ID?
- What does the Prisma Browser record for one specific user contain?
instructions:
- text: Get the Prisma Browser user with ID {id}.
slots:
id: path.id
- text: Show me the browser user profile for user {id}.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/seb-api/v1/users/suspend'].post
update:
x-apievangelist-phrasing:
intent: Suspend Prisma Browser users
effect: destructive
questions:
- How do I cut off a user's access to Prisma Browser on all their devices?
- Can I suspend several browser users at once?
instructions:
- text: Suspend Prisma Browser users {userIds}.
slots:
userIds: requestBody.userIds
- text: Block browser access for user {userIds} on every device by suspending them.
slots:
userIds: requestBody.userIds
method: generated
generated: '2026-09-26'
- target: $.paths['/seb-api/v1/users/resume'].post
update:
x-apievangelist-phrasing:
intent: Reactivate suspended Prisma Browser users
effect: write
questions:
- How can I give a suspended user their Prisma Browser access back?
- Can I reactivate multiple suspended browser users in one call?
instructions:
- text: Resume the suspended Prisma Browser users {userIds}.
slots:
userIds: requestBody.userIds
- text: Restore browser access for suspended user {userIds}.
slots:
userIds: requestBody.userIds
method: generated
generated: '2026-09-26'
- target: $.paths['/seb-api/v1/users/force-reauth'].post
update:
x-apievangelist-phrasing:
intent: Force users to re-authenticate in the browser
effect: write
questions:
- Can I make a user sign in to Prisma Browser again on all of their devices?
- What happens to active browser sessions when I force re-authentication?
instructions:
- text: Force re-authentication in Prisma Browser for users {userIds}.
slots:
userIds: requestBody.userIds
- text: Make user {userIds} log in to the browser again on every active device.
slots:
userIds: requestBody.userIds
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.03/users'].get
update:
x-apievangelist-phrasing:
intent: List Compute console users (v34.03 API)
effect: read
questions:
- Which console users exist in Prisma Cloud Compute on the v34.03 API?
- How do I get all Compute users with the older v34.03 endpoint?
instructions:
- text: List all Compute console users using the v34.03 API.
- text: Show me every user and role in Compute via the v34.03 users endpoint.
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.03/users'].put
update:
x-apievangelist-phrasing:
intent: Update a Compute console user (v34.03 API)
effect: write
questions:
- Can I change a Compute user's role through the v34.03 API?
- How do I edit an existing console user's permissions on v34.03?
instructions:
- text: Using v34.03, change the role of Compute user {username} to {role}.
slots:
username: requestBody.username
role: requestBody.role
- text: Update the description of Compute user {username} to {description} with the v34.03 API.
slots:
username: requestBody.username
description: requestBody.description
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.03/users'].post
update:
x-apievangelist-phrasing:
intent: Add a Compute console user (v34.03 API)
effect: write
questions:
- How do I create a new Compute console user with the v34.03 API?
- Which auth types can a new user have when added on v34.03?
instructions:
- text: Add Compute user {username} with role {role} via the v34.03 API.
slots:
username: requestBody.username
role: requestBody.role
- text: Create a v34.03 Compute user {username} using auth type {authType}.
slots:
username: requestBody.username
authType: requestBody.authType
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.03/users/password'].put
update:
x-apievangelist-phrasing:
intent: Change my Compute password (v34.03 API)
effect: write
questions:
- Can I change my Compute console password through the v34.03 API?
- Does the v34.03 password change require my old password?
instructions:
- text: Change my Compute password from {oldPassword} to {newPassword} using v34.03.
slots:
oldPassword: requestBody.oldPassword
newPassword: requestBody.newPassword
- text: Set a new Compute console password {newPassword} via the v34.03 endpoint.
slots:
newPassword: requestBody.newPassword
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.03/users/{id}'].delete
update:
x-apievangelist-phrasing:
intent: Delete a Compute console user (v34.03 API)
effect: destructive
questions:
- How do I remove a console user from Compute with the v34.03 API?
- Can a deleted v34.03 Compute user be recovered?
instructions:
- text: Delete Compute user {id} using the v34.03 API.
slots:
id: path.id
- text: Remove console user {id} from Compute through the v34.03 endpoint.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.04/users'].get
update:
x-apievangelist-phrasing:
intent: List Compute console users (v34.04 API)
effect: read
questions:
- Which users have access to the Compute console on the current v34.04 API?
- Can I pull the full Compute user list from the v34.04 endpoint?
instructions:
- text: List all Compute console users with the v34.04 API.
- text: Show every Compute user and role from the v34.04 users endpoint.
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.04/users'].put
update:
x-apievangelist-phrasing:
intent: Update a Compute console user (v34.04 API)
effect: write
questions:
- How do I change an existing Compute user's permissions on v34.04?
- Can I switch a Compute user's auth type with the v34.04 API?
instructions:
- text: With v34.04, set the role of Compute user {username} to {role}.
slots:
username: requestBody.username
role: requestBody.role
- text: Update Compute user {username} to auth type {authType} on the v34.04 API.
slots:
username: requestBody.username
authType: requestBody.authType
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.04/users'].post
update:
x-apievangelist-phrasing:
intent: Add a Compute console user (v34.04 API)
effect: write
questions:
- Can I add a new console user to Compute with the v34.04 API?
- What role and permissions can I give a user I create on v34.04?
instructions:
- text: Create Compute user {username} with role {role} on the v34.04 API.
slots:
username: requestBody.username
role: requestBody.role
- text: Add v34.04 Compute user {username} with password {password}.
slots:
username: requestBody.username
password: requestBody.password
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.04/users/password'].put
update:
x-apievangelist-phrasing:
intent: Change my Compute password (v34.04 API)
effect: write
questions:
- How can I rotate my Compute console password on the v34.04 API?
- Is my current password needed to set a new one in v34.04?
instructions:
- text: Change my Compute password from {oldPassword} to {newPassword} with v34.04.
slots:
oldPassword: requestBody.oldPassword
newPassword: requestBody.newPassword
- text: Update my console password to {newPassword} using the v34.04 password endpoint.
slots:
newPassword: requestBody.newPassword
method: generated
generated: '2026-09-26'
- target: $.paths['/api/v34.04/users/{id}'].delete
update:
x-apievangelist-phrasing:
intent: Delete a Compute console user (v34.04 API)
effect: destructive
questions:
- Can I delete a Compute console user through the v34.04 API?
- What happens to a user's console access after deleting them on v34.04?
instructions:
- text: Delete Compute user {id} with the v34.04 API.
slots:
id: path.id
- text: Remove console user {id} from Compute via the v34.04 endpoint.
slots:
id: path.id
method: generated
generated: '2026-09-26'
- target: $.paths['/v1/users'].get
update:
x-apievangelist-phrasing:
intent: List users enrolled in Prisma Access Browser
effect: read
questions:
- Who is enrolled in Prisma Access Browser and which policy is each assigned?
- How many active sessions does each enrolled browser user have?
- Can I list only the enrolled browser users assigned to a given policy?
instructions:
- text: List Prisma Access Browser users assigned to policy {policy_id}.
slots:
policy_id: query.policy_id
- text: Show the first {limit} enrolled Prisma Access Browser users with their session counts.
slots:
limit: query.limit
method: generated
generated: '2026-09-26'
- target: $.paths['/v1/users/{user_id}/sessions'].get
update:
x-apievangelist-phrasing:
intent: Get a user's Prisma Access Browser sessions
effect: read
questions:
- What devices and IP addresses has a given user browsed from recently?
- Can I see only the active browser sessions for one user?
instructions:
- text: Show the browser sessions for user {user_id}.
slots:
user_id: path.user_id
- text: List {status} Prisma Access Browser sessions for user {user_id}.
slots:
status: query.status
user_id: path.user_id
method: generated
generated: '2026-09-26'
- target: $.paths['/api/users'].get
update:
x-apievangelist-phrasing:
intent: List users discovered across SaaS apps
effect: read
questions:
- Which user accounts has SaaS Security discovered in my connected apps?
- Can I see only the users of one connected SaaS application?
instructions:
- text: List SaaS users discovered in connected app {app_id}.
slots:
app_id: query.app_id
- text: Show all user accounts found across my connected SaaS applications.
method: generated
generated: '2026-09-26'
- target: $.paths['/api/user/{id}/activities'].get
update:
x-apievangelist-phrasing:
intent: Get a user's activity across SaaS apps
effect: read
questions:
- What files did a particular user share or touch in our SaaS apps?
- Can I pull a user's SaaS login and sharing events for a date range?
instructions:
- text: Show SaaS activity for user {id} between {start_date} and {end_date}.
slots:
id: path.id
start_date: query.start_date
end_date: query.end_date
- text: List user {id}'s activity in connected app {app_id}.
slots:
id: path.id
app_id: query.app_id
method: generated
generated: '2026-09-26'