WhatsApp anti-ban: the complete guide to lowering your number's risk

• The short answer: what anti-ban is and what it is not
• Nothing is 100% safe: what the WhatsApp Terms say
• Why does WhatsApp block numbers?
• How many messages per day can I send?
• How do you warm up a new number?
• Which anti-ban layers exist?
• How do you set the sending pace through the API?
• How do you build a list that does not trigger reports?
• Which signs show your number is at risk?
• The number got blocked: what to do, step by step
• What is the risk by type of use?
• When should you pick the official API?
• Final checklist

This is the main guide of a series. If you want to jump straight to one question, there are focused guides: why WhatsApp blocks numbers, how many messages per day and banned number: what to do. The resource pages are anti-ban, chip warm-up and the warm-up checklist.

Anti-ban means reducing the behaviors that make WhatsApp treat a number as spam. It works by going after causes you control: who receives, at what pace, with what text and from what history. It is not a button, a special SIM or a tool secret. That is why you should be wary of anyone selling anti-ban as a guarantee.

Summary in five points. One: talk to people who expect to hear from you. Two: warm up the number before using it at volume. Three: send at a human pace, with varied text. Four: keep the list clean and respect people who ask to opt out. Five: monitor the number and have a plan B. If your business cannot afford to lose the number, the right answer may be the official API, and the guide explains when.

This is the part many people leave out. According to the WhatsApp Terms of Service (consulted on 10/27/2026), the acceptable use section prohibits, among other things, creating accounts through unauthorized or automated means, and sending impermissible communications such as bulk messaging and auto-messaging. Using the service for anything other than personal purposes requires WhatsApp's authorization. The Terms also say WhatsApp may take action on an account, including disabling or suspending it, and may modify, suspend or terminate access at any time and for any reason.

In plain English: an unofficial API, like ZapZap, connects your number to WhatsApp Web on a server, and that use is not covered by the Terms. That means WhatsApp can limit or ban the number, the risk exists from day one and no practice brings it to zero. Warm-up, pace and a clean list change the probability, not the nature of the risk. ZapZap does not promise your number will not be blocked, and our acceptable use page describes what is and is not allowed on the platform.

What this means in practice. Use a number you can afford to lose, or at least have a spare. Do not put a business's only revenue channel on a single number. Do not message people who did not ask to hear from you. If your case requires an approved channel, use the official API. The choice between the two is in official vs unofficial API. This text is informational and does not replace legal advice.

WhatsApp does not publish its criteria. What is known comes from the Terms, from operators' experience and from observed behavior. The most commonly cited triggers are patterns, not a single rule. Among them: many reports from recipients, many blocks by recipients, volume sending from a number with no history, identical messages in sequence, sending to many numbers that never interacted with you and a high rate of nonexistent numbers on the list.

There is also blocking with no apparent cause: WhatsApp's own verification sweeps, a SIM with a bad history from a previous owner and policy changes. That is why the account should be seen as managed risk, never as a guaranteed asset. The guide focused on causes is why WhatsApp blocks numbers.

There is no safe number published by WhatsApp, and any 'daily limit' table you find is individual experience, not a rule. That is why this guide does not give a number. The real limit depends on the number's history, on who receives, on how they react and on the content. Two identical numbers with the same volume can end up in different places.

What works better than a magic number is a behavior rule. Start small with contacts who have already talked to you. Raise the volume in steps, only after you see replies and no complaints. Spread sending across the day instead of concentrating it. Stop and investigate at the first sign of falling replies, rising reports or undelivered messages. And prefer conversations (question and answer) to block announcements.

The API also helps you see. The new conversation limits endpoint checks the limit WhatsApp allows you to start from the number (the account tier), useful for tracking warm-up. Treat it as an indicator, not as permission to go up to the ceiling. The guide focused on volume is how many messages per day.

Warming up means giving the number a usage history similar to a person's before putting it into operation. The process, in broad strokes: complete the profile (name, photo, about), use the number for real in conversations with contacts who reply, raise activity in steps over days and only then add automations. Avoid starting with a blast on day one, which is the classic picture of spam.

Warm-up lowers the risk; it guarantees nothing. A warmed-up number that blasts a cold list can still be reported. Nor is there a magic day count. The detailed plan by phase is in the chip warm-up guide, on the warm-up page and in the warm-up checklist, including a description of the community warm-up that ZapZap offers.

