Single Send - Retry
Last updated
Last updated
We will be updating our response payload to include a creatorId
field from 24 Feb 2025. Please read the last section to find out where the amendment is and update your own systems if necessary, before 24 Feb 2025.
Retries a single failed message. The message will retain the same message ID.
The message retry will only go through if:
The message latestStatus
is failure
If the message belongs to a batch, the batch
status is either messages_enqueued
or messages_enqueuing_failed
After a message is retried, the message latestStatus
will be set to created
.
The Single Send - Retry feature behaves the same way as the feature.
Note that in your retry endpoint, the messageId
remains the same, and is generated from the original request in your .
[Now to 26 Jan 2025] Example response body
[From 24 Feb 2025] The creatorId
field will be inserted in the response payload from 24 Feb 2025. Please amend your own code accordingly for
"creatorId": "<USER_ID_OF_MESSAGE_CREATOR>"