WhatsApp Anti-Ban Guide

Wapito is an unofficial WhatsApp API. It drives a real WhatsApp account through the same protocol the phone and desktop apps use, not through Meta's Cloud API, and that is the whole reason it can create groups, post to Channels and message anyone without a template. It also means WhatsApp can ban the linked number, and no provider — Wapito included — can promise otherwise. This page is the honest version of what that risk is, what Wapito does about it automatically, what only you can do about it, and what happens on the day it goes wrong anyway.

What actually gets numbers banned

Nobody outside Meta knows the exact rules, and the rules change. What follows is what every team that has run linked numbers at volume has seen, in roughly the order of how much it matters.

1. Being reported. The strongest signal by far. When a recipient taps Report or Block and report, WhatsApp receives your recent messages to them. A handful of reports on a young number is enough. Everything else on this list matters mostly because it leads here.
2. Messaging strangers. People who do not have your number saved and did not write to you first are the ones who report. A conversation the other side started almost never gets a number banned, whatever the volume.
3. Volume from a new number. A number that was linked on Monday and sends five hundred messages on Tuesday does not look like a person. WhatsApp expects volume to grow over weeks.
4. Identical content. The same text, the same link, to many recipients in a short time — the shape of a broadcast. Links in a first message are worse still.
5. Adding strangers to groups. Putting people into a group they did not ask to join is the single most reported action there is, and WhatsApp has been tightening the rules around it for years.
6. Machine-like timing. Messages every 200 ms, at all hours, with no "typing…" and no reads on the inbound side.
7. A hollow account. No profile name, no photo, no contacts, no history, freshly bought virtual number, linked from a datacenter IP. Each of these is a small weight on the wrong side of the scale.

Notice what is not on the list: the API itself. Numbers are not banned for being driven by software; they are banned for behaving like spam. A linked number that answers customers who wrote to it can run for years.

What Wapito does automatically

These controls are on for every channel and cannot be switched off — not on Premium, not on request — because they are what keeps the number alive. Their exact numbers are in rate limits; this is what each one is for.

• Send pacing. One queue per channel; each message leaves about 1.5 seconds after the last, plus up to 1.5 seconds of random jitter. A burst of API calls becomes a stream of sends with human rhythm. A producer that outruns the queue gets 429 send_rate_limited rather than a faster number.
• Typing simulation. With typing_simulation: "auto" (or typing_time on a send) the recipient sees "typing…" for a duration proportional to the message, and a reply marks the inbound message as read first — the sequence a person produces.
• The warm-up ladder. A newly linked number may send 50 messages on its first day, 100 on the second, then 200, 350, 500, 750 and 1,000, and only after a week is it bound by the plan alone. The ladder follows the phone number, not the channel, and survives reconnects.
• The cold-send guard. Only so many first messages to strangers per hour — ten in the first two days, twenty for the rest of the first week, then sixty on Premium and twenty on Sandbox. Replies to people who wrote to you are never limited by it. This is the control that turns "reply-first" from advice into a property of the platform.
• Timelock detection. When WhatsApp pauses new reach-outs from a number, Wapito notices, reports it in GET /channel/limits, answers cold sends with 423 reachout_timelocked and lets replies through. You find out from the API, not from a customer.
• One steady connection. A channel holds one session per number and does not reconnect in loops; bulk number checks run at low concurrency; nothing is fetched from WhatsApp that the endpoint you called did not need.
• A proxy per channel on Premium, so a number can keep a consistent, residential-looking exit address instead of sharing a datacenter one.
• The ban detector. The engine's disconnect reasons are watched, and a ban is turned within a minute into a channel webhook event with reason: "banned", a banned status in the dashboard and an e-mail to the account owner. The session is stopped so nothing keeps knocking.
• Offline nudges. A linked device whose phone stays offline too long is eventually unlinked by WhatsApp. Wapito tracks when the phone was last seen and e-mails you before that happens.

What only you can do

Reply first. Design the integration so the customer's message is the trigger: a keyword, a form on your site that ends with "message us on WhatsApp", a wa.me link, a QR code on the receipt. Once they have written to you, you may answer for as long as the conversation lasts, and the cold-send guard never touches you.

Get consent, and keep it. Message people who asked to hear from you, tell them how to stop, and stop when they say so. A "STOP" that is honoured is a report that never happens. This is also what the acceptable use policy you agreed to requires.

Do not run cold outreach. Bulk messages to lists of numbers that have never heard of you are the thing that gets numbers banned, and the thing the platform is built to refuse. If your business depends on unsolicited outreach, the Cloud API with approved templates is the honest tool; see how the two compare.

Respect the pacing. Do not fire a thousand calls and retry every 429 in a tight loop. Feed the queue at the rate the number can send, read GET /channel/limits before a batch, and treat cold_send_limit and reachout_timelocked as instructions, not obstacles.

Warm up before you need to. Link the number a week before the first campaign. Use it from the phone as well: save contacts, join a group, reply to a few people, set a profile name and photo. Wapito's ladder paces the API side; the human side is yours.

Write like a person. Vary the wording, use the customer's name, skip the link in the first message, do not send at 3 a.m. in the recipient's time zone. If a message would look like spam arriving on your own phone, it looks like spam on theirs.

Keep the phone alive. The number is still a phone. Keep it charged, online and occasionally in a human hand; a phone that is off for two weeks is unlinked by WhatsApp whatever Wapito does.

One number, one system. Do not run the same number through Wapito and another tool, or link it to several providers in turn. Repeated re-linking from different places is exactly the pattern an account-takeover check is looking for.

Use a number you can afford to lose. A real SIM with some history is safer than a freshly bought virtual number, and a number that is not your main business line is safer still.

Watch the receipts. A rising share of messages.status events with status: "failed", or inbound messages that suddenly stop, is the number telling you something before WhatsApp does.

When the ban comes

Sometimes it comes anyway. Here is what happens and what to do.

1. The channel event fires with status: "banned" and previous_status: "connected", the dashboard shows the channel as banned, and the account owner gets an e-mail. Subscribe to the channel event from day one so this reaches your on-call, not your inbox.
2. Wapito stops the session. Sends answer 409 channel_not_connected from then on; nothing is queued, nothing keeps retrying against a dead account.
3. On the phone, WhatsApp shows either a countdown — a temporary ban, usually hours to a few days — or a permanent one with a Request a review button. The review is between you and WhatsApp. Wapito has no channel to Meta, no appeal process to run on your behalf, and no way to reverse a decision. Anyone who tells you otherwise is guessing.
4. After a temporary ban ends, the number can be linked again from the Connect tab. Start slower than before: the ladder restarts only if the phone number changes, so it is on you to send at a fraction of the previous volume for a while.
5. After a permanent ban, the number is gone. Move the channel to a new number, which resets the warm-up ladder, and change whatever behaviour led here before you do.

If a customer's number was banned while running through Wapito, delete the channel or link a new number to it; the token, webhooks and settings all survive the switch.

What we will never tell you

You will find providers that advertise "ban-proof" numbers, "anti-ban algorithms" or "official grade" reliability on an unofficial API. There is no such thing. The protocol is the same for everyone, the judgement is WhatsApp's alone, and the only variables are how the number behaves and how quickly you learn when it is in trouble. Wapito's promise is narrower and true: honest defaults you cannot switch off, honest limits that say no before WhatsApp does, and honest signals — the timelock, the receipts, the channel event — the moment something changes.

The long-form guide to avoiding bans goes deeper into the numbers and the reasoning; the acceptable use policy is the contractual version of the same rules.