REST API with 150+ documented endpoints, webhooks and ready docs. Prepaid: you pay per number, not per message.
From --/number/month + one-time activation fee.Prepaid.No fixed monthly fee
Why ZapZap for B2B SaaS
With an official BSP, every template goes through approval. With ZapZap you connect a regular number by QR code, warm it up in the community and start sending.
Deterministic pool, community warm-up, automatic retry. Your API hands WhatsApp off to ZapZap and focuses on the core product.
Your customer never sees the raw credential. You call /api/v1 with your key and ZapZap proxies with sanitization. Auditable.
The problem
Illustrative example
A customer wants WhatsApp notifications. You look into an official BSP: template approvals, per-message pricing and a contract.
Illustrative example
The cheap option: a generic API that goes down every week. Your product's SLA tanks and support has nothing to work with.
Illustrative example
You integrate, it works in dev. In production, after 200 messages, the number is blocked. Your customer sees a 500 error coming from your API.
My WhatsApps
3 instances . 2 online
Sales Support
+55 11 9 8765-4321
Marketing
+55 21 9 9876-5432
Orders Bot
+55 11 9 1234-5678
Messages today
1,847
Connected
2/3
Balance
R$ 78.40
How it works
Every part built to last at scale.
150+ REST endpoints. Secure proxy: your code only sees the API Key and Secret, and the instance token stays on the backend. Works with n8n, Zapier or any HTTP tool.
// Send a text message
const response = await fetch(
`https://api.zapzapapi.com/v1/${id}/send/text`,
{
method: 'POST',
headers: { 'x-api-key': apiKey },
body: JSON.stringify({
phone: '5511999999999',
message: 'Hi! Your order has been approved'
})
}
);
// Response
{ "status": "sent", "id": "msg_abc123" }
A deterministic hash per contact. Each customer reaches the same instance every time, even with 10 numbers in the pool. The conversation picks up where it left off.
Your numbers exchange automatic messages with other businesses' numbers in the pool, at varying intervals, to build a usage history before going live. It lowers the risk, with no guarantee that the number won't be restricted.
The monitor checks your instances every minute. If one drops, you get a WhatsApp message with a link to reconnect. No need to open the dashboard.
Number disconnected
Support SP went offline. Reconnect now.
Low balance
You have R$ 15.00 left. Top up so nothing pauses.
Daily report
1,847 msgs sent. 2 instances online. 3 campaigns active.
Every instance already has AI available. Turn it on in seconds: it keeps context between messages, transcribes audio and reads images. When it does not know, it hands off to a human.
Import the CSV, pick the pool. Variable delay between sends and per-contact variables. Send only to people who agreed to receive, and honor opt-out requests.
5511988776655
Hi, I'd like to know about...
Sales Support
Number connected successfully
5521977665544
Your order #1847 has...
Highlights
Community warm-up
On by default in every instance, with rest hours per number.
Built-in conversational AI
Automatic support set up in the same dashboard as your instances.
Per-instance pricing
Prepaid balance, no lock-in contract.
Protected access
The provider's master token stays on the server only and never reaches your browser.
ZapZap charges per connected instance, with a prepaid balance that does not expire. The price does not vary with conversation volume, and you connect the number in minutes.
Calculator
Adjust the numbers to your scenario. Results update in real time.
Estimated monthly difference
R$ 12,250
Monthly ZapZap cost
R$ 250
With the cost you entered, the estimated difference is R$12,250 per month, before AI usage, if you use it.
Create accountA clean REST API, docs at /docs, first request in minutes.
Prepaid · No contract · Balance never expires