The platform takes care of the technical side (send queue, typing indicator, delay, proxy), and you take care of content and audience (who, when, what). No layer makes up for the absence of another: a perfect delay with a bought list still draws reports.

On proxy: the API lets you choose between a service-managed proxy, your own proxy and no proxy (set proxy). It defines where the instance exits to the internet. It is not a shield against bans, and a bad proxy can hurt stability, so only change it if you have a reason.

Three concrete adjustments. The first is the delay between messages in the instance queue, in seconds, with a minimum and a maximum (set delay). Variable values within the range avoid a pace that is too regular. The second is the automatic typing indicator on text sends, which is on by default and proportional to message length. The third is validating numbers before sending with check number.

Which delay range to use depends on your case and on the number's history, and there is no universal value. Start conservative and only shorten it if everything is healthy. The examples below show the endpoints, not values recommended for you.

BASE="https://api.zapzapapi.com/api/v1"
H1="x-api-key: $ZAPZAP_API_KEY"
H2="x-api-secret: $ZAPZAP_API_SECRET"

# atraso mínimo e máximo (segundos) entre mensagens da fila
curl -X POST "$BASE/$INSTANCE_ID/instance/updateDelaySettings" -H "$H1" -H "$H2" \
  -H "Content-Type: application/json" -d '{"msg_delay_min": 8, "msg_delay_max": 25}'

# quais números da lista existem no WhatsApp
curl -X POST "$BASE/$INSTANCE_ID/chat/check" -H "$H1" -H "$H2" \
  -H "Content-Type: application/json" \
  -d '{"numbers":["5511999999999","5521988888888"]}'

# limite atual de novas conversas do número
curl "$BASE/$INSTANCE_ID/instance/wa_messages_limits" -H "$H1" -H "$H2"

const BASE = "https://api.zapzapapi.com/api/v1";
const ID = process.env.INSTANCE_ID;
const headers = {
  "x-api-key": process.env.ZAPZAP_API_KEY,
  "x-api-secret": process.env.ZAPZAP_API_SECRET,
  "Content-Type": "application/json",
};

const saudacoes = ["Olá", "Oi", "Bom dia"];
const escolhe = (lista) => lista[Math.floor(Math.random() * lista.length)];
const pausa = (ms) => new Promise((r) => setTimeout(r, ms));

async function main(contatos) {
  // 1) só números que existem no WhatsApp
  const r = await fetch(BASE + "/" + ID + "/chat/check", {
    method: "POST",
    headers,
    body: JSON.stringify({ numbers: contatos.map((c) => c.numero) }),
  });
  const existentes = new Set(
    (await r.json()).filter((x) => x.isInWhatsapp).map((x) => x.query)
  );

  // 2) envio devagar, com pausa variável e texto que muda
  for (const c of contatos.filter((c) => existentes.has(c.numero))) {
    const text = escolhe(saudacoes) + ", " + c.nome + "! Tudo bem? Podemos falar sobre o seu pedido?";
    await fetch(BASE + "/" + ID + "/send/text", {
      method: "POST",
      headers,
      body: JSON.stringify({ number: c.numero, text }),
    });
    await pausa(8000 + Math.random() * 17000);
  }
}

main([{ numero: "5511999999999", nome: "Maria" }]).catch(console.error);

The list matters more than any technical setting. Use contacts who asked to hear from you (a form, a purchase, a previous support interaction) and record when and how consent was given. Brazil's LGPD requires a legal basis for processing personal data, and consent is the most direct basis for relationship messages. This text is not legal advice.

In practice, four rules. First: the first contact should say who you are and why you are writing. Second: offer an exit in every campaign message and honor the request to stop right away, removing the contact from the list. Third: remove people who have not replied in a long time. Fourth: never buy a list. A purchased number combines everything WhatsApp penalizes most: a cold list, nonexistent numbers and recipients who will report you.

To validate numbers without sending anything, use the validation tool or the batch verification endpoint shown earlier. For more on campaigns, see bulk messaging on WhatsApp.

Before a ban there are usually signs. A sharp drop in reply rate, messages that stay on a single tick for a long time, more people saying they did not ask for the message, unexpected instance disconnections and trouble reconnecting are all reasons to stop and review your sending. Reduce volume, go back to talking only with people who already engage and review the text.

