Delivery Receipts in Conversations provide visibility into the status of Conversation Messages sent across different channels.
Using Delivery Receipts, you can verify that Messages have been sent, delivered, or even read (for OTT) by Conversations Participants.
All URLs in the reference documentation use the following base URL:
_10https://conversations.twilio.com/v1
Using the REST API, you can interact with Conversation Message Receipt resources in the default Conversation Service instance via a "shortened" URL that does not include the Conversation Service instance SID ("ISXXX..."). If you are only using one Conversation Service (the default), you do not need to include the Conversation Service SID in your URL, e.g.
_10GET /v1/Conversations/CHxx/Messages/IMXXX/Receipts
For Conversations applications that build on more than one Conversation Service instance, you will need to specify the Conversation Service SID in the REST API call:
_10GET /v1/Services/ISxx/Conversations/CHxx/Messages/IMXXX/Receipts
The SID of the message within a Conversation the delivery receipt belongs to
A messaging channel-specific identifier for the message delivered to participant e.g. SMxx
for SMS, WAxx
for Whatsapp etc.
The unique ID of the participant the delivery receipt belongs to.
The message delivery status, can be read
, failed
, delivered
, undelivered
, sent
or null.
read
failed
delivered
undelivered
sent
The date that this resource was last updated. null
if the delivery receipt has not been updated.
An absolute API resource URL for this delivery receipt.
GET https://conversations.twilio.com/v1/Conversations/{ConversationSid}/Messages/{MessageSid}/Receipts/{Sid}
GET https://conversations.twilio.com/v1/Conversations/{ConversationSid}/Messages/{MessageSid}/Receipts
How many resources to return in each list page. The default is 50, and the maximum is 1000.