Wapito

Try the WhatsApp API without signing up

Pick one of the six calls most integrations start with, fill in the fields, and read the exact request you would send — in curl, in Node.js or in Python — next to the response the endpoint documents. No account, no card and no email address.

No template and no 24-hour window: the message goes out as soon as the send queue releases it.

The token is a placeholder. Nothing is sent from this page — your own token arrives once you create a channel, and the same call then runs for real.

Create a free channel to run it

POST /messages/text

curl -X POST 'https://api.wapito.com/v1/messages/text' \
  -H 'Authorization: Bearer wpt_YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
  "to": "+15551234567",
  "body": "Your order #4182 has shipped."
}'

Example response · 201

{
  "id": "true_15551234567@s.whatsapp.net_3EB0C767D82B0A1E4F2B",
  "chat_id": "15551234567@s.whatsapp.net",
  "from_me": true,
  "from": "15557654321",
  "type": "text",
  "timestamp": 1789459200000,
  "source": "api",
  "text": {
    "body": "Your order #4182 has shipped."
  },
  "status": "sent"
}

What this demo does, and what it does not

Everything on the left is real. The path, the HTTP method, the header and the JSON body are what the Wapito API accepts today, generated by the same code that renders the snippets inside the dashboard and the quick start in the docs — so the call you copy here is the call that will work once you have a token. The only placeholder is the token itself.

Nothing is sent. This page never contacts the API, and no message is sent to the number you type in: the panel on the right is the response the endpoint documents in our OpenAPI specification, with your own values echoed into it so you can see the shape a real answer has. Sending WhatsApp messages from an anonymous public page would be a spam service, not a demo, which is why the only way to run one of these calls for real is to link a number of your own.

What changes when the call is real

Three things. First, the token: creating a channel issues a Bearer token that begins with wpt_, is shown once, and is the only credential the API needs — there is no app id, no app secret and no OAuth dance. Second, the number: a channel is a WhatsApp number you have linked by scanning a QR code or entering a pairing code on the phone, and every call runs as that number. Third, the response is live — a message id WhatsApp generated, a group id you can immediately add people to, a contact check that really asks WhatsApp whether the number exists.

The calls that change something also come back to you as events. When a message is delivered or read, when somebody replies, when a participant joins the group you just created, Wapito posts a signed JSON payload to whatever URL you configured. That is the half of the integration this page cannot show you, and it is usually the half that decides whether an API is pleasant to build on.

Why these six calls

They are the first day of a typical integration, and four of them have no equivalent in Meta's official Cloud API at all. Creating a group, posting a poll, listing the chats a number is already in and checking whether an arbitrary number is on WhatsApp are things the official platform either does not expose or restricts to approved business accounts. Sending a plain text message is in both, but not on the same terms: the official API needs an approved template outside a 24-hour window, and Wapito does not.

  • POST /messages/text — No template and no 24-hour window: the message goes out as soon as the send queue releases it.
  • POST /messages/image — Pass a public HTTPS URL, base64 or a media id; Wapito fetches the bytes and forwards them.
  • POST /contacts/check — Up to fifty numbers per call. Every number checked counts against the daily check quota, found or not.
  • POST /groups — The official Cloud API has no endpoint for this at all — groups are one of the reasons Wapito exists.
  • POST /messages/poll — Polls are a native WhatsApp message type. Votes arrive on your webhook as they are cast.
  • GET /chats?count=20 — A page of conversations, most recently active first — direct chats, groups and WhatsApp Channels.

Before you build on it

Wapito is an unofficial API. It speaks WhatsApp's own protocol rather than going through Meta, which is exactly why the six calls above exist — and it also means WhatsApp can restrict or ban a number it judges to be automated. Nobody, Wapito included, can appeal that on your behalf. Read the anti-ban guide before you point a new number at a contact list, start on the free plan, and treat the first week of a new number as a warm-up rather than a launch.

Anti-ban guide Full API reference Pricing and quotas Getting started

Run it on your own number

Creating a channel takes about a minute: name it, link the number with a pairing code or a QR scan, and the token appears. The free plan needs no card.

Create a free channel