Webhook
Integration summary
- Delivery: WhatsApp → Concepto Móvil →
POSTto your webhook URL (the one you share with our Operations team), with a JSON body.- Format: Meta's
valueobject withoutmetadataormessaging_product; Flows notifications arrive with the full object (object,entry).- Identify the user:
from/recipient_idor, if missing, the BSUID.- Expected response: HTTP 200 with no body. Connection errors, timeouts and HTTP 408, 429, 500, 502, 503 or 504 are retried up to 3 times with increasing delays; any other response code is not retried.
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:
| URL | Share your Webhook URL with our Operations team. |
| Method | POST |
| Type | application/json |
Headers
Webhook headers:
| Name | Description | Type | Requirements |
|---|---|---|---|
| Content-Type | application/json; charset=UTF-8 | String | Required |
| Cache-Control | no-cache | String | Required |
| Accept | */* | String | Optional |
Response
Webhook response:
The platform expects your webhook to respond with HTTP 200 and no body. Notifications are retried only on connection errors/timeouts or when the response is HTTP 408, 429, 500, 502, 503 or 504. A notification is retried up to 3 times. Any other response code (e.g. 400, 401, 404) is discarded and not retried. After the last retry fails, the notification is not delivered again.
Note: Flows notifications are delivered to the platform webhook configured for the account (not the per-number webhook), with different headers (no
Cache-Control, optionalAuthorization: Basic …) and are not retried on HTTP error responses (only on I/O errors).
