Webhook for message status updates
This webhook is triggered when the status of a sent message changes. A separate notification is sent for each actual message sent. "The possible status updates are: DELIVERED, READ, FAILED (only for the last channel of the fallback chain), and NOSENT. "Notifications are only sent for the final delivery channel. If a webhook call fails, retries will be performed at increasing intervals for up to 48 hours.
Body
Required
Payload for the message status update callback
-
The API call ID, returned in the response of the message dispatch request.
-
The message ID.
-
Refers to the specific content of the translation sent in the request or the single content defined in the template used for sending.
-
Total number of content parts, representing the actual number of messages sent to the recipient.
-
Values are
RCS
,SMS
, orWHATSAPP
. -
The user identifier specified in the API request for the current channel.
-
The new status of the message. Possible values: DELIVERED, READ, FAILED, NOSENT.
Values are
DISPATCHED
,NOSENT
,SENT
,FAILED
,DELIVERED
, orREAD
. -
The order number to be used for sorting statuses when notifications have the same timestamp. Notifications may arrive out of order due to provider behavior or webhook retries.
-
The date and time (UTC) of the status change.
-
General metadata sent in the message dispatch request.
-
Metadata specific to the recipient associated with the channelIdentifier specified in the message dispatch request.
{
"dispatchId": "0FCB1XXXVEABC",
"messageId": "0FCB1ABCVEXYZ",
"messagePart": 1,
"messageTotalParts": 3,
"channel": "RCS",
"channelIdentifier": "+390000000",
"status": "DELIVERED",
"statusOrder": 10,
"statusDate": "2024-01-01T14:30:00Z",
"dispatchMetadata": {
"additionalProperty1": "string",
"additionalProperty2": "string"
},
"recipientMetadata": {
"additionalProperty1": "string",
"additionalProperty2": "string"
}
}