As part of using the Event Subscription API, you will receive email notifications sent by the service. Some of these notifications are for information purposes only, such as confirming that a new subscription has been created or informing you when a subscription has been paused. However, some of these notifications are crucial alerts such as your subscription has failed and others may require you to perform specific actions in order to keep your subscriptions active and functional. Depending on the type of notification, these actions may range from increasing your daily event limit to manually extracting unsent event data.
\nCurrently, the following event notifications may be received and should be reviewed for any potential actions required:
\nSee the sections below for more specific details on each notification.
\nReceived to notify you that your subscription to a specific trigger is once again active and will begin forwarding new emitted events.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nSent to confirm that a subscription to a specific trigger has been deleted and will no longer be sending events.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nNotification that one of your current subscriptions has started to fail and cannot send your event data. Any events that are unable to be sent to you will be saved in the system, so no data will be lost.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nConfirmation message that a new subscription was successfully created. These notifications also include basic information about the new subscription, such as the Subscription ID, Subscription Name, Protocol and Callback URL.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nNotification that one of your active subscriptions has been paused and will not forward events to you until the subscription is resumed. Any events that are unable to be sent to you will be saved in the system, so no data will be lost.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nIndicates that a previously paused subscription has been resumed and will begin forwarding new events to you. Any unsent events that were saved while the subscription was paused will also be forwarded once the subscription is resumed.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nNotification that your subscription was rejected because the system has been unable to deliver events to your webhook. Any events that are unable to be sent to you will be saved in the system, so no data will be lost.
\nReceived when:
\nRequired actions:
\nOptional actions:
\nPATCH /intelligence/api/subscriptions/${subscriptionId}/events
\nMessage sent when an active subscription has continuously failed and will be suspended. Includes the specific date on which the subscription began to fail. Any pending data will be lost as a result of the subscription being suspended.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\nWarning message sent when you reach the maximum number of allowed subscriptions to knowledge model triggers. Reaching this limit will not impact any active subscriptions. However, it will prevent you from creating any new subscription.
\nTriggering event:
\nRequired actions:
\nOptional actions:
\n