Skip to content

WhatsApp messaging API

Send WhatsApp. Read the reply.

One endpoint to send, a signed webhook the moment somebody answers, and an inbox for whoever is going to type back.

No card, and nothing to install.

POST /v1/messages · 202 Accepted
$ curl https://sendbu.com/v1/messages \
    -H "Authorization: Bearer sk_live_…" \
    -H "Idempotency-Key: order-8842-shipped" \
    -d '{ "channel_id": "6b1f0c4e-9a2d-4f77-bd31-0c5a…",
          "to": "+15551234567",
          "type": "text",
          "text": { "body": "Your order has shipped." } }'

< 202 Accepted
  { "id": "0f9c7a55-3d84-4b1e-9a60-27ce1f0b4d93",
    "status": "queued" }
Two-waySend from your code and read the reply back — as a signed webhook, from /v1, or in the Inbox.
202Queued, never pretending to be delivered. The outcome arrives as a webhook.
IdempotentA key is required on every send, so a timeout on your side never becomes two messages on theirs.

The half that is usually missing

A reply is a message too.

Most WhatsApp APIs are a send button. When somebody answers, the answer has to land somewhere — in your code as an event, and in front of whoever is going to type back.

  • It arrives as an event. message.received carries the sender, the text and WhatsApp’s own timestamp — not an id you have to fetch.
  • It is readable afterwards. GET /v1/messages and /v1/conversations page through everything either way, so a missed webhook is not a lost message.
  • Somebody can answer it. The Inbox in the panel is a real reply box, and a support agent does not need an admin account to use it.

Without writing any of it

Your shop can send for you.

Most of what a business wants from WhatsApp is not a message it types. It is an order confirmation, a shipping notice, a reminder, an answer at eleven at night. None of those should need a server of yours.

  • Shopify and WooCommerce, natively. Paste a URL into their webhook settings and an order marked fulfilled becomes a WhatsApp message with the tracking number. We verify their own signature and read their own payload.
  • Anything else, through one endpoint. WordPress without a shop, Zapier, Make, n8n, a cron job, your own backend — sign a small JSON body and we send it.
  • Campaigns, paced. One template to everybody carrying a tag, at one message a second — because an account that sends a burst of identical messages gets banned, and the ban lands on your number.
  • Opt-out is a column, not a promise. Somebody who replies stop is recorded and left out of every campaign, without anybody remembering to.
  • An answer when you are shut. Opening hours in your own timezone, and canned answers for the words people actually send — once per person, never to somebody who asked to be left alone.
  • A shared inbox. Take a conversation, close it, filter to yours. So two people stop answering the same customer.

What is not built yet

Official numbers, switched on. Meta’s Cloud API is built — signup, sending, receiving — and waits on our Meta app; until then a channel is a phone of yours holding the session. Payments need Stripe keys. Paying through Stripe is built and switches on once a deployment’s Stripe keys are set; where they are not, a plan is set by hand.

Everything else on this page runs in production. The reference keeps the same list, and is written from the code that serves it.

Create the account. Mint the key.

No card. Mint a key, pair a number from the panel, and your first POST /v1/messages goes out from it.