Features
API and webhooks
Your software already knows when a booking is made or a report is ready. With one API call it can tell the customer on WhatsApp, and webhooks tell your software what happened next.
What you get
Send from your software. Hear back instantly.
One request to send
POST a message or an approved template, and get a message ID straight back.
Idempotent by design
Send a reference with each message, and a retry will never message a customer twice.
Signed webhooks
Delivery receipts, replies and template updates, signed so you can verify they are genuine.
Consent enforced for you
The API refuses to send to opted-out people, and to message people outside the 24-hour window without a template.
Clear, stable errors
Every failure has a code you can switch on, not a message you have to parse.
Docs developers like
Examples in cURL, Node, Python and PHP, signature-checking code, and an OpenAPI file.
How it works
Up and running in three steps
- 1
Create an API key
Generate it in Settings and keep it on your server.
- 2
Send a template
Call POST /v1/messages from your code on the event that matters.
- 3
Listen for webhooks
Receive message.status and message.received events, verify the signature, and update your records.
FAQ
API and webhooks: questions answered
Is there a rate limit?
Yes. Each API key has a per-second limit, and batch calls let you send many messages in one request. Exceeding it returns a clear error with how long to wait.
How do I know a webhook is really from Engage?
Every webhook is signed with an HMAC. Our docs include verification code in Node, Python and PHP.
Can one key be restricted to one number?
Yes. A key can be tied to a single WhatsApp number so it cannot use any other.
Try api and webhooks with your team
Leave your number and our team will walk you through it, and help you connect your WhatsApp account.