Monitor through the API. The instance status shows the state, the webhook with the connection event warns of drops and the messages_update event brings delivery status (see the guide on webhooks in production). A number that keeps dropping deserves investigation, as in the guide on WhatsApp disconnecting on its own.

First, stop all sending from the number, including automations. Insisting makes it worse. Second, identify the type of problem. A temporary restriction usually blocks sending or starting conversations for a while, while a permanent ban disables the account. Check the message WhatsApp shows in the app and the instance status.

Third, use WhatsApp's own appeal channels. If the app offers the option to request a review, use it, explaining the legitimate use of the number honestly. There is no guarantee of reversal, and timelines and rules belong to WhatsApp. Fourth, do not create accounts through automated means to get around the ban: the Terms prohibit it, and it makes the problem worse.

Fifth, do the root-cause analysis before using another number. Review the list, the consent, the volume, the text and the pace. Swapping SIMs without changing behavior repeats the result. Sixth, activate plan B: a spare number that is already warmed up, communicating with customers through another channel (email, SMS) and, if the channel is critical, evaluating the official API. The detailed step by step is in banned number: what to do.

A qualitative reading, with no numbers, of what tends to weigh more or less. It guarantees nothing and serves to prioritize care.

A more detailed guide to this matrix, with examples by industry, is the subject of its own guide. Here the rule holds: the more the message is expected by the recipient, the lower the risk; the more it is a surprise, the higher.

Pick the official one when losing the number would be unacceptable, when a contract or legal team requires an approved channel, when the volume is large-scale transactional notifications or when the brand needs the official account badge. On the official API, billing is per delivered message and outside the 24-hour window only an approved template works, as in the guide on the 24-hour window and templates.

The unofficial one tends to make sense for conversation with your own base, quick channel validation and operations that live in groups, always with awareness of the risks described above. Many businesses use both. See the comparison ZapZap vs the official API and the honest guide to the unofficial API. ZapZap's current prices are on the pricing page.

[ ] I accept that unofficial use is not covered by the WhatsApp Terms and that the number can be restricted

[ ] I have a spare number and an alternate channel to notify customers

[ ] I only message people who expect to hear from me, with consent on record

[ ] The number was warmed up and volume ramps up in steps

[ ] The list is validated before sending and people who ask to opt out are removed

[ ] Varied text, variable delay and the typing indicator on

[ ] I monitor status, drops and delivery through webhooks

[ ] I stopped sending at the first sign of risk and investigated the cause

[ ] If the channel is critical, I evaluated the official API

Myth 1: a new, cheap SIM solves it. A new SIM has no history, and history is exactly what helps. Swapping SIMs without changing behavior just repeats the result, at a higher cost.

Myth 2: there is a technical trick that makes the number invisible. No network, proxy or software trick changes the fact that WhatsApp evaluates behavior and reports. A tool helps with pace and list hygiene; it does not replace consent.

Myth 3: a personalized message with a name is enough. The name helps, but if the person did not expect the message, they will report it all the same. Relevance and expectation weigh more than personalization.

Myth 4: sending in the middle of the night, or very slowly, protects you. Timing and speed are part of the whole, but neither alone makes up for a cold list.

Myth 5: if it worked yesterday, it will work tomorrow. WhatsApp's detection rules change without notice. What is safe today can become a problem later, which is why monitoring is a permanent part of the operation, not an initial step.

Myth 6: whoever sells the tool guarantees the result. No vendor controls WhatsApp's decision. If someone promises it, treat the promise as a warning sign about the vendor.

ZapZap helps with the technical side: the send queue with a configurable delay per instance, the automatic typing indicator proportional to the text, the number verification endpoint, the new-conversation limits lookup, the proxy per instance, the status and connection events by webhook, and the community warm-up described on the warm-up page. All of this reduces typical bot patterns.

The help ends where your use begins. ZapZap does not control who is on your list, whether there was consent, what the message says or how WhatsApp evaluates the account. It also has no power over WhatsApp's decision to limit or ban a number, which is why we do not promise it will not happen. What we can do is provide the tools, the transparency and this guide. The decision to use an unofficial API, with the risk it carries, is yours.