post
https://core.{customerId}.ec.avayacloud.com/api/config/v1/queues
Creates a new queue with the specified name and configuration. The name field is required and must be unique within your organization.
Finding Your Customer Subdomain
Your subdomain is found in your Avaya 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
To use this API:
- Find your subdomain from your Infinity portal URL (as shown above)
- Get your Bearer token using the
ADMIN_API_CONSUMERclient credential (see Authentication below) - In the API explorer on the right:
- Click on
{customerId}in the URL field and replace it with your actual subdomain - Paste your Bearer token in the Credentials section
- Fill out the request body with at minimum a unique queue
name
- Click on
Authentication
This endpoint requires a valid OAuth 2.0 Bearer token. 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 and include it in the Authorization: Bearer <token> header of each request.
Important Notes
nameis the only required field. All other fields are optional and can be updated later.- Queue names must be unique within your organization. Submitting a duplicate name returns a
422with the messagename must be unique. - The
queueIdreturned in the response is the permanent identifier used in all subsequent API calls for this queue.
DOS Protection & Rate Limiting
- This endpoint implements DOS protection and rate limiting.
Security Implementation Guidelines
- Never expose your
client_secretor Bearer token to client-side applications. - Implement proper error handling — avoid surfacing internal error details to end users.
