> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/troubleshooting/429-too-many-requests-soft-ban.md).

# 429 (Too Many Requests) - Soft Ban

A few tips on what to do if you encounter a soft ban

A soft ban involves partially blocking the activity of your number. For example, you'll be able to send messages but not create groups. Or view and respond to messages, but without the ability to write new messages. This blocking is temporary and is related to atypical activity of your number. If you encounter error 429 (Too Many Requests), it means that your number has fallen under soft blocking. This is not a permanent ban yet, which means you will be able to continue using the number, but with some time restrictions.

A few tips on what to do if you encounter a soft ban:

* Give the account a "rest", stop sending messages (or doing the activity your number has been doing for the last 12 hours, such as creating groups, etc.) for a day or two, don't use WhatsApp with that number.
* Reinstall the app and switch accounts (for example, if you have WhatsApp Business, log out of it and log into regular WhatsApp, and vice versa).
* Write an email to WhatsApp support via the mobile app (Settings -> Help -> Write to us) asking them to unblock your account since you haven't violated anything. In response, you should wait for the standard reply that the account is unlocked, after which messages will start being delivered.

{% hint style="info" %}
For more details on how to enhance your WhatsApp security and reduce the risk of being blocked, check out our comprehensive guide on using residential proxies [here](/help-desk/blocking/using-residential-proxies-with-whapi.cloud.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.whapi.cloud/help-desk/troubleshooting/429-too-many-requests-soft-ban.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.