Skip to main content
Minimo sends two events to the webhooks you register:
  • whatsapp.message.received: a contact wrote to one of your WhatsApp numbers.
  • whatsapp.message.status: a message you sent was sent, delivered, read or failed.
The body is the same for every provider (Meta, 360dialog, Twilio), signed with HMAC-SHA256, retried, and sent once per message.
This is your webhook. The webhook Minimo uses to talk to Meta is a different thing, see Inbound & Webhooks.

Received messages

whatsapp.message.received is sent for every message a contact writes to you. Minimo POSTs (or GETs, if you configured method: "GET") this body to your URL. It is versioned — bump of version signals a breaking change; additive fields do not bump it.

Fields

message.media

Present only when the message carries an attachment:

Delivery status events

whatsapp.message.status is sent when a message you sent changes delivery state: sent, delivered, read or failed. Only for numbers answered by your bot (see Overview). Match it to your message with message.wamid (also in the conversation messages).

Delivery headers

Every delivery carries these headers (plus any static headers you registered):

Verify the signature

The signature is the HMAC-SHA256 of the exact raw request body (the bytes on the wire), hex-encoded, keyed by your registration’s secret. Minimo serializes the body once and signs that same string, so you must verify against the raw body — do not re-serialize a parsed object first, or key reordering/spacing will break the check.

Retries and idempotency

Retries and provider re-deliveries mean your endpoint can receive the same wamid more than once. Always dedup on X-Minimo-Delivery (the wamid) before acting on a message.A registration set to inactive (or deleted) is skipped on the next attempt — delivery stops cleanly, with no error and no retry.