REST API
WhatsApp REST API
Every Wasaas SDK is a thin wrapper around one plain REST API: JSON over HTTPS, authenticated with a single API key. If your language doesn't have an SDK, this is everything you need to call it directly — the Node.js and PHP clients make exactly these same requests.
Base URL and authentication
All requests go to https://wasaas.org/api/v1, authenticated with an API key from the dashboard in the Authorization header. Keys are prefixed wsa_; a missing or invalid key returns 401.
Authorization: Bearer wsa_your_api_key
Content-Type: application/jsonResources
A small, fixed set of endpoints — not a sprawling API surface to learn:
| Endpoint | What it does |
|---|---|
| GET /api/v1/sessions | List connected WhatsApp sessions and their status |
| POST /api/v1/messages | Send a text message |
| POST /api/v1/messages/image | Send an image by URL, with an optional caption |
| POST /api/v1/messages/document | Send a document as base64 — no public hosting needed |
| POST /api/v1/messages/bulk | Send to up to 500 recipients in one call, with paced delivery |
| POST /api/v1/check-number | Check whether a phone number has WhatsApp before you send |
| /api/v1/chatbot/flows | Create and manage keyword-triggered chatbot flows |
A first request
Every send needs a session ID — visible in the dashboard once you scan a session's QR code, or from GET /api/v1/sessions — and a recipient in international format without a leading +.
curl -X POST https://wasaas.org/api/v1/messages \
-H "Authorization: Bearer wsa_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"session_id": "customer-5-1",
"to": "966501234567",
"message": "Hello from the Wasaas REST API!"
}'
# { "success": true, "to": "966501234567", "status": "sent" }Errors
Non-2xx responses return a JSON body with an error field. The status codes that matter in practice:
401— invalid or revoked API key404— the session ID doesn't belong to this account429— a quota is exceeded (messages, sessions or API calls for the current period)500— the WhatsApp session itself failed to send
What this API does not do
There is no outbound webhook delivery — nothing POSTs events to a server you control, for incoming or sent messages. Supported message types are text, image and document only; audio, location pins and interactive buttons are not available. This is an unofficial, QR-connected integration, not Meta's official Business Platform — see what that means in practice.
Pricing
Every plan includes full access to this API; higher plans raise the message, session and API-call allowances. See WhatsApp API pricing for current limits.
Where to go next
- WhatsApp REST API documentation — the full reference — every field, header and error code
- WhatsApp API for developers — the full picture: SDKs, setup flow and who this fits
- WhatsApp API for Node.js — a typed client over this same API
- WhatsApp API for Laravel — a PHP client over this same API
- WhatsApp bulk messaging API — the pacing and quota behaviour behind /messages/bulk