Last updated: Monday, November 28, 2022
This feature is currently in progress with additional functionality coming soon. Reach out to your account rep to coordinate an implementation plan.
An Event-Triggered Callback can be returned after an Event is sent to Vibes. In order to determine whether or not your event succeeded or failed, you will need to understand the components of an Event Processed Callback and register to receive those callbacks.
Note: Events are primarily used for API-Triggered Messages. For more information on Events and their uses, please see our Event-Triggered Messages integration scenario.
If the Event that was received and the action is processing, you will see a success callback such as the one below.
Potential Routing Failures
No Route Rules
This indicates that the system was not able to find an action in the system like an Event-Triggered Message to send the received Event to.
Person Doesn’t Belong To Associated Subscription List
Person Not Found
This failure occurs when the person that is referenced in the Event is not found.
Carrier Not Supported
This failure occurs when the MDN referenced in the Event cannot be reached. This may be because the number is a landline, or it is on an unsupported carrier.
Potential Processing Failures
No Incentive Codes
If the destination Event-Triggered Message is using an Incentive Pool and there are no incentive codes remaining to be used, you will receive this failure message.
When some unexpected error has occurred during the Event-Triggered Message, you may receive this code.
Potential Processing Callbacks
SMS Message Queued To Be Sent To Carrier
You will receive this callback when an SMS message was successfully generated for an Event-Triggered Message and the message is queued to be sent to the carrier.
event_data and debug_data from the original Event will currently not be returned in the callback. This information is being worked on being provided in a future update.
Elements & Attributes of a Call
|Success/Failure||Unique Event ID for the callback event.|
|Success/Failure||When the event occurred.|
The callback type that was registered for.
Will always be
An object describing the details of the success or failure of the actions that were taken during the processing of the Event that was sent in to Public API.
Indication whether the action related to the Event is in a processing state, failed or succeeded.
|Success/Failure||Indicates the reason for the action status.|
|Processing/Failure||Indication of what type of message is being referenced.|
|Processing/Failure (SMS)||The path to the resource that generated the message.|
|Processing/Failure (SMS)||The person key identifier for the person that was associated to the message that was generated.|
|Processing/Failure (SMS)||The path to the person resource that was associated to the message that was generated.|
If a failure has occurred, this object will containing failure information for the action being described, including reason and error(s).