conversation.message.status_changed
A message you sent was delivered, or gave up, after the send call returned. Today this is a Vrbo reply that was answered with 202 and status: "queued" because Vrbo was busy.
When it fires
Once per change, when a queued message becomes sent or failed. failed carries statusReason, in plain words. conversationId and messageId match GET /v1/conversations/{id}/messages, where the message shows the same status. Messages that were delivered within the send call (200) do not send it.
Payload
Every delivery uses the same outer envelope (event, eventId, apiVersion, timestamp, data). Dedupe on eventId — it stays stable across retries and replays, while the X-Repull-Delivery-Id header changes on every attempt.
{
"event": "conversation.message.status_changed",
"eventId": "3f1c9a2e-8b7d-4c6a-9e0f-1a2b3c4d5e6f",
"apiVersion": "2026-04",
"timestamp": "2026-05-01T12:34:56.000Z",
"data": {
"conversationId": "549555",
"messageId": "1861207",
"status": "sent",
"statusReason": null
}
}Verifying signatures
Every delivery includes a timestamped X-Repull-Signature header of the form t=<unix_ts>,v1=<hex>, where v1 is HMAC-SHA256(signing_secret, `${t}.${raw_body}`). Verify it before processing — see Verify Signatures for full Node.js and Python examples.
Use the raw body
Example handler
if (event.event === 'conversation.message.status_changed') {
const { conversationId, messageId, status, statusReason } = event.data
await messages.update(messageId, { status, statusReason })
if (status === 'failed') {
notify(`Reply in conversation ${conversationId} was not delivered: ${statusReason}`)
}
}Common patterns
- Show a queued reply as "sending" in your inbox and switch it to delivered or failed when this arrives.
- Do not resend on
202: the reply is already recorded and being delivered. Resend only afterfailed, if the reason allows it.
Related
Tip: Acknowledge with a 2xx status within 10 seconds. Failed deliveries are retried 7 times over 24 hours, with backoff.Webhook reliability →