Nfon queue-profiles API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearer_auth).
bearer_auth — JSON Web Token
Paths & Operations 7
Across 5 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are QueueProfile (5 properties), GetQueueProfilesExtensionResponse (5 properties), Error (4 properties), QueueProfilePatchRequest (4 properties). Each schema is shown below with its type and property counts.
Error
object
Error represents the standard API error response.
4 properties
ErrorDetail
object
ErrorDetail represents error details in the delete response.
2 properties
Visibility
object
Visibility represents a single visibility entry with name and extension.
2 properties2 required
QueueProfilePatchRequest
object
QueueProfilePatchRequest represents a partial update request. All fields are optional, but at least one must be provided.
4 properties
QueueProfile
object
QueueProfileResponse represents the response when creating/updating a queue profile. This is named QueueProfile in the OpenAPI spec.
5 properties
QueueProfileRequest
object
QueueProfilesRequest represents the request body for creating a queue profile. Name and Color are required. Visibilities and QueueServiceNumbers are optional.
