TL;DR: WhatsApp error
80007means the WhatsApp Business Account has reached its rate limit — too many calls against the WABA in the current window. This is a WABA-level rate-limit problem, not message-send throughput. Back off, cache reads, and reduce polling.
What Error 80007 Means
Meta's details string is: "The WhatsApp Business Account has reached its rate limit." (Throttling error — confirmed verbatim on the live table.) Meta points to the WhatsApp Business account Rate Limits doc and advises trying again later or reducing the frequency/amount of API queries. Note: 80008 is not a code in Meta's current WhatsApp Cloud API error table — if you saw "80008" referenced elsewhere for "too many WABA calls," 80007 is the documented WhatsApp code; 4 is the app-level API call rate limit.
Where You See It
An immediate API error on calls against the WABA (lookups, template management, assigned users, subscribed_apps, related admin/config APIs). It is not message-send throughput (130429).
Common Causes
- Polling WABA/template endpoints too frequently.
- Several background jobs querying the same WABA.
- Repeated setup/debug calls during onboarding; poor caching of management reads.
How to Fix It
- Back off immediately and retry later.
- Cache management reads aggressively; batch admin reads where possible.
- De-duplicate concurrent jobs polling the same WABA.
- Replace polling with webhook-driven state where available.
How to Prevent It
- Design WABA admin tooling around caching and change events, not tight polling loops.
- Stagger setup, audit, and monitoring jobs; don't confuse management polling with message-send traffic.
- Per Meta's Graph API rate-limiting doc, the WhatsApp Business Management API allows 200 requests/hour per app, per WABA by default, rising to 5,000 requests/hour per app, per active WABA once at least one phone number is registered. Stay well under these with caching and webhooks.
Related Errors
/docs/whatsapp-error-130429— send throughput limit/docs/whatsapp-error-100-webhook-override— subscribe before override/docs/whatsapp-error-190— invalid token on management calls- See the full error reference
FAQ
Does 80007 block normal message sends? It blocks the WABA/management calls hitting the limit; it's distinct from message-send throughput 130429.
Is there an "error 80008"? Not in Meta's current WhatsApp Cloud API error table. For WABA rate limits use 80007; for app-level API call limits use 4.
What's the biggest prevention win? Stop over-polling — cache reads and use webhook/state-change patterns.
How Dualhook Helps
This is a platform/management area where Dualhook helps by reducing the need for noisy manual polling — it surfaces connection and management status in a purpose-built way and routes account/webhook events so you don't poll WABA endpoints as hard. See Capacity, Quality & Limits, Messaging Health Status, and WhatsApp Webhook Override. Dualhook still never reads message content.