Inbound messages
Receive supported customer messages and media events so connected systems can store, route or respond to the conversation.
Event-driven WhatsApp integrations
WhatsApp Webhooks and Real-Time Event Notifications
Receive supported WhatsApp message, interaction and delivery-status events at your HTTPS endpoint so your CRM, support, commerce and automation systems can react without repeatedly polling for changes.
- Server-to-server HTTPS delivery
- JSON event payloads
- API and automation workflows
Event delivery flow
WhatsApp event
Message or status update
BotLinkd webhook
Supported event is delivered
Your HTTPS endpoint
Validate, queue and process
Exact event names, fields and authentication requirements are defined in the current BotLinkd API documentation for your integration.
Direct definition
What are BotLinkd WhatsApp webhooks?
A webhook is an event-driven HTTPS callback. When a supported event occurs, BotLinkd sends structured data to the endpoint configured by your business. Your application can then validate the request and perform an authorised action such as updating a CRM record, routing a support ticket or recording a delivery status.
Webhooks complement the BotLinkd API: webhooks notify your system about events, while API requests perform supported actions. BotLinkd operates as an independent business messaging platform built on the official WhatsApp Business Platform Cloud API.
Event coverage
Use real-time events across business messaging workflows
Subscribe only to the information your integration requires. Event availability depends on the connected feature, account configuration and current platform capabilities.
Message status updates
Process available sent, delivered, read and failed status events for operational reporting and campaign analysis.
Customer interactions
React to supported button replies, list selections and other structured interactions returned by the connected WhatsApp workflow.
Automation triggers
Start CRM actions, order lookups, ticket routing, notifications or internal workflows when a relevant event arrives.
How delivery works
From WhatsApp event to business action
The integration stays easier to operate when event receipt and business processing are treated as separate stages.
-
01
An event occurs
A customer sends a message, selects an interactive option or a previously sent message changes status.
-
02
BotLinkd receives the event
BotLinkd processes the supported event from the official WhatsApp Business Platform connection.
-
03
Your endpoint receives JSON
BotLinkd sends the subscribed event to the HTTPS webhook URL configured for your integration.
-
04
Your system takes action
Your application validates, records and processes the event according to the workflow you have implemented.
Implementation checklist
Build a reliable webhook receiver
A production endpoint needs more than a public URL. Use validation, duplicate protection, observability and secure data handling from the first release.
Check the current technical contract-
1
Create a public HTTPS endpoint
Use a stable HTTPS URL that can accept the supported webhook requests documented for your BotLinkd integration.
-
2
Configure the callback in BotLinkd
Add the endpoint in the applicable BotLinkd dashboard or integration settings and enable only the events your system needs.
-
3
Validate every request
Apply the authentication or verification mechanism documented for the integration before trusting or processing a payload.
-
4
Acknowledge accepted events promptly
Keep the request path lightweight. Record or queue accepted events, return the required successful response and perform slower work asynchronously in your own application.
-
5
Make processing idempotent
Use the event or message identifier to prevent duplicate business actions when the same delivery is retried or received more than once.
-
6
Monitor failures and latency
Track validation failures, response codes, processing time, queue depth and downstream errors without logging confidential message content unnecessarily.
Illustrative JSON
A webhook payload should be treated as a versioned contract
The example shows the type of structured information an event-driven integration may receive. It is intentionally illustrative and is not a substitute for the current BotLinkd API specification.
- Validate the documented request authentication before parsing the event.
- Use a stable event or message identifier for duplicate protection.
- Do not assume every event includes every optional field.
- Keep raw customer content out of routine application logs where it is not required.
Illustrative event payload
application/json
{
"event": "message.received",
"event_id": "evt_example_01",
"occurred_at": "2026-07-03T10:30:00Z",
"data": {
"message_id": "wamid.example",
"from": "CUSTOMER_NUMBER",
"to": "BUSINESS_NUMBER",
"type": "text",
"text": {
"body": "Hello, I need help with my order."
}
}
}Field names and values shown above are examples. Implement against the documented payload for the BotLinkd feature connected to your account.
Security and resilience
Protect the endpoint and the customer data it receives
Authenticate requests
Reject requests that do not satisfy the verification method documented for the integration.
Use HTTPS only
Keep transport encryption active and maintain a valid certificate on the public callback URL.
Restrict data exposure
Apply least privilege, controlled retention and redacted logging for personal or confidential content.
Design for retries
Make processing idempotent and keep enough event history to investigate failures without duplicating actions.
Separate receipt from processing
Queue accepted events so external API calls and heavier business logic do not block the incoming request.
Monitor operational health
Alert on unusual error rates, authentication failures, queue growth and delayed processing.
Business applications
Connect customer events to the systems your teams already use
BotLinkd webhooks can support event-driven workflows across customer service, sales, e-commerce, automation and reporting.
Support routing
Create or update support tickets, route priority messages and preserve conversation context for authorised agents.
CRM synchronisation
Update contact timelines, lead stages and follow-up tasks when a relevant customer interaction is received.
Commerce workflows
Connect customer messages with order lookup, payment, shipping, returns or other supported commerce processes.
AI and human handover
Use events to trigger supported AI assistance while retaining human escalation, per-contact AI pause and platform-wide control.
Delivery analytics
Store available message-status events for operational dashboards, campaign review and delivery troubleshooting.
Internal notifications
Notify authorised teams or connected systems when selected events require review or manual action.
API and webhook roles
Use webhooks for events and APIs for actions
| Capability | Webhook | API request |
|---|---|---|
| Primary purpose | Notify your system when a subscribed event occurs | Ask BotLinkd to perform or return a supported operation |
| Who initiates | BotLinkd sends the event to your configured endpoint | Your application sends a request to a documented endpoint |
| Typical use | Inbound message, interaction or delivery-status processing | Send a message, access supported data or manage an integration workflow |
| Recommended design | Validate, acknowledge, queue and process idempotently | Authenticate, validate input, handle response codes and respect applicable limits |
Need a ready-made conversation interface?
Authorised BotLinkd users can also manage supported customer conversations through the BotLinkd chat workspace instead of building every interface from the beginning.
Webhook FAQ
Common questions about BotLinkd WhatsApp webhooks
What is a WhatsApp webhook?
A WhatsApp webhook is an HTTPS callback used to deliver event data to a configured endpoint when a supported messaging event occurs. Instead of repeatedly polling for updates, your application can receive relevant events as they are made available.
Which WhatsApp events can BotLinkd send to my system?
Available events can include supported inbound messages, customer interactions and message-status updates such as sent, delivered, read or failed. Exact event names, fields and availability depend on the connected BotLinkd feature, account configuration and current platform capabilities.
Do I still need the BotLinkd API when I use webhooks?
Usually, yes. Webhooks notify your application that an event occurred, while API endpoints are used for supported actions such as sending a reply or retrieving applicable data. The two mechanisms are designed to work together.
Should webhook processing happen inside the incoming request?
Keep the incoming request path small and reliable. Validate the request, store or queue the event, return the required successful response and complete slower business logic in your own background worker or queue system.
How should duplicate webhook events be handled?
Treat webhook delivery as potentially repeatable. Store a stable event or message identifier and make downstream actions idempotent so a retry does not create duplicate tickets, orders, replies or notifications.
Can webhook payloads contain customer data?
Yes. A payload may contain business messaging data required for the event. Protect the endpoint, restrict access, minimise logs, apply appropriate retention controls and process personal data according to your legal and contractual obligations.
Where can developers find the exact payload contract?
Use the current BotLinkd API documentation for the authoritative event names, authentication method, headers, field definitions and response requirements that apply to your account and integration.
Build with BotLinkd
Connect WhatsApp events to your business systems
Review the API documentation or discuss the required webhook events, security model and workflow with the BotLinkd team.