Session Message Failed

eventType: sessionMessageFailed. A session-message attempt failed. HTTP acceptance of the original send is separate from this delivery result.

Use this documented event only when it is registered by your workspace's event-types API and the relevant product/channel is available on your account. Registration alone is not a delivery guarantee; verify an actual permitted event reaches your enabled subscription. Acknowledge promptly with a successful 2xx; process idempotently and allow duplicate/out-of-order delivery. Do not assume a universal event UUID, fixed retry schedule or signing scheme. See webhook setup and recovery.

Example

{
  "eventType": "sessionMessageFailed",
  "id": "<wati-message-id>",
  "conversationId": "<conversation-id>",
  "ticketId": "<ticket-id>",
  "localMessageId": "<caller-local-message-id>",
  "type": "session",
  "statusString": "Failed",
  "text": "Example session message",
  "timestamp": "1793318400",
  "failedCode": "<provider-failure-code>",
  "failedDetail": "Message could not be delivered."
}

The example is illustrative, not an exhaustive list of fields or possible outcomes. Null/absent values must be handled.

Field	Type / meaning
`id`	WATI message identifier; keep distinct from localMessageId and the provider ID.
`localMessageId`	Caller correlation when available; not a universal request-idempotency guarantee.
`whatsappMessageId`	Provider message identifier when available; may be absent on an early failure.
`conversationId / ticketId`	Related conversation/ticket identifiers when present.
`type`	session.
`statusString`	Failed.
`timestamp`	Unix seconds as a string, assigned when the failure notification is mapped; not necessarily the original send time.
`failedCode / failedDetail`	Failure code/detail strings from the provider/service; do not assume one fixed enumeration.
`operatorEmail / assigneeId`	Optional sender/assignment metadata.
`channelId / channelPhoneNumber`	Optional channel metadata when emitted.