Full REST API to send messages, manage contacts, run bulk sends and invoke AI. Real-time bidirectional webhooks for every event (message received, new lead, tag changed). SDKs in Node and Python. Complete documentation.
3 typical problems when building custom WhatsApp integrations — and how Wazzap solves them.
Building on Meta's official API requires a BSP, Business Manager verification, pre-approved templates, the 24h rule, and per-message cost. Complex technical setup + endless restrictions.
Standard REST API with Bearer token auth. POST /messages and you send. No BSP, no templates, no 24h rule. Technical setup in 30 minutes vs 2-4 weeks.
Community JS/Python libraries for WhatsApp break often (WhatsApp Web changes), have poor docs, and frequent abandonment. Your team ends up maintaining more code than they wrote.
SDKs built and maintained by us. npm install wazzap-sdk or pip install wazzap and you start. Full types, examples, active support.
Cheap solutions use polling (check every N minutes). For apps that need to respond instantly to a message, the delay kills UX and conversion.
Every event (message received, new lead, tag changed, bulk completed) fires a push webhook to your URL in under 1 second. HMAC signing for security. Automatic retries.
Endpoints for everything: /messages, /contacts, /groups, /campaigns, /ai/chat, /templates, /files. Interactive Swagger-style documentation with curl, Node, Python examples.
Push events to your URL: message.received, contact.created, tag.added, campaign.completed, ai.handoff. HMAC signing to validate origin. Automatic retries with backoff.
SDKs maintained by us with full types (TypeScript), autocomplete, error handling. const msg = await wazzap.messages.send({...}). Start integrating in minutes, not hours.
Bearer token authentication with granular scopes (read-only, send-only, admin). Protected rate limiting. HMAC signing on webhooks. Per-request logs for auditing. SOC 2 ready.
No BSP, no Meta templates, no fragile community libraries.
In Wazzap, Developers section, you generate an API key with the scopes you need (read, send, admin). You paste it into your app or environment variables. 2 minutes.
npm install wazzap-sdk or pip install wazzap. You follow the documentation for your first use case (send message, receive webhook, manage contacts). 15-30 min to get something into production.
You point your webhook URL to your app. Every event fires a POST with HMAC signature to validate. Automatic retries. Logs visible in your Wazzap panel.
"I needed to connect WhatsApp to our custom CRM. I tried 3 community libraries that broke. The Wazzap API was plug-and-play — first endpoint running in 30 minutes."
"We built our own notifications platform on top of the Wazzap API. We process 50k events/day with no downtime. The docs + SDK quality saves weeks of development."
"What I liked most: the API is honest. If you ask for X, it gives you X. No weird abstractions, no hidden coupling. As a developer, it feels well built."
3 ways to integrate WhatsApp into your custom app — compared with data.
| Wazzap API + Webhooks | WhatsApp Cloud API (Meta) | Community libraries (whatsapp-web.js) | |
|---|---|---|---|
| Setup time | 30 minutes | 2-4 weeks (Meta + BSP) | 1-3 days |
| Cost | $19/mo platform | $0 + $0.005-0.15 per message | $0 + your hosting |
| Per-message cost | $0 — unlimited | $0.005-$0.15 | $0 |
| Meta templates required | No | Yes | No |
| Maintained official SDKs | ✓ Node + Python | ✓ Multiple languages | Variable |
| Real-time webhooks | ✓ <1s + HMAC | ✓ <1s | Variable |
| Stability / uptime | 99.9% (8+ months) | 99.9% (official) | Variable (community) |
| Built-in anti-ban | ✓ Spintax + proxies | N/A (official) | ✗ You build it |
| Support | Wazzap team | BSP intermediary | GitHub issues |
When to use WhatsApp Cloud API directly? If your product needs Meta's verified badge for regulatory compliance. For everything else (custom apps, internal integrations, SaaS tools), Wazzap API wins on cost, speed and freedom.
All these integrations are included in the same plan.
REST API + webhooks + Node and Python SDKs + documentation + granular scopes — no add-ons, no per-message fees.
See plans and pricingStandard Bearer token (Authorization header). API keys have granular scopes: read-only (query data), send-only (send messages), admin (everything). You can generate multiple keys with different scopes for different use cases.
Yes, generous ones. Standard plan: 60 requests/minute, 5,000/hour, 50,000/day. For larger volumes we have enterprise plans. Rate limits apply per API key, response headers show remaining quota.
Yes. Every webhook includes a X-Wazzap-Signature header with HMAC-SHA256 of the body signed with your secret. You validate with your SDK (included) or manually — this prevents anyone from spoofing webhooks to your URL.
Automatic retries: 5 attempts with exponential backoff (1s, 5s, 30s, 5min, 1h). After the last failure, the event stays in Wazzap's log for 7 days so you can reprocess it manually.
Official SDKs: Node and Python. For other languages (PHP, Ruby, Go, Java, .NET), the REST API is standard — you can consume it directly with any HTTP client. We have guides for the most common languages.
Yes. Every account can create "sandbox" sub-accounts with your own test numbers. Messages work for real but stay flagged — useful for testing without contaminating production.
Yes, 15+ events: message.received, message.sent, message.delivered, message.read, contact.created, contact.updated, tag.added, tag.removed, campaign.started, campaign.completed, ai.handoff, group.joined, conversation.assigned, etc. Full documentation in developer docs.
7 days free, API + SDKs included, complete documentation.
Start free trial