Skip to main content
WEBHOOK
Fires when the carrier network confirms that an outbound message was delivered to the recipient’s device. Not all carriers provide delivery receipts; if a carrier doesn’t report delivery status, this event may not fire.
A message.delivered event indicates the carrier accepted the message for delivery — it does not always mean the message reached the recipient’s handset. Carriers vary in how they report delivery, and a delivery receipt can come back even when the message ultimately doesn’t land on the device.

Common use case

Use message.delivered to update delivery status in your own database or to trigger follow-on workflows that depend on confirmed delivery.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
account_id
string
required

The ID of the account in which this event occurred

data
object
required

The data associated with the event

timestamp
string<date-time>
required

The timestamp when this event occurred, in ISO8601 format

type
string
required

The type of the event. Always message.delivered for this event.

Allowed value: "message.delivered"

Response

200

Return a 200 status to indicate that the data was received successfully