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.
All URLs in the reference documentation use the following base URL:
_10https://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:
_10GET /v1/Services/ISxx/Conversations/CHxx/Messages
account_sid
type: SID<AC>The unique ID of the Account responsible for this participant.
^AC[0-9a-fA-F]{32}$
34
34
chat_service_sid
type: SID<IS>The SID of the Conversation Service the Message resource is associated with.
^IS[0-9a-fA-F]{32}$
34
34
conversation_sid
type: SID<CH>The unique ID of the Conversation for this message.
^CH[0-9a-fA-F]{32}$
34
34
message_sid
type: SID<IM>The SID of the message within a Conversation the delivery receipt belongs to
^IM[0-9a-fA-F]{32}$
34
34
sid
type: SID<DY>A 34 character string that uniquely identifies this resource.
^DY[0-9a-fA-F]{32}$
34
34
channel_message_sid
type: SIDA messaging channel-specific identifier for the message delivered to participant e.g. SMxx
for SMS, WAxx
for Whatsapp etc.
^[a-zA-Z]{2}[0-9a-fA-F]{32}$
34
34
participant_sid
type: SID<MB>The unique ID of the participant the delivery receipt belongs to.
^MB[0-9a-fA-F]{32}$
34
34
status
type: enum<string>The message delivery status, can be read
, failed
, delivered
, undelivered
, sent
or null.
read
failed
delivered
undelivered
sent
date_updated
type: string<date-time>The date that this resource was last updated. null
if the delivery receipt has not been updated.