get
https://core.{customerId}.ec.avayacloud.com/api/events/v1/subscriptions
Returns a paginated list of existing notification subscriptions for your account.
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
EVENT_NOTIFICATIONclient 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
- Use
pageNumberandpageSizeto paginate results as needed
- 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 EVENT_NOTIFICATION scope.
Once you have your credentials, generate an access token and include it in the Authorization: Bearer <token> header of each request.
POST https://core.avaya1234.ec.avayacloud.com/auth/realms/avaya/protocol/openid-connect/token
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials&client_id=<your_client_id>&client_secret=<your_client_secret>&scope=EVENT_NOTIFICATION
Important Notes
- Results are scoped to your account — derived automatically from your Bearer token.
- Default page size is 10, maximum is 25.
- Use the
links.nextandlinks.prevURLs in the response to navigate between pages.
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.
