Izap Ai Webhooks

generated: '2026-11-12'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://devs.izap.ai/en/api-reference/webhooks.md
sources:
- https://devs.izap.ai/en/api-reference/webhooks.md
description: Outbound webhooks push real‑time WhatsApp events to a HTTPS endpoint you control.
events:
- event: message.received
  description: A new inbound WhatsApp message arrives in a conversation.
- event: conversation.created
  description: A customer opens their first conversation with the business. The conversation carries on when the 24h session renews, so this does
    not fire again.
- event: message.status_updated
  description: 'A message the business sent gets a new delivery status: `sent`, `delivered`, `read`, `played`, `undelivered` or `failed`.'
delivery:
  auth: Bearer token in Authorization header when registering the endpoint; no per‑delivery authentication beyond the signed payload.
  signature: Headers `izap-webhook-signature-v2` (recommended, format `v2=<hex-hmac>`) and legacy `izap-webhook-signature` (format `v1=<hex-hmac>`).
    Signatures are HMAC‑SHA256 over the string `{delivery_id}.{timestamp}.{raw_body}` using the endpoint’s `signing_secret`.
  retries: On retry or manual resend the same `izap-webhook-id` and payload bytes are used, but a fresh `izap-webhook-timestamp` and both signatures
    are recomputed. The `izap-webhook-id` remains stable across retries, allowing idempotent handling.
docs: https://devs.izap.ai/en/api-reference/webhooks.md