2025-01-01
Message delivery failed
Triggered when a message fails to be delivered. This can happen due to:
- Request timeout (message expired before being processed)
- Upstream service error (processing failed after retries)
- Request cancelled (message was explicitly cancelled)
- Service unavailable (no service available to process the request)
- Send blocked (the message was rejected before reaching the messaging service, e.g. a sender eligibility check)
Note: The original message content may not be available if the message expired before being consumed by a processor.
postWebhookmessage.failed.v2025-01-01
Payload
Example payload
{
"api_version": "v3",
"webhook_version": "2025-01-01",
"event_id": "550e8400-e29b-41d4-a716-446655440000",
"created_at": "2025-11-23T17:30:00Z",
"trace_id": "abc123def456",
"partner_id": "partner_abc123",
"data": {
"chat_id": "550e8400-e29b-41d4-a716-446655440000",
"message_id": "550e8400-e29b-41d4-a716-446655440001",
"reason": "Request expired before being processed",
"detail_code": 100001,
"service": "iMessage",
"preferred_service": "iMessage",
"failed_at": "2025-11-23T17:35:00Z"
}
}Response
Webhook received successfully
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.