Latest Legacy

Verify Status Callbacks

The best way to keep track of the status of your Verify sessions is to set up a server endpoint to receive status update events in real-time.

Once you’ve configured this endpoint, specify its URL and HTTP method in the create a verify session request. Plivo will call this endpoint with the latest Verify session details as and when the session status changes.


With every status change event, these message attributes are passed to the status update URL. They’re passed as form data if the method configured is POST, and as query parameters if it’s GET.

AttemptSequence string

This indicates the sequence of the verification attempt for which you are receiving this callback.

AttemptUUID string

This is the unique identifier for the SMS that was sent or Voice call that was triggered as part of the Verify session.

Channel string

The channel you used to send the code.

Possible values: sms,voice

ChannelErrorCode string

This is the error code returned by the channel on which verification was attempted.

ChannelStatus string

This indicates the status of your verification request based on the specified channel. Possible values:

sms - queued, sent, undelivered, failed, delivered

voice - in-progress, completed, ringing

Recipient string

The phone number to which the message is to be delivered.

RequestTime string

UTC time when this attempt was created.

SessionStatus string

The current status of the session.

Possible values: in-progress and expired.

SessionUUID string

A 36-character string that uniquely identifies a session detail record.