Wamafy API
What people build with it
- Order updates, OTPs and appointment reminders sent from a shop, ERP or booking system. See Send a template message.
- Replies to customers, with text, buttons or files, while a conversation is open. See The 24-hour window.
- A CRM that pushes its contacts and tags into Wamafy as they change. See Create or update a contact.
- Delivery and read tracking in your own reports, by looking a message up or through the status webhook.
- Tickets or alerts raised when a customer writes in, from the message.inbound event.
Base URL
Every path in these docs is relative to:
https://api.wamafy.com/api/v1/publicRequests and responses
Send JSON with Content-Type: application/json, except file uploads, which are multipart/form-data. Every response has the same envelope. A successful one carries data:
{
"success": true,
"data": {
"messageId": "wamid.HBgM...",
"status": "sent"
}
}A failed one carries error, with a code you can branch on and a message you can show or log:
{
"success": false,
"error": {
"code": "NO_OPEN_CONVERSATION",
"message": "No open conversation with this contact. Send a template to start one."
}
}Where to start
The Quickstart takes you from a new key to a delivered message in a few minutes. After that, All endpoints lists everything the API can do.
If you work in Postman or generate clients, download the Postman collection or the OpenAPI file.
Help
Stuck on something these pages do not answer? Write to hello@wamafy.com with the endpoint, the request and the response you got. The request log in your dashboard shows every call your key made, which usually explains the problem.