Skip to contentSkip to navigationSkip to topbar
Page toolsOn this page
Looking for more inspiration?Visit the

Message Status Stream


Message status events

message-status-events page anchor

The message status stream provides real-time information on the delivery status of messages sent from your Verify Service. By subscribing to specific message status events, you can identify and respond to issues impacting message delivery by carriers. The message status stream is equivalent to the outbound message event's stream provided by Twilio Programmable Messaging.


You can subscribe to five message status events through Event Streams:

Event typeEvent type stringDescription and timing
Message sentcom.twilio.accountsecurity.verify.message.sentThis event fires when the messaging channel provider accepts the message for downstream processing. Delivery is not yet confirmed.
Message deliveredcom.twilio.accountsecurity.verify.message.deliveredThis event fires when the channel provider confirms successful delivery to the end user.
Message readcom.twilio.accountsecurity.verify.message.readThis event fires when the messaging channel provider confirms the end user opened or read the message. Not available for the SMS channel.
Message undeliveredcom.twilio.accountsecurity.verify.message.undeliveredThis event fires when the channel provider reports that the message could not be delivered to the end user.
Message failedcom.twilio.accountsecurity.verify.message.failedThis event fires when the messaging channel provider reports that message delivery failed. The provider doesn't make further delivery attempts unless you send a new attempt.

Delivered

delivered page anchor
1
[
2
{
3
"specversion": "1.0",
4
"type": "com.twilio.accountsecurity.verify.message.delivered",
5
"source": "/v1/Accounts/ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/Services/VAaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/Verifications/VEaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
6
"id": "ea3f13068cb622aa37b0e1f6d88bed4095c7fb07f31d9aeb60f8d1800f02fe38",
7
"dataschema": "https://events-schemas.twilio.com/AccountSecurity.MessageStatusEvent/1",
8
"datacontenttype": "application/json",
9
"time": "2026-02-17T09:20:25.336Z",
10
"data": {
11
"channel": "SMS",
12
"verification_sid": "VEaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
13
"to": "+919999999999",
14
"mcc": "272",
15
"number_segments": 1,
16
"created_at": "2026-02-17T09:20:25.336Z",
17
"account_sid": "ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
18
"attempt_sid": "VLaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
19
"has_fallback": false,
20
"mnc": "05",
21
"is_fallback": false,
22
"service_sid": "VAaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
23
"message_status": "DELIVERED"
24
}
25
}
26
]

Event resource properties

event-resource-properties page anchor
PropertyTypeDescription
account_sidstringThe SID of the Account that is sending the message.
service_sidstringThe unique SID identifier of the Verify Service that is sending the message.
verification_sidstringThe unique SID identifier of the OTP verification to which the messages belong.
channelstringThe messaging channel used to send a message. Supported channels include SMS, WhatsApp, RCS, and Voice.
created_atstringThe date and time that the message started to be processed in ISO 8601 format.
message_statusstringThe message status, which is equivalent to a delivery receipt reported to Verify by the messaging channel provider. It can be one of: DELIVERED, UNDELIVERED, SENT, READ, FAILED.
tostringThe destination phone number in E.164 format.
mccstringThe Mobile Country Code that uniquely identifies the destination country for the message.
mncstringThe Mobile Network Code which uniquely identifies the destination network for the message.
number_segmentsintegerThe number of segments used to send the message.
attempt_sidstringThe unique SID identifier of the Verification Attempt. There is one primary message per attempt.
has_fallbackbooleanIndicates whether an alternate channel fallback is available if the message status is FAILED or UNDELIVERED.
is_fallbackbooleanIndicates whether the message is a fallback from a previous message.