> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/account-settings/whatsapp-api/official-whatsapp-api-errors/error-131048-spam-rate-limit-hit.md).
# Error (#131048) Spam Rate Limit Hit
The error **131048 - Spam Rate Limit Hit** is returned directly by Meta (WhatsApp) when a business number reaches limitations related to the quality of sent messages or behavior considered spam-like.
#### Error message presented by Meta
> **Message failed to send because there are restrictions on how many messages can be sent from this phone number. This may be because too many previous messages were blocked or flagged as spam.**
In free translation:
> **Failed to send the message because there are restrictions on the number of messages that can be sent by this number. This may happen because many previous messages were blocked by users or marked as spam.**
### Why does this error happen?
According to Meta's documentation, this error occurs when the WhatsApp Business number shows signs of low quality, usually caused by:
* High volume of blocks by recipients;
* Spam reports made by users;
* Sending messages to contacts without prior consent;
* Mass campaigns to poorly engaged lists;
* Content considered irrelevant by recipients.
When this happens, Meta temporarily reduces the number's sending capacity to protect the platform users' experience.
### How to check the number quality?
Meta recommends checking the number quality indicator in WhatsApp Manager.
The statuses can be:
| Status | Meaning |
| --------- | -------------------------------------- |
| π’ High | Good reputation and low complaint rate |
| π‘ Medium | Attention needed |
| π΄ Low | High risk of restrictions and blocks |
When quality drops to Medium or Low, Meta may limit message sending or apply temporary restrictions.
### How to fix it?
If error 131048 is displayed, it is recommended to:
1. Temporarily suspend new mass sends;
2. Wait for the restriction period imposed by Meta;
3. Review the number quality in WhatsApp Manager;
4. Analyze recent campaigns that may have caused blocks or reports;
5. Prioritize sending to contacts who already interact with your company;
6. Ensure that all contacts have consented to receive messages.
### Best practices to avoid the error
#### Request authorization from contacts
Send messages only to users who have given consent for communication via WhatsApp.
#### Segment your list
Avoid sending campaigns to your entire contact list without proper segmentation.
#### Send relevant content
Useful and personalized messages tend to generate more engagement and fewer blocks.
#### Avoid excessive frequency
Multiple sends in a short period can increase the chances of blocks and reports.
#### Monitor the number quality
Regularly track the quality indicators provided by Meta.
### Important
The error **131048** is not caused by SAC 360ΒΊ or by SprintHub. It is a limitation applied directly by Meta (WhatsApp) to the connected number.
While the restriction is active, some messages may not be delivered, even if the sending is performed correctly by the system.
### Conclusion
The error **131048 - Spam Rate Limit Hit** indicates that Meta has identified a sending behavior that may negatively impact users' experience. In most cases, the solution involves improving campaign quality, reducing complaints, and waiting for the restriction to be automatically removed.
Maintaining relevant, authorized, and segmented communication is the best way to avoid this type of block and preserve the reputation of the WhatsApp Business number.
For more technical details, the official Meta documentation can be consulted at:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sprinthub.com/en/topics/system-settings/account-settings/whatsapp-api/official-whatsapp-api-errors/error-131048-spam-rate-limit-hit.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.