WhatsAble

What are Whatsable and Meta messaging rate limits?

Whatsable API v1 rate limits (RateLimit headers, 429 rate_limited, Retry-After), Meta WhatsApp throughput (80 MPS default, 20 on Coexistence), messaging limits outside the 24h window, and error 130429.

WhatsApp throughput and messaging caps are set by Meta, not by a Whatsable plan slider. This page covers the request limits of the Whatsable API v1, Meta messages-per-second (MPS) limits, the lower Coexistence MPS cap, and Meta messaging limits outside the 24-hour customer-service window.

If you need how to connect a number, start with Connect WhatsApp (Embedded Signup + Coexistence). For plan gates and unique-contact billing, see plans Bulk Message / Pro / Agency.

Two different Meta limits

Do not mix these up:

Limit typeWhat it controlsWho enforces it
Throughput (MPS)How fast a business phone number can send/receive messages on Cloud APIMeta (per phone number)
Messaging limitsHow many unique WhatsApp users you can message outside a customer-service window in a rolling 24 hoursMeta (portfolio / business capability)

Whatsable sits on Meta Cloud API. Hitting either limit shows up as Meta errors or undelivered business-initiated traffic. No Whatsable plan or setting raises them.

Meta throughput (messages per second)

Cite Meta’s Throughput documentation for the live numbers. As of Meta’s published Throughput page (updated 2026-06-17):

Phone-number situationMeta MPS (throughput)
Default Cloud API numberUp to 80 messages per second
Automatic upgrade (eligibility met)Up to 1,000 messages per second
Coexistence (WhatsApp Business app + Cloud API on the same number)Fixed 20 messages per second

Meta notes that throughput counts inbound and outbound traffic and all message types. Numbers remain subject to WhatsApp Business Account rate limits and template messaging limits even after a throughput upgrade.

Exceeding throughput: Meta returns Cloud API error 130429 (“Cloud API message throughput has been reached”) until you are back under the allowed level. Match on code and error_data.details, not on titles — see WhatsApp Cloud API error 130429.

Higher throughput: Meta can auto-upgrade a number to 1,000 MPS when the portfolio has an unlimited messaging limit, the number messages enough unique users outside the service window in a rolling day, and quality is Medium (yellow) or higher. Eligibility and exact checks live on Meta’s Throughput page — Whatsable does not sell or flip that upgrade.

Coexistence throughput (20 MPS)

Most Whatsable customers keep the WhatsApp Business app on the phone while using Cloud API (Coexistence). Meta fixes Coexistence numbers at 20 MPS so the app and API stay compatible. That cap is a Meta-side constraint.

Whatsable notes that match this page:

  • Coexistence throughput is Meta’s, not a Whatsable product limit you can raise in Settings.
  • Do not uninstall the WhatsApp Business app after connect — that breaks Coexistence.
  • Unofficial (non-Meta) API tools on that number stop once Coexistence is on.

Operator connect guide: Connect WhatsApp Business to Whatsable. Outbound when humans type in the Business app: Outbound WhatsApp Business app.

Meta messaging limits (unique recipients / day)

Separate from MPS: Meta caps how many unique customer numbers a business can message outside the customer-service window in a moving 24-hour period. Inside the window (the customer messaged you recently), free-form replies are not gated by that unique-recipient messaging-limit ladder.

Exact tier values and scaling rules change on Meta’s side. Treat Meta Messaging Limits and WhatsApp Manager as the live source.

Operator notes (not a substitute for Meta’s page):

  • Outside the 24-hour window, only approved templates start business-initiated conversations.
  • Unverified Meta Business Portfolios start with a low daily unique-recipient cap; verified portfolios scale through Meta’s messaging-limit tiers up to unlimited.
  • Customer replies that open or refresh the service window are not “using up” that business-initiated unique-recipient ladder the same way.

Keep messaging limits and MPS apart: they are two different limits.

Whatsable API v1 rate limits

The Whatsable API v1 limits how fast each API key can call it. Two limits apply:

  • Per API key. Each key has its own budget of requests, which refills steadily. Every request that authenticates counts, including one refused for a missing scope or plan.
  • Per sending number. Sends through the API from one number are also limited per second, whichever key sends them.

Every response to an authenticated request carries the state of the key's budget:

HeaderMeaning
RateLimit-LimitThe most requests the key can make in a burst.
RateLimit-RemainingHow many requests the key can make right now.
RateLimit-ResetSeconds until the budget is full again.

Over either limit, the API answers 429 with the error code rate_limited and a Retry-After header in seconds. The request was not processed. Wait that long, then retry. When the number's send limit refused the request, error.details.scope is "number".

  • Read the headers instead of hard-coding a number. The limits can change.
  • Spread requests out rather than sending them all at once.
  • A 429 rate_limited from Whatsable is not Meta error 130429. The first refuses the request before WhatsApp is called; the second comes back from WhatsApp on a send.

The error codes are on API v1 errors, and retrying safely is on Error Handling.

Pair rate and burst behavior (Meta)

Meta also applies pair rate limits when you send too many messages to the same WhatsApp user too quickly (separate from phone-number MPS). Meta documents this on Cloud API overview / error materials (for example throttling around error 131056). Campaigns that spray many different recipients are what MPS is sized for; hammering one user is a different Meta pair limit.

Whatsable does not override Meta pair limits.

Operator checklist when sends slow or fail

  1. Read the error code and details. Throughput → 130429. Do not match deprecated titles alone.
  2. Check Coexistence. If the number still uses the WhatsApp Business app, Meta MPS is 20, not the default 80 / 1000 ladder.
  3. Separate MPS from messaging limits. A green throughput number can still fail business-initiated templates if Meta messaging limits / quality / cold outreach rules apply.
  4. Warm gradually on cold lists (especially US). Meta may withhold delivery for healthy-ecosystem reasons — related codes live under Whatsable’s Meta error pages (for example 131049).
  5. Do not uninstall the Business app to “raise” throughput. That breaks Coexistence; Meta’s Coexistence MPS cap remains the documented path for dual-app numbers.

FAQ

Does Whatsable raise Meta’s 20 MPS Coexistence limit?

No. Coexistence MPS is fixed by Meta for app + API numbers. Whatsable does not control or raise it.

Where do plan unique-contact limits fit?

Those are Whatsable billing (unique contacts / overage), not Meta MPS. See plans Bulk Message / Pro / Agency; money stays on pricing.

Connect WhatsApp (Coexistence)

Embedded Signup, keep the Business app, Meta-side throughput honesty.

Error 130429 (throughput)

Match code + details when Cloud API MPS is exceeded.

Outbound Business app

Human replies typed in the WhatsApp Business app on Coexistence.

Meta Throughput (external)

Meta’s live MPS, Coexistence 20 MPS, and upgrade eligibility.

On this page

Two different Meta limitsMeta throughput (messages per second)Coexistence throughput (20 MPS)Meta messaging limits (unique recipients / day)Whatsable API v1 rate limitsPair rate and burst behavior (Meta)Operator checklist when sends slow or failFAQDoes Whatsable raise Meta’s 20 MPS Coexistence limit?Where do plan unique-contact limits fit?