Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 131056: Pair rate limit hit

Error 131056 is the pair rate limit: one business number sent too many messages to one recipient number in a short period. The limit applies to that pair only, so the rest of your sends keep working.

131056
Code
Pair rate limit hit
Meta's name
Rate limit
Type
API response or failure webhook
Where you see it
Yes, with backoff
Retry

Quick answer

You hit WhatsApp's limit on messages from one business number to one person in quick succession. Slow down for that recipient, combine messages where you can, and retry the held message after a short wait.

What WhatsApp error 131056 means

Meta lists 131056 as a throttling error: too many messages were sent from the sender phone number to the same recipient phone number in a short period of time. Meta's guidance is to wait before retrying to that recipient, while sends to other numbers can continue without waiting.

Why error 131056 happens

Limits like this are triggered by sending patterns rather than single messages. The patterns that usually cause it:

  • A loop or a retry bug resent the same message to one customer many times.
  • An automation fired several notifications for one order at once: confirmation, invoice, shipping and a survey.
  • A chatbot replied with many short separate messages instead of one structured message.
  • Load tests that targeted a single test handset at high speed.

How to fix error 131056

Most of the work is making your sending resilient so this resolves itself.

  • Find the recipient in your logs and check how many messages went to them in the last minute or so.
  • Look for duplicate sends from retries without an idempotency key, or two systems sending the same event.
  • Merge bursts into fewer, richer messages: one template with the key details, or one interactive list instead of several texts.
  • Add a short per-recipient queue so messages to one person go out one after another rather than all at once.
  • Spread test traffic across several test numbers instead of hammering one handset.

Should you retry after 131056?

Retry the held message to that recipient after a pause, with exponential backoff if it fails again. There is no need to stop other traffic: the limit is per sender–recipient pair. If a customer genuinely needs a stream of updates, space them out.

How error 131056 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131056, the "(#131056)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 131056, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up. Check the recipient's conversation in the InfiQ inbox: a burst of identical or near-identical outbound messages usually points straight at the duplicate.

Send it through InfiQ

Frequently asked questions

What is WhatsApp's pair rate limit?+
It caps how many messages one business number can send to one WhatsApp user in a short window. Meta does not tie it to a published number you should aim for; design your flows so a single person never receives a rapid burst of separate messages.
Does error 131056 affect my other customers?+
No. It is specific to the sender–recipient pair. Messages from the same number to other customers continue normally, which is why it usually points to a bug or a chatty flow rather than an account problem.