logo
enes

Webhook

Last update: 6 hours ago by Irais Aguirre

Integration summary

  • Delivery: WhatsApp → Concepto Móvil → POST to your webhook URL (the one you share with our Operations team), with a JSON body.
  • Format: Meta's value object without metadata or messaging_product; Flows notifications arrive with the full object (object, entry).
  • Identify the user: from/recipient_id or, if missing, the BSUID.
  • Expected response: HTTP 200 with no body; otherwise the notification is retried with exponential backoff.

Every notification is sent to your webhook with the same HTTP request. The body depends on the notification type; see the pages in Receive notifications.

Webhook

Request

Webhook request:

URLShare your Webhook URL with our Operations team.
MethodPOST
Typeapplication/json

Headers

Webhook headers:

NameDescriptionTypeRequirements
Content-Typeapplication/json; charset=UTF-8StringRequired
Cache-Controlno-cacheStringRequired
Accept*/*StringOptional

Response

Webhook response:

The platform expects your webhook to respond with an HTTP 200 code and no body. Retries only happen on connection errors/timeouts or when the response has one of the HTTP status codes 408, 429, 500, 502, 503 or 504 (limited number of attempts with exponential backoff); other response codes (e.g. 400, 401, 404) are discarded and not retried.

Note: Flows notifications are delivered to the platform webhook configured for the account (not the per-number webhook), with different headers (no Cache-Control, optional Authorization: Basic …) and are not retried on HTTP error responses (only on I/O errors).



WhatsApp — Previous
Receive notifications
Next — WhatsApp
Message notifications