Clickatell One API Client Callbacks API
Forward CompatibilityWhile the basic callback structure will remain constant: { "integrationId": "string", "integrationName": "string", "event": {} }There are constant additions to channels including new features and message types, and Clickatell will be adding these to the callbacks as they become available. Customers are required to implement callback processing in such a way that new event types as well as additional parameters in an event type do not break callback processing in the customer system.Any HTTP 200 range status code response from client is considered an acknowledgement that the callback was successful. Anything else will be retried, excluding redirect status code.Callback payloads and configurations are different (not backwards compatible).In future, one HTTPS callback request may contain multiple events for efficiency, but for now batch sizes are always 1.The events in callbacks may be out of sequence. User should look at timestamp fields to determine order.Timestamps are millisecond unit timestamps.If the customer application does not respond fast enough to HTTP/S callbacks, we will retry the callback. This means they may experience duplicate callbacks (due to the retries).Customer can configure a callback URL for status event callbacks and another URL for MO messages. This helps to maintain low latency conversations by splitting the events.