Can an API guarantee that my number will not be banned?

No. WhatsApp controls restrictions. A linked device, health reading or warming feature cannot guarantee that a number will remain unrestricted.

Who controls pacing and jitter?

You do, in your application or automation workflow. HelloHop does not pace or jitter customer sends. Usage allowances and in-flight caps serve different purposes.

What is the riskiest way to start with a new number?

Cold outbound to people who never messaged you is the fastest way to get a new number restricted. Start with expected conversations, get permission and honor requests to stop.

Does a good health reading mean I can send faster?

No. Health readings describe available evidence, not a safe sending quota or a prediction of what WhatsApp will do. Waiting and stale readings also need context.

Is warming available to every account?

No. The warming endpoint is available only to enabled accounts. Other accounts receive not_found. Optional warming has its own terms and restart rules and does not replace your sending practices.

Does unlinking impose a cooldown before I can link again?

No. You can request a new QR or pairing code and approve it on your phone. Linking again does not remove a restriction imposed by WhatsApp.

Guides

WhatsApp number bans: how to avoid them when using an API

Reduce WhatsApp restriction risk by messaging people who expect to hear from you, avoiding bursts, and stopping unwanted outreach. Cold outbound to people who never messaged you is the fastest way to get a new number restricted. With HelloHop, pacing and warm-up are your responsibility; health readings and warming cannot guarantee protection from bans.

Facts (as of October 2026, API v1)

GET /v1/sessions/{channel}/safety returns number health readings, not a ban prediction.
GET /v1/sessions/{channel}/warming reads warming state only for accounts enabled for that feature.
No sending interval, warm-up period or health reading guarantees a number will remain unrestricted.

What can trigger restrictions

Cold outbound to strangers is especially risky for a new number. A purchased list is not an expected conversation.
Bursts of outreach can increase restriction risk. A successful API response is not permission to accelerate.
People can report unwanted messages. Honor requests to stop and remove those recipients from future outreach.

Pacing and warm-up belong to the customer

Build pacing, jitter, recipient checks and gradual warm-up into your application or automation workflow. HelloHop is the transport and does not pace or jitter customer sends. Sandbox allowances and in-flight caps bound usage and concurrent work; they are not a reputation strategy.

Start with real conversations people want, rather than testing a new number against strangers. Keep volume appropriate to those conversations. If people object or WhatsApp restricts the number, stop the outreach and review your recipient selection and behavior. There is no universal safe daily quota or delay.

Read number health without treating it as permission

curl

API=https://api.hellohop.app/v1
BASE="$API/sessions/$CHANNEL_ID"
AUTH="Authorization: Bearer $CHANNEL_TOKEN"

curl -s -X GET "$BASE/safety" \
  -H "$AUTH"

curl -s -X GET "$BASE/warming" \
  -H "$AUTH"

Set CHANNEL_ID and CHANNEL_TOKEN first. The /safety response includes status, overall and indicators. Read the reasons behind each indicator. A waiting or stale report is not a fresh measurement; a good overall.level is not a guarantee against restriction and should not trigger higher sending volume.

What the warming endpoint does

The /warming GET reads enabled, state, reason_code, restart_after and stale. Access is limited to accounts enabled for warming; other accounts receive not_found. A stale reading is last known progress. This optional feature does not replace your responsibility for customer traffic or make unsolicited outreach safe.

PUT /v1/sessions/{channel}/warming turns optional warming on or off. Enabling requires the account owner to acknowledge the current warming terms. A restart after a warming safety stop can require a cooldown and restart acknowledgment. Those rules govern the optional warming feature; they are not a cooldown on linking your number or a pacing policy for your application sends.

What is not guaranteed

HelloHop cannot promise ban immunity, a guaranteed safe sending rate, recovery of a restricted number, or that warming prevents a restriction. WhatsApp controls restrictions. You can link, unlink on your phone and link again without an extra transport cooldown; re-linking is not a way to remove a WhatsApp restriction.

Keep connection failures separate from restrictions. A disconnected linked device may need reconnection; a number restricted by WhatsApp needs attention in WhatsApp. Read the reported state and error before deciding what to do. Avoid repeated send attempts while the cause is unknown.

Questions

Can an API guarantee that my number will not be banned?: No. WhatsApp controls restrictions. A linked device, health reading or warming feature cannot guarantee that a number will remain unrestricted.
Who controls pacing and jitter?: You do, in your application or automation workflow. HelloHop does not pace or jitter customer sends. Usage allowances and in-flight caps serve different purposes.
What is the riskiest way to start with a new number?: Cold outbound to people who never messaged you is the fastest way to get a new number restricted. Start with expected conversations, get permission and honor requests to stop.
Does a good health reading mean I can send faster?: No. Health readings describe available evidence, not a safe sending quota or a prediction of what WhatsApp will do. Waiting and stale readings also need context.
Is warming available to every account?: No. The warming endpoint is available only to enabled accounts. Other accounts receive not_found. Optional warming has its own terms and restart rules and does not replace your sending practices.
Does unlinking impose a cooldown before I can link again?: No. You can request a new QR or pairing code and approve it on your phone. Linking again does not remove a restriction imposed by WhatsApp.

Free sandbox, forever. Add a real number when you're ready.

Start in the free sandbox

HelloHop is an independent WhatsApp API for developers: send and receive messages, automate groups and communities, and get signed webhooks with a free sandbox. Not affiliated with WhatsApp or Meta. You link your own number.