Returns a single notification subscription by its subscriptionId.

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:

1. Find your subdomain from your Infinity portal URL (as shown above)
2. Get your Bearer token using the EVENT_NOTIFICATION client credential (see Authentication below)
3. 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 subscriptionId of the subscription you want to retrieve

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

Working with Subscription IDs

Subscription IDs are system-generated UUIDs in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, returned in the response body when a subscription is created. Use the subscriptionId from POST /subscriptions or GET /subscriptions to reference a specific subscription.

Important Notes

• Returns a 404 if no subscription exists with the specified ID.

DOS Protection & Rate Limiting

• This endpoint implements DOS protection and rate limiting.

Security Implementation Guidelines

• Never expose your client_secret or Bearer token to client-side applications.
• Implement proper error handling — avoid surfacing internal error details to end users.