Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4133 pages

APIs and integrations

WhatsApp Cloud API Messaging Limits, Throughput Tiers and Template Quality

In short

WhatsApp Business API messaging limits count unique recipients outside the customer service window, per business portfolio, so one busy number can use up the allowance of every other number you own. New portfolios start at 250 a day. Separately, each number has a messages-per-second ceiling, each recipient a pair limit, and each template a quality rating that can hold or drop sends.

What do WhatsApp Business API messaging limits actually count?

Meta defines the messaging limit as the number of unique WhatsApp user phone numbers your business can deliver to outside a customer service window, in a moving 24-hour period. It is not a message count. Ten reminders to one person use one slot; one message each to 300 new people goes past the starting limit.

The limit is set on the business portfolio and shared by every business phone number inside it. Meta warns that a single number can consume the whole portfolio's capacity. A marketing number and a one-time-passcode number in the same portfolio therefore compete for the same daily pool.

To read the current value, request the whatsapp_business_manager_messaging_limit field on the phone number; the example response returns TIER_250. The older messaging_limit_tier field is deprecated. WhatsApp Manager shows the same figure under Account tools, Messaging limits.

Checked against: source 1

How does a portfolio climb from 250 to unlimited?

The ladder has five steps: 250, 2,000, 10,000, 100,000 and unlimited. Only the first jump needs action from you; the rest happen automatically when the criteria hold.

  • 250: where every new portfolio starts.
  • 2,000: complete one scaling path. Verify the business, have the onboarding partner verify it, or deliver 2,000 messages outside service windows to unique numbers within 30 days using templates with a high quality rating. Meta then reviews message quality and approves or denies.
  • Approval arrives by email, a developer alert and a business_capability_update webhook. The field is max_daily_conversations_per_business on webhooks v24.0 and newer; v23.0 and older used max_daily_conversation_per_phone until February 2026.
  • Denial triggers an account_alerts webhook whose alert_type (ELIGIBILITY_DEFERRED, FAILED or NEED_MORE_INFO, each prefixed INCREASED_CAPABILITIES_) names the next path to try.
  • 10,000, then 100,000, then unlimited: one level at a time, within 6 hours, when messages are high quality across all numbers and templates and the business used at least half its current limit in the last 7 days.

Checked against: source 1

How many messages per second can one business number send?

Throughput is set per registered number: 80 messages per second by default, counting inbound and outbound traffic of every type. Going over returns error code 130429 until you are back under the rate. Numbers shared with the WhatsApp Business app are fixed at 20 per second.

The upgrade to 1,000 per second is automatic. It needs three things: an unlimited messaging limit on the portfolio, the number reaching 100K or more unique users outside service windows in a moving 24 hours, and a quality_score of YELLOW or better. During the upgrade, which can take up to 1 minute, the number is unusable and requests return 131057. A phone_number_quality_update webhook with event THROUGHPUT_UPGRADE confirms it.

Meta also sets a bar for your webhook servers at that speed: absorb three times outgoing traffic in status callbacks plus one times expected inbound, with median latency at or under 250 ms and under 1% of requests above 1 second. Failed webhooks are redelivered for up to 7 days with exponential backoff. GET the throughput field on the number to see its level.

Checked against: source 2

Why does one customer trigger a throttle on a healthy number?

The pair rate limit governs one business number talking to one user. The steady rate is 1 message every 6 seconds, roughly 10 a minute or 600 an hour. Exceeding it returns error 131056, even when the number's overall throughput is idle.

A burst of up to 45 messages in 6 seconds is allowed, but it borrows from future quota: after a burst of 20, the docs say to wait about 2 minutes. Their retry formula is 4 to the power X seconds, starting with X at 0 and adding 1 after each failure. I would watch for it first in chatbots that split one answer into several bubbles.

Checked against: source 3

What does a template's quality rating change?

Each template carries a quality_score of GREEN, YELLOW, RED or UNKNOWN, built from user feedback, read rates and engagement. New templates start at UNKNOWN. All four can still be sent; the rating matters because it drives pacing and pausing.

Pacing applies to marketing and utility templates that are new, recently unpaused or not GREEN. The send call answers message_status accepted or held_for_quality_assessment. A good signal releases held messages; a bad one pauses the template and fails each held message with code 132015. Meta's stated goal is delivery within an hour at the 99th percentile even when paced.

A template that falls to RED is paused for 3 hours the first time, 6 hours the second, and disabled the third. Sends to a paused template are rejected and do not count against the messaging limit. A pacing pause needs a manual unpause through POST /{template_id}/unpause or WhatsApp Manager. Pausing leaves the phone number alone at first, but repeated low quality can eventually affect it.

Checked against: source 4, source 5, source 6

Which limit did a failed send hit?

Four counters can stop a send, and each one has a different scope and signal. A management API budget sits beside them: 200 requests an hour per app per Messaging account by default on endpoints such as message_templates, or 5,000 for active accounts with a registered number.

CounterScopeHow it shows up
Messaging limitBusiness portfolio, unique users per moving 24 hoursLimit field on the number; capability webhooks
ThroughputOne business phone number, messages per secondError 130429
Pair rate limitOne number to one WhatsApp userError 131056
Template qualityOne templateheld_for_quality_assessment, then 132015 or a pause

Checked against: source 1, source 2, source 3, source 5

What else do people ask?

Do replies inside the customer service window count toward the daily limit?

Meta's definition covers delivery outside a customer service window, so messages within an open window are not what the limit counts.

Can adding a second phone number double the daily limit?

No. The limit belongs to the business portfolio and is shared by all of its numbers. A second number adds throughput, not reach.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. This page compares Meta's WhatsApp Business Platform developer documents, fetched on 20 Nov 2026. I did not send messages through the Cloud API for it, so nothing here is a measurement. It does not cover pricing, the Marketing Messages API, calling, groups, or Help Center articles outside developers.facebook.com. Found a mistake? Tell me.

Keep reading

Next step

Have a project in mind?

Tell me about it. A discovery call within 48 hours.