WhatsApp API Without Meta Approval

WhatsApp's official Business Platform requires a Meta Business account, app review, and a verification process that can take days to weeks. Wasaas doesn't use that platform. Instead, you connect a regular WhatsApp number the same way you'd link WhatsApp Web on a computer: open WhatsApp on your phone, scan a QR code shown in the Wasaas dashboard, and the number is connected. There is no Meta Business account to create and no app to submit for review.

Partially. Meta's official WhatsApp Business Platform (Cloud API) has relaxed its own onboarding: a developer can now connect a number and start sending business-initiated messages before completing Business verification, capped at a limited number of conversations per rolling 24 hours. Full Business verification — documents, review, a waiting period — is still required to raise that cap toward production volume.

Wasaas's model is different in kind, not just in speed: there is no cap tied to a verification status at all, no document review, and no separate Meta-side approval step to unlock higher volume — plan limits (see pricing) are the only ceiling. The tradeoff, covered above, is that a Wasaas-connected number is subject to WhatsApp's ordinary consumer terms and spam enforcement rather than the compliance framework of the official Business Platform.

1. Create a Wasaas account and start the 7-day trial — no credit card required.
2. Go to Sessions → Add Session and a QR code appears.
3. On your phone: WhatsApp → Linked Devices → Link a Device, and scan it.
4. The session status changes to connected, and you can send your first message via the API or the built-in tester.

This is the same linked-device mechanism WhatsApp Web itself uses — Wasaas hosts the session so you can send and receive through a REST API instead of a browser tab.

Because you connect a regular WhatsApp number rather than the official Business Platform, that number stays subject to WhatsApp's normal terms of service and its own automated spam-detection systems. Sending unsolicited bulk messages, messaging people who haven't opted in, or sending at a pace that looks automated can get a number restricted — this is WhatsApp's enforcement, not something Wasaas controls or can override.

No unofficial, QR-connected WhatsApp API provider — Wasaas included — can honestly guarantee a number will never be restricted. Wasaas's bulk sending paces messages with a randomised delay specifically to reduce this risk, but it cannot eliminate it. If you need a contractual delivery guarantee or are sending very high volumes to non-opted-in contacts, the official Business Platform's compliance model is the more appropriate fit — see the comparison below.

A REST API for text, image and document messages, bulk sending, and programmatic chatbot flows — the same product documented on the API reference. Example first call, once a session is connected:

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!"
  }'