WhatsApp
messaging API

Connect a number you own, send messages over HTTP, and receive replies through signed webhooks.

Independent WhatsApp Web connectivity. A phone authorization is required.

TurbineWhats.appWhatsApp

Send a message over HTTP

Edit the example request and copy it into your server-side integration. A scoped token and connected session are required for a real send.

Authentication: Scoped Bearer tokens
Response: Queued message ID
Events: Signed HTTPS delivery

POST/api/v1/messages/textRequest example

Message text

Edit the example, then copy the request into your server-side integration.

curl --request POST 'https://turbinewhats.app/api/v1/messages/text' \
  --header "Authorization: Bearer $TURBINEWHATS_TOKEN" \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: order-1042-confirmed' \
  --data '{
  "channel_id": "1d848fa6-b0c2-4d28-b870-09f44d750d93",
  "to": "14155550123",
  "body": "Your order is confirmed."
}'

Supported operations

The public API supports the operations below. Session access and sending allowances are checked for every account.

Text messages

Send to individuals, or groups on paid access. An idempotency key identifies each request.

send

Media and polls

Send images, audio, video, PDFs, stickers and polls through paid, quota-checked operations.

send

Session management

Create a session, retrieve its pairing QR code, check status, start, stop, or delete it.

manage

Group administration

Create groups, manage participants and settings, share invite links, and handle membership requests.

manage

Account data

Read contacts, chats, and groups available to the connected account.

read

Message status

Read queued, sent, delivered, read, rejected, or uncertain states by message ID.

read

The current send API does not accept group IDs, remote media URLs, audio, video, or arbitrary document formats. Review the full endpoint reference.

Connecting a number

A session links a WhatsApp account to your workspace. The account owner authorizes that connection from their phone; creating a session alone does not authorize sending.

Verify your TurbineWhats.app email and create a session.
Open the session’s QR code when preparation finishes.
Scan it using WhatsApp → Linked devices → Link a device.
Wait for ready status before queuing messages.

Session states and lifecycle

Session lifecycleExample

Order notifications

ready

1d848fa6-b0c2-4d28-b870-09f44d750d93

The authorized connection can accept sends within its plan allowance.

Owner: This workspace
Authorization: Phone QR scan
Lifecycle access: manage scope

Pairing and lifecycle reference

API access and events

Limit each integration’s permissions, protect its token, and verify incoming webhook deliveries before acting on them.

API key permissionsExample

readRead sessions and message statessendQueue text and paid-plan mediamanageControl connections and retrieve QR codes

Selected permissionsread, send

Session binding and revocation

Keys with explicit permissions

Choose read, send, or manage access. Bind a key to one session when it does not need the rest of your workspace. Tokens expire after 90 days and can be revoked immediately.

Webhook verificationLocal example

{
  "id": "fce4e0cb-9ee9-4f74-a5f4-a8851facf045",
  "type": "message.sent",
  "data": {
    "id": "b4829d81-353f-4821-ae99-77adeab896ce",
    "channel_id": "1d848fa6-b0c2-4d28-b870-09f44d750d93"
  },
  "created_at": "2026-11-14T10:00:00.000Z"
}

Change the signed body

Signing guide

Verification runs in your browser; no event is sent.

Signed event deliveries

Add up to three public HTTPS destinations. Verify the signature over the exact request body and deduplicate event IDs. Failed deliveries receive bounded retries.

Queueing and delivery

HTTP 202 confirms that a message entered the queue. It does not confirm that WhatsApp or the recipient received it.

Delivery states and retries

Repeated request: The same key and payload return the existing message, without another allowance reservation.
Interrupted dispatch: An uncertain send is marked for review and is never automatically sent again.
Delivery receipts: Delivered and read states depend on receipts available from WhatsApp and the recipient’s settings.

Plans and trial limits

Prices and sending allowances come from the plan catalog. New sends pause at the applicable limit; there are no automatic overage charges.

Standard

$50USD / month, before tax

Connected sessions: 1
Messages per month: 10,000
Messages per day: 500
Sends per minute: 10

Create account

Three-day trial

One session and 50 text messages total, with a maximum of 20 per day and three per minute. Only your linked number or support-approved test recipients can receive trial messages. Email verification is required; no card is needed.

Allowance windows and counting rules

Connection requirements

TurbineWhats.app uses an independent WhatsApp Web connection. It is not affiliated with WhatsApp or Meta, and it does not provide an official WhatsApp Business Platform API.

WhatsApp can require relinking, change its protocol, or restrict an account. No delivery-time guarantee or uptime SLA is published. Keep an alternative channel for authentication, emergency alerts, and other critical messages.

Send only expected messages to consenting recipients. Spam, scraped lists, unsolicited campaigns, and attempts to evade limits are prohibited.

Service model Terms

WhatsAppmessaging API