Two different Meta limits
Do not mix these up:
Whatsable sits on Meta Cloud API. Hitting either limit shows up as Meta errors or undelivered business-initiated traffic — not as a Whatsable “upgrade your RPM” control in the console.
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):
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.
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 — do not hard-code a Whatsable “daily RPM.” 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.
Whatsable API rate limits (RPM)
Unpublished / unknown. Whatsable does not currently publish a numeric requests-per-minute (RPM) figure for its own HTTP APIs in customer docs.- Do not invent a Whatsable RPM, “generous rate limit,” or plan-based API quota.
- Use the Meta MPS, Coexistence, and messaging limits sections on this page.
- If a send fails with Meta throughput details, treat it as Meta
130429/ Throughput — not as a missing Whatsable RPM table.
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 error131056). 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
- Read the error
codeanddetails. Throughput → 130429. Do not match deprecated titles alone. - Check Coexistence. If the number still uses the WhatsApp Business app, Meta MPS is 20, not the default 80 / 1000 ladder.
- Separate MPS from messaging limits. A green throughput number can still fail business-initiated templates if Meta messaging limits / quality / cold outreach rules apply.
- 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).
- 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.
What this page does not claim
- No invented Whatsable numeric RPM or plan-based API quota.
- No marketing comparisons to other BSPs.
- No typing-indicator / “dots” product claims.
- No native drip builder (sequences stay in Make / Zapier / n8n).
- No rate-dashboard UI that is not present in your console.
- Exact Meta messaging-limit tier integers are not copied here as everlasting Whatsable facts — use Meta’s Messaging Limits page and WhatsApp Manager.
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.