Skip to main content
WEBHOOK
Fires when a contact sends a message to one of your phone numbers. This is the primary event for building two-way messaging flows. If this is the first message in a new thread, conversation.created fires alongside it.

Common use case

Use message.received to drive inbound message handling, auto-reply bots, support ticket creation, or forwarding to a human agent. To reply, call POST /accounts/{account_id}/messages with the same conversation.id.

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.received for this event.

Allowed value: "message.received"

Response

200

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