put
https://core.{customerId}.ec.avayacloud.com/api/config/v1/queues/
Updates the configuration of an existing queue. All fields are optional — only the fields included in the request body will be updated.
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
- Enter the
idof the queue to update and provide only the fields you want to change
- 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
- All fields in the request body are optional. Only fields explicitly provided will be modified — omitted fields retain their existing values.
- Updating the
nameto one already used by another queue returns a422with the messagename must be unique. - Returns a
404if no queue exists with the specified ID.
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.
