Adds a new notification subscription when one does not exist or replaces the existing one if it exists. An Authorization can also be added to this API.
Only one is allowed per group.
An Authorization can also be added to this API. To achieve this, a customer can create an authorization that Webex Connect supports, which generates a unique authorization ID. To create an authorization, navigate to the Authorizations tab under Assets > Integrations section.
Adding Authorization in Contact Policy Add or update a subscription API allows the notification receiving server to confirm that the notifications are being sent from an authorized system. The receiving server can verify the token received in the header of the request. Successful verification of the token indicates that the notification is received from the authorized system.
For more information on Authorizations, refer here.
auth ID is an optional parameter in the API. Adding the authId as a parameter in the body of the API request will add Authorization as a header in the notification response.
Once the authentication successful, the header ‘Authorization’ is added to the notification request as shown in the below example:
If there is no value or invalid values or invalid parameter name for Auth ID are passed, the values are ignored by the API.
Note
When you are sending the Auth ID as an optional parameter, the payload sent in the notification will change as per the request.
Sample Payload
{
"callbackUrl" : "https://01hXXXXXXXXXX04XXXXXXXXXXy00-bb8fXXXXXXXXXX949363.requestinspector.com",
"authId" : 123
}
{
"callbackUrl" : "https://01hXXXXXXXXXX04XXXXXXXXXXy00-bb8fXXXXXXXXXX949363.requestinspector.com"
}