Webhooks
Events delivered
as they happen.
Register an endpoint and beeoneten pushes events to it in real time: new messages, delivery and read receipts, and changes to conversations. No polling required.
Real-time · Retries · Delivery log · Event filtering
Real time
Events arrive within moments of happening.
Retried on failure
If your endpoint is down, delivery is retried.
Logged
See every event sent and how your endpoint responded.
Delivery status
Know what reached
each customer.
Status events tell your system when a message was delivered, read or failed, so you can update orders, retry on another channel or alert your team.
Triggers
Events in, and
events out.
Send your own events to beeoneten to start a workflow, such as an order shipping, and receive events back as the conversation moves on.
Events
Kinds of events you can receive.
Exact event names and payloads are in the API reference.
Incoming messages
A customer sent a message on any channel.
Message status
Sent, delivered, read or failed.
Assignment
A conversation was assigned or reassigned.
Tickets
A ticket was opened, updated or resolved.
Contacts
A contact was created or updated.
Templates
A WhatsApp template was approved or rejected.
Getting started
Your first webhook.
An HTTPS endpoint that accepts POST requests is all you need.
-
1
Create an endpoint
An HTTPS URL on your server that accepts POST requests.
-
2
Register it
Add the URL in beeoneten and choose which events to receive.
-
3
Verify requests
Check each request really comes from beeoneten.
-
4
Respond quickly
Return a success code, then process the event in the background.
Common questions.
What happens if our endpoint is down?
Delivery is retried for a period of time, and every attempt is shown in the webhook log, so you can see what was missed.
Can we choose which events we receive?
Yes. Subscribe only to the events your system needs.
How do we know a request came from beeoneten?
Requests can be verified so your endpoint can reject anything that did not come from beeoneten. The method is described in the API reference.
Where are the exact event names and payloads?
In the API reference, shared when API access is set up. The examples on this page are illustrative.
Connect your systems
to every conversation.
Request API access and we will send the webhook reference with example payloads.
Local team in Indonesia · Developer onboarding included