Service-Scoped Delivery Receipt Resource
Service-Scoped Delivery Receipts in Conversations provide visibility into the status of Service-Scoped Conversation Messages sent across different Conversations within a non-default Conversation Service.
Using Service-Scoped Delivery Receipts, you can verify that Messages have been sent, delivered, or even read (for OTT) by Conversations Participants within a non-default, service-scoped Conversation Service.
API Base URL
All URLs in the reference documentation use the following base URL:
https://conversations.twilio.com/v1
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:
GET /v1/Services/ISxx/Conversations/CHxx/Messages
ServiceConversationMessageReceipt properties
| Resource Properties in REST API format | |
|---|---|
account_sid
|
The unique ID of the Account responsible for this participant. |
chat_service_sid
|
The SID of the Conversation Service the Message resource is associated with. |
conversation_sid
|
The unique ID of the Conversation for this message. |
message_sid
|
The SID of the message within a Conversation the delivery receipt belongs to |
sid
|
A 34 character string that uniquely identifies this resource. |
channel_message_sid
|
A messaging channel-specific identifier for the message delivered to participant e.g. |
participant_sid
|
The unique ID of the participant the delivery receipt belongs to. |
status
|
The message delivery status, can be |
error_code
|
The message delivery error code for a |
date_created
|
The date that this resource was created. |
date_updated
|
The date that this resource was last updated. |
url
|
An absolute API resource URL for this delivery receipt. |
Need some help?
We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.
