# Understanding WhatsApp Error Code 131056 (Pair Rate Limit)

When sending messages via the WhatsApp Cloud API, you may sometimes encounter error code **131056**, also known as the **Pair Rate Limit error**. This error is triggered when too many messages are sent too quickly to the **same WhatsApp user number**.

Let’s break down what this means and how to resolve it.

***

### <mark style="color:green;">What Does Error Code 131056 Mean?</mark>

The error indicates that your business is hitting a **pair rate limit** — in other words, you are trying to send too many messages in a short span of time to a **single user**.

While the Cloud API supports high throughput at the account level, Meta also enforces **user-level safeguards** to prevent spamming and ensure a better customer experience.

***

### <mark style="color:green;">Practical Limits Meta Imposes</mark>

According to Meta’s documentation:

* **Per-second limit**: For each registered business phone number, Cloud API supports **up to 80 messages per second (mps) by default**, and up to **1,000 mps with automatic upgrade**.
* **Throughput coverage**: This includes both inbound and outbound messages, across all message types (text, template, media, etc.).
* **Business-level limits**: Numbers are still subject to their **WhatsApp Business Account’s rate limits and template messaging limits**.
* **Error 130429 (Throughput exceeded)**: If you exceed your allowed throughput level, the API will return error **130429** until you are within the limit again.
* **Pair rate behavior**: Throughput is intended for campaigns involving **different recipients**. If too many messages are sent too quickly to the **same WhatsApp user**, the system enforces a **pair rate limit** to throttle delivery.

This is exactly where **Error 131056** comes into play.

***

### <mark style="color:green;">Why Does Meta Enforce Pair Rate Limits?</mark>

Meta applies these restrictions to:

* Prevent spammy behavior.
* Protect end-user experience on WhatsApp.
* Encourage businesses to communicate responsibly by spacing out repetitive messages to the same user.

***

### <mark style="color:green;">Troubleshooting & Best Practices</mark>

If you face **Error 131056**, here are recommended steps to handle it:

1. **Pause and Retry** → Slow down sending frequency to the same user. Allow short gaps between consecutive messages.
2. **Bundle Information** → Instead of sending multiple back-to-back messages, combine details into fewer, richer messages.
3. **Use Templates Wisely** → For repetitive communication, rely on approved WhatsApp templates instead of sending multiple free-form messages.
4. **Monitor Sending Patterns** → Track message flows to spot where your system may be over-sending.
5. **Stagger Campaigns** → If sending bulk notifications, stagger delivery times so that individual users aren’t hit with multiple messages in a row.

***

### <mark style="color:green;">Key Takeaway</mark>

Error **131056** doesn’t mean your WhatsApp Business Account is blocked — it simply means you need to **space out your messages** to individual users.

Meta’s throughput limits (80–1,000 mps per number) allow you to run large campaigns, but **pair rate limits** ensure you maintain a positive and non-intrusive customer experience.

By pacing your outreach, combining messages, and monitoring delivery patterns, you can avoid this error and deliver a smoother experience to your users.


---

# Agent Instructions: 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:

```
GET https://learn.doubletick.io/troubleshoot-errors/understanding-whatsapp-error-code-131056-pair-rate-limit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.