Rate limits and messaging throughput
There are four separate limits, and conflating them is why rate limiting is confusing. A messaging tier caps unique recipients per day, throughput caps messages per second, a pair limit caps messages to one person, and a management limit caps API calls that are not messages.
The error returned when the throughput limit is reached.
The error for too many messages between one pair.
The error for the account's management call limit.
Messaging tier
How many unique customers you can start a conversation with in a rolling 24 hours. New numbers begin low and move up automatically as quality holds and volume grows.
- Tiers step up: 1K, 10K, 100K and unlimited unique recipients per day.
- Only business-initiated conversations count against it.
- Replies inside the service window do not.
- A quality drop can move the tier back down.
Throughput
Messages per second, which is a different thing from the daily tier. A number can be well inside its tier and still hit throughput by sending a burst.
On a Coexistence number this is the limit that surprises people, because it is capped lower than on a standard Cloud API number. That ceiling is Meta's and applies to every Coexistence provider, so no provider can raise it.
Per-recipient limits
A separate cap on how many messages pass between your number and one recipient in a short window, reported as error 131056. It exists to stop one person being flooded, so it can trigger on a low-volume account.
The cause is almost always automatic: a retry loop, a webhook handler invoked twice for the same event, or a bot splitting a reply into several short messages.
Management call limits
Nothing to do with messages. Reading numbers, listing templates and checking status all count against a separate account limit, reported as error 80007.
Polling is what exhausts it. A status check every thirty seconds is thousands of calls a day against data that changes a few times a month, and webhooks remove the need for almost all of them.
What raises a limit
Quality and history, not payment. There is no plan to buy and no provider who can lift a cap on your behalf.
- Maintain a green quality rating; recipient blocks are what lower it.
- Send volume consistently rather than in bursts.
- Complete business verification, which gates the higher tiers.
- Wait. Tier increases are evaluated automatically over time.
Common mistakes
- Treating all rate limits as one. Four different limits produce four different errors.
- Polling status on a short interval. It burns the management limit on data that rarely changes.
- Expecting to pay for a higher tier. Tiers move on quality and history.
EasyCoexistence reads quality rating, messaging tier and connection state from Meta continuously, so a tier change or a quality decline is visible as an event rather than inferred from failed sends.
Frequently asked questions
Why am I rate limited at low volume?
Probably the per-recipient limit, error 131056, which caps messages to one person regardless of your account total.
Can I pay for a higher tier?
No. Tiers rise automatically on quality and sending history.
Is throughput lower on Coexistence?
Yes. Meta caps it lower than on a standard Cloud API number, and no provider can raise it.
What counts against the management limit?
Reads and configuration calls: listing numbers, templates and statuses. Webhooks avoid almost all of them.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on