The Waplify API, and the webhooks that answer back

Two halves of the same thing. The API is how your software talks to Waplify. Webhooks are how Waplify talks back. One key, and both are included on every plan.

Read the API docs Sign up free

Full reference, request examples and a Postman collection in the docs.

Your software on the left calling the Waplify API in the middle, the message arriving in a WhatsApp chat on the right, and a return arrow carrying the delivery event back to your server

The short answer

What is the Waplify API?

The Waplify API is a REST API that lets your own software send WhatsApp messages and manage contacts, campaigns and conversations, without anyone opening the dashboard. Waplify webhooks are the other direction: Waplify posts to your server the moment a message is delivered or read, a customer replies, or a chat is assigned. Together they keep your system and your WhatsApp account in step.

You call the API

Your code sends a request. Waplify does it and answers.
Webhooks call you

Something happens on WhatsApp. Waplify posts it to your URL.
One key for both

Created once under Developers. No separate plan, no per-call fee.

The API

What you can do with the Waplify API

Four things. The full reference is one click away.

Send messages

An approved template, or a free-form reply inside an open conversation.
Run campaigns

Create a broadcast, send it in the background, read the delivery stats back.
Manage contacts

Create, list, fetch and delete contacts, and build the groups you send to.
Assign chats

List your agents, then assign, unassign or reopen a conversation.

The webhooks

What Waplify tells your server

Eleven events, and they answer three questions. Payloads are in the docs.

Did it arrive?

Sent, delivered, read and failed, per message, as it happens.
Did they respond?

Inbound messages, replies to your sends, and quick-reply button taps.
Who is handling it?

Chats assigned, resolved and reopened, so your CRM can mirror the inbox.

Every endpoint and every payload, in the docs

Full reference, request examples and a ready-made Postman collection.

Open the API docs Book a demo

How it works

Three steps

The key takes a minute. The rest is one request.

Create a key

Developers, then API. The key starts with wapl_ and is shown once.
Call an endpoint

Send it as Authorization: Bearer to server.waplify.io, under /api/v1/.
Add a webhook

Developers, then Webhooks. Add your URL and pick the events you want.

FAQ

API and webhook questions

1. Can I send any message I want through the API?

Not quite, and this is the rule to know before you write anything. A message your business STARTS has to use a template Meta has approved. Free-form text only works inside the 24 hours after a customer messages you, which is the window the reply endpoints are for. That is a WhatsApp rule on the Official Business API rather than a Waplify limit, and it is what keeps a sending number healthy.

2. What is the difference between the API and a webhook?

Direction. You call the API when your software wants Waplify to do something, like send a message. A webhook is Waplify calling you when something happens, like that message being delivered or the customer replying. Most integrations use both.

3. How do I authenticate?

With an API key sent as a Bearer token. Create one under Developers, then API; it starts with wapl_ and is shown only once. The base URL is https://server.waplify.io and every endpoint sits under /api/v1/. Full detail in the authentication guide.

4. Which events can a webhook send me?

Eleven, covering message delivery, inbound messages and replies, button taps, and assignment in the shared team inbox. The events reference lists every one with its payload.

5. What if my server is down when an event fires?

Waplify retries. You set the retry count per endpoint, from 0 to 10, and the request timeout, from 1 to 30 seconds. You can also set a signing secret so your server can verify a payload really came from Waplify.

6. Do I need the API to connect my CRM?

Usually not, and there may already be a connector: IndiaMART and Google Sheets are built and maintained. If you only want your CRM to start a WhatsApp conversation, use the Webhook trigger on a chatbot flow: your CRM calls a URL, the flow runs, and you write no code. Reach for the API when you want to send, read and manage from your own software.

7. Is there a Postman collection?

Yes, and it is the fastest way to make a real request. It ships pre-configured with the base URL and Bearer auth, so you set one variable and send. Download the collection, or import it by URL from the API overview. There is no language SDK: the collection plus the reference is what exists today.

8. How do I know when something changes?

The changelog records what shipped and when, so you can check it before an upgrade rather than finding out from a failing call.

9. Is it included on my plan?

Yes. Waplify plans differ by billing period, not by feature, so the API and webhooks are not behind an upgrade. See pricing.

Limited Time Deal