WhatsApp error 130429: throughput limit reached
Error 130429 means the Cloud API throughput limit for this number has been reached. It is a rate problem rather than a volume one: the same messages sent more slowly go through. On a Coexistence number the ceiling is fixed by Meta.
- A rate limit, not a daily cap
- Coexistence throughput is fixed by Meta
- Queue and pace rather than retry immediately
Nothing charged for 7 days. Cancel anytime.
Meta's code for reaching the Cloud API message throughput limit.
Sending throughput on a Coexistence number, set by Meta and not raisable.
The separate code for reaching a WhatsApp Business Account rate limit.
What is actually being limited?
The rate at which messages leave, not how many you may send in a day.
The platform accepts a certain number of messages per second for a number, and requests beyond that are rejected rather than queued. So a send of ten thousand messages is not itself a problem; sending them all in the same second is. Spread across a few minutes the same batch goes through untouched.
This is distinct from messaging tier, which governs how many unique customers you may start conversations with in a day, and from quality limiting, which restricts a number whose recipients react badly. Three different ceilings, three different codes, commonly confused with one another.
Can the limit be raised?
Not on a Coexistence number. It is fixed by Meta at a set rate and no provider can lift it, which is worth knowing before designing around a higher number.
On a number onboarded the ordinary way, throughput scales with quality rating and messaging tier over time. That difference is one of the few genuine trade offs of Coexistence, and it is the reason a high volume broadcast number is usually better off onboarded without it.
For conversational use the ceiling is rarely the constraint. It becomes one when something loops through a list and sends as fast as the code allows, which is a shape worth avoiding for its own sake.
What should the sender do instead?
Pace the sending and retry with a backoff, rather than retrying immediately.
A queue with a fixed rate is the durable answer, because it makes the limit a property of the system rather than something discovered in production. Where that is too much, an exponential backoff on this specific code gets most of the benefit.
What does not work is tight retrying. A loop that retries instantly on rejection generates more requests at exactly the moment the number is already over its rate, which extends the condition rather than clearing it.
Common mistakes
- Retrying immediately. More requests at the moment of rejection keeps the number over its rate.
- Confusing it with messaging tier. That governs daily unique conversations, not messages per second.
- Designing a Coexistence number around throughput that scales. It does not; the ceiling is fixed.
EasyCoexistence reads throughput level alongside quality rating and messaging tier on every connected number, so the ceiling a number is actually operating under is visible rather than assumed.
Frequently asked questions
Does this mean my number is restricted?
No. It is an ordinary rate limit. The number is healthy and the same messages succeed when sent more slowly.
How fast can a Coexistence number send?
Meta sets it at a fixed rate for Coexistence numbers rather than scaling it with quality and tier.
Is 80007 the same?
No. That one is a rate limit on the WhatsApp Business Account rather than on message throughput for a number.
Will a different provider send faster?
No. The limit belongs to the number and to Meta, not to whoever is calling the API.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on