Callback Services can originate from several Vibes Data Center locations. If a customer wishes to white list the IP traffic to their endpoint, they should include the following Originating IP addresses in their rules.
Client Endpoint Responses
Upon validating the request, the server shall respond with an appropriate response code. A successfully processed message will return an HTTP Server Response of 2XX. If the server responds with an HTTP Server Response of anything other than 2XX, then a system error has occurred and the delivery will be attempted again. Vibes will continue to attempt delivery of the message every five minutes, up to a maximum of five 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.
|Caution: The delivery recipient application must handle all message content delivered. Messages that are considered invalid, like including 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.|
In order to maintain a high-level of service, Vibes callbacks have a relatively short timeout process of two 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).
Only the submitMOMessage callback supports Basic Auth. All other callbacks are made without authentication. Additional information can be found at Client Certificate Authentication for Callbacks from the Vibes Platform.