Business Use Case Rate Limit(BUC)

Counted per

App, per WABA, over a rolling hour

Default budget

200 requests an hour

Active WABA (registered number)

5,000 requests an hour

Credit Line API

5,000 requests an hour

Usage header

X-Business-Use-Case-Usage (percentages + minutes to regain access)

Limit errors

80008 (BUC reference) · 80007 (WABA rate limit)

Template creation cap

Also at most 100 new templates per WABA an hour

Not counted here

Message sends — see throughput (80 mps default)

1. 1

   Know which calls count

   The WABA node and its phone_numbers, message_templates, subscribed_apps and assigned_users edges count against the per-WABA budget; the Credit Line API has its own. Message sends do not.

2. 2

   Know the budget for each WABA

   200 requests an hour per app per WABA until a phone number is registered, 5,000 after. Track which of your WABAs are active, because the same script costs very different shares of each.

3. 3

   Read the usage header

   Parse X-Business-Use-Case-Usage on every response, find the entry for the WABA you called, and take the highest of call_count, total_cputime and total_time as your usage.

4. 4

   Slow down before 100%

   Set your own thresholds, for example deferring background syncs at 75% and pausing all non-urgent calls at 90%, so interactive actions such as creating a template still have room.

5. 5

   Stop and wait when throttled

   On 80008 or 80007, stop calling that WABA and wait for estimated_time_to_regain_access minutes. Meta's guidance is to stop making calls once the limit is reached, so immediate retries only prolong the problem.

6. 6

   Replace polling with webhooks

   Subscribe to template status, template quality and phone number quality webhooks so changes arrive as events, instead of fetching every template on a timer.

• Polling instead of listening

  Fetching every template or number on a timer spends the budget on calls that usually return nothing new. Subscribe to the template status and phone number quality webhooks and fetch only when an event says something changed.

• Confusing it with throughput

  Slowing message sends will not clear an 80008, and pacing management calls will not fix a 130429. Identify the error code and endpoint first, then apply the matching limit.

• Retrying straight away

  Calls made while throttled fail and delay recovery. Pause that WABA for the estimated_time_to_regain_access minutes the header gives, then resume gradually.

• Forgetting new WABAs get 200, not 5,000

  Onboarding work happens before the number is registered, exactly when the budget is smallest. Register the number early and keep pre-registration scripts lean.

• Expecting batches to save quota

  A batch of 50 operations costs 50 calls. Batching saves round trips, not budget, so the header climbs just as fast.

Management calls are where partners and large brands quietly overspend their quota: a dashboard that polls every template every minute, an onboarding script that lists phone numbers after each step, a health check on a timer. On a new WABA with no registered number, 200 calls disappear quickly, and then template creation fails just as a campaign is about to launch. Reading the usage header and replacing polling with webhooks keeps the budget for the calls that matter and makes throttling a planned slowdown instead of an outage.

• Chart buc_usage_pct per WABA and alert at 75%, long before calls start failing.
• Give interactive actions (creating a template, connecting a number) priority over background syncs when usage is high.
• Cache WABA and phone number details for minutes, not seconds; they rarely change and webhooks report the important changes.
• Spread nightly jobs across the hour instead of firing them all at minute zero.

What is the rate limit for the WhatsApp Business Management API?

200 requests an hour per app per WABA by default, rising to 5,000 once the WABA has at least one registered phone number. The window is a rolling hour, and the Credit Line API endpoints have their own 5,000 budget.

What does the X-Business-Use-Case-Usage header mean?

It reports how much of a business use case budget your app has used. Each entry, keyed by the business object ID, gives call_count, total_cputime and total_time as percentages, plus estimated_time_to_regain_access in minutes when you are throttled.

What does WhatsApp error 80008 mean?

Your app has reached the business use case rate limit for the WhatsApp Business Management API on that account. Stop calling it, wait for the time the usage header gives, and reduce polling before resuming.

Does the BUC rate limit affect sending WhatsApp messages?

No. Message sends are governed by throughput (80 messages per second per number by default), the pair rate limit and messaging limits. The BUC limit applies to management calls such as templates, phone numbers and subscribed apps.