For developers, freelancers & agencies

WhatsApp API for Developers

A REST API for WhatsApp messaging that you connect in minutes, not weeks: an API key, a QR-scanned session, and a handful of endpoints for text, images, documents and bulk sends. No Meta Business account, no app review, no verification queue — built for the integration you're shipping this week, not a six-month enterprise onboarding.

Who this is for

Wasaas is built for the developer shipping a WhatsApp integration into a real project — a freelancer adding order notifications to a client's store, a small agency wiring WhatsApp into several clients' stacks, or a solo founder who needs messaging working today. It is not a fit if you need Meta's official compliance framework, a contractual delivery SLA, or very high volume to non-opted-in contacts — see the honest tradeoffs below.

The 3-step flow, end to end

  1. Create an account and get an API key, prefixed wsa_, from the dashboard.
  2. Connect a WhatsApp number: Sessions → Add Session shows a QR code. Scan it from WhatsApp → Linked Devices on your phone, the same way you'd link WhatsApp Web.
  3. Call the API with the session's ID and your API key. Every send, in every language below, needs exactly those two things.
bash
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 Wasaas!"
  }'

Pick your stack

What you get

  • Text, image and document messages, plus a bulk-send endpoint for campaigns.
  • Multiple sessions per account — one WhatsApp number per client, team or project.
  • Number validation before you send, to keep failed sends out of your logs and quota.
  • Keyword-triggered chatbot flows you can also manage over the API.

Honest limitations before you build on this

This is an unofficial, session-based integration, not Meta's official WhatsApp Business Platform. A connected number is a regular WhatsApp account subject to WhatsApp's normal terms and automated spam enforcement — no provider on this model, Wasaas included, can guarantee a number is never restricted.

Outbound webhook delivery to your own server is not available yet — there is no event push for incoming or sent messages today. Supported message types are text, image and document; audio, location pins and interactive buttons are not available. See WhatsApp API without Meta approval and official vs. unofficial for the full picture, including when the official platform is the better fit.

Pricing

Every plan includes full REST API access, API keys and the same endpoints described here — higher plans raise the session, message and API-call allowances. See WhatsApp API pricing for current limits, and start with the free trial before committing to a plan.

Where to go next

WhatsApp API for Developers | Wasaas