Create, retrieve, update, and delete queues programmatically in the Avaya Infinity. Queues are collections of agents used for routing customer interactions. This API is intended for organizations that manage large numbers of queues or need to integrate queue configuration into external applications and workflows as an alternative to manual administration through the Infinity portal.
Endpoints
Create a Queue
POST /queues
Creates a new queue with a specified name and configuration.
List Queues
GET /queues
Returns a paginated list of queues with optional filters for name, active status, folder, and type.
Get a Queue
GET /queues/{id}
Returns the full configuration details for a specific queue by its ID.
Update a Queue
PUT /queues/{id}
Updates the configuration of an existing queue. All fields are optional — only provided fields are modified.
Delete a Queue
DELETE /queues/{id}
Permanently or soft-deletes a queue by its ID.
Getting Started
Find Your Customer Subdomain
Your subdomain is found in your Infinity portal URL and is required for all API calls.
Example: If your portal URL is:
https://core.avaya1234.ec.avayacloud.com/app/core-config-ui/Your subdomain is: avaya1234
All API requests use this format:
https://core.{customerId}.ec.avayacloud.com/api/config/v1/...Authentication
All endpoints require Bearer token authentication. To get started, contact Avaya Support to request a client_id and client_secret provisioned with the ADMIN_API_CONSUMER scope. Once you have your credentials, generate an access token.
Working with Queue IDs
Queue IDs are system-generated identifiers assigned at creation, distinct from the queue's display name. They follow the format 003xxxxxxxxxxxxxxxxxxxxxxx and can be found in the response body of POST /queues or GET /queues, or in the Avaya Infinity portal URL when viewing a queue's configuration.
Example: A queue ID looks like this: 003d010826307dd6630992437c
Use this ID in all subsequent API calls to get, update, or delete a specific queue.
Common Integration Patterns
Bulk Queue Provisioning — Use POST /queues in sequence to programmatically create and configure large numbers of queues, eliminating manual portal administration.
Sync Queue Configuration — Use GET /queues with filters to retrieve current queue state and compare or sync it against an external system of record.
Dynamic Activation — Use PUT /queues/{id} to activate or deactivate queues in real time in response to staffing changes or business events.