WE'RE MOVING! Check out our new Vibes Developer Hub for Aggregation. Please note that this page will no longer be available starting January 13, 2023.
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Callback Services are HTTP requests that are made from the Vibes platform to a Customer's URL endpoint, for the event based delivery of information. This can be either Mobile Originated (MO) messages or Mobile Terminated (MT) Delivery Receipts.

Originating Traffic

Callback Services can originate from either of Vibes' two Data Centers. If a customer wishes to whitelist the IP traffic to their endpoint, they should include the following Originating IP addresses in their rules:

Data CenterIP Address
Elk Grove (Chicago)

Client Endpoint Responses

Upon validating the request, the server shall respond with appropriate response code.  A successful message processed shall return an Http Server Response of 2XX.  If the server responds with an Http Server Response of anything other than 2XX, then there was a system error that occurred and the delivery will be attempted again.  Vibes will continue to attempt delivery of the message every 5 minutes up to a maximum of 5 retries before moving the message into an error queue and alerting Vibes Operations staff.  The Operations staff will contact the Customer to resolve the issue. Once the customer has resolved the problem with their endpoint, any messages that are less than 24 hours old can be resent by Vibes Operations staff.

Note: The delivery recipient application must handle all message content delivered.  Messages that are considered invalid (ex: Bad keyword), are the responsibility of the client to log and acknowledge with Http Response 200, to keep Vibes delivery service from continually retrying delivery of the message.

Performance Considerations

In order to maintain high levels of service, the Vibes callbacks have a relatively short timeout process of 2 seconds. Customers should make every effort in their design to minimize any processing done synchronously on the callback and utilize store and forward to avoid timeouts (and retries).


  • No labels