Retry a failed message
Puts a failed outgoing message back to sent and queues delivery again.
It clears content_attributes as part of the retry, so anything stored there — submitted form values, external error details, rich-message payloads — is lost. A message ID that does not exist is a silent no-op rather than a 404.
Authorizations
This token can be obtained by visiting the profile page or via rails console. Provides access to endpoints based on the user permissions levels. This token can be saved by an external system when user is created via API, to perform activities on behalf of the user.
Path Parameters
The numeric ID of the account
The numeric ID of the conversation
The numeric ID of the message
Response
Success
The ID of the message
The text content of the message
The ID of the account
The ID of the inbox
The ID of the conversation
0 = incoming, 1 = outgoing, 2 = activity, 3 = template.
0, 1, 2, 3 The time at which message was created
ISO-8601 timestamp of the last update. Note this differs from created_at on the same object, which is unix epoch seconds.
The flags which shows whether the message is private or not
The status of the message
sent, delivered, read, failed The source ID of the message
The type of the template message
text, input_select, cards, form The content attributes for each content_type
The class of the sender, capitalised to match the underlying record type.
Contact, User, AgentBot The ID of the sender
The external source IDs of the message
The additional attributes of the message
The processed message content
The sentiment of the message
The conversation object
The file object attached to the image
User/Agent/AgentBot object