For automation, CRM and SaaS resellers
You sell automation, CRM or customer service and need one WhatsApp number per client, created without manual work and delivered with your client's look. Create instances by API, store the client identifier on each one, send the connection link and deliver a portal with their name, logo and color. Your cost is R$15 per active number per month, with no per-message fee and no volume tier, so your margin is a multiplication. Create the account and test it with one client.
Updated on
Creating each new client's number by hand does not scale, and onboarding becomes the bottleneck of your growth
You need to know which client owns each instance and receive events already identified, without keeping a parallel table
The end client wants to see their own brand, not the vendor's, on the screen where they connect the number and follow results
When a number drops, reconnection support lands on you, and you become a QR code attendant
A per-message fee or a price that rises with volume makes it impossible to close a fixed price in your monthly plan
Building and maintaining the connection infrastructure yourself takes time that should go to selling and delivering
A POST to /api/v1/instances creates the number. Store the client identifier and plan in the metadata field. Every webhook from that instance arrives with that metadata, so you know whose event it is.
On each instance you set the name, logo and accent color, and you can remove Powered by. The client portal and the connection link for that number then use their brand.
You send the connection link and the client scans the QR code with no account to create. If the number drops, they reconnect in the portal without opening a ticket with you.
Your cost is R$15 per active number per month, prepaid. When you remove the number of a client who left, its billing stops. The selling price and the plan you offer are yours.
What to use
The ZapZap modules that solve exactly the pain points of this scenario.
Create, list, query and remove instances by API, with key and secret, plus the metadata field that travels with the instance and comes back in every webhook. It is what lets you provision a new client without touching the dashboard.
Name, logo, accent color and the option to remove Powered by in the client portal and the connection link. It is your client's brand on their screen, set once per number.
The client connects the number, sees leads and sales and reconnects the QR code without an account and without depending on you. You choose the sections each portal shows.
Real-time events to your system, identified by the metadata. It integrates with your CRM, with n8n or with the back end you already have.
Examples to get started. Personalize them with the customer's name and your business details.
Hello! Here is the link to connect [Client Company]'s WhatsApp to the platform. Open it on the phone that has the number, scan the QR code and you are done. Any questions, just message me.
[Client Company]'s number has disconnected. To get back to answering, open your dashboard, tap reconnect and scan the QR code again. It takes less than a minute.
Your results portal is live: [link]. There you see today's leads, confirmed sales and the month chart. The access password comes in a separate message.
When you resell, you handle third-party data and usually act as a processor under LGPD: keep a data processing agreement with each client, make clear who is the controller and record contact consent. ZapZap is an unofficial solution and the client must know, in writing, that the number can be limited or blocked.
No. Your client's brand (name, logo, color and removal of Powered by) applies to the client portal and the connection link of each number. The main dashboard and the API remain ZapZap's, and there is no custom domain. If you need to hide the vendor everywhere, this is not the solution.
When you create the instance by API, store the client identifier and plan in the metadata field. The metadata comes back when you query the instance and in every webhook, so your system identifies the client without an extra lookup.
No. It is R$15 per active number per month, prepaid, with no per-message fee, the same math for 5 or for 500 numbers. Creating an instance has a one-time activation fee (currently R$3 per number, which you confirm first with GET /instances/cost).
The pricing page does not publish a limit. If your operation will go beyond a few dozen numbers, talk to support before migrating clients so capacity can be agreed.
No. They connect the number through the connection link and follow results in the portal, which opens by link or by number and password. You are the one with the account who pays the balance.
ZapZap is an unofficial API and WhatsApp can restrict or block numbers, even with good practices. Community warm-up, a human pace and consent reduce the risk but do not remove it. Put this in writing in your contract with the client.
Create your account, connect a number in minutes and test the API with warm-up and anti-ban. R$15 per active number/month, prepaid, no lock-in.
