WhatsApp error 4: app reached its API call rate limit
Error code 4 means the app has reached its API call rate limit. Meta's description is "The app has reached its API call rate limit." It counts calls made by the app over a rolling hour, not messages sent from a number. Check usage in the App Dashboard, wait, and reduce how often the app calls the API.
Meta's code for "The app has reached its API call rate limit."
Calls an app may make in one hour under Graph API Platform Rate Limits.
The name the Graph API error handling guide gives code 4.
What does WhatsApp error code 4 mean?
It means your app has made too many API calls in the current window and further calls are refused until the count drops.
Meta lists code 4 under throttling errors with the details text "The app has reached its API call rate limit." The Graph API error handling guide calls it API Too Many Calls and describes it as a temporary throttling issue.
It sits beside two other throttling codes that are easy to confuse with it. 80007 is the WhatsApp Business Account reaching its rate limit. 130429 is Cloud API message throughput. Code 4 is neither: it is the app's own budget of calls.
How is the app's call limit calculated?
For requests made with an app access token, Meta's Graph API rate limiting guide gives a formula: calls within one hour equal 200 multiplied by the number of users.
The number of users is based on the app's unique daily active users, with weekly and monthly figures used when daily usage dips. It is a limit on the app as a whole rather than per user, so a few busy users can use most of it.
The guide also says usage appears in the App Dashboard and, once enough calls have been made, in an X-App-Usage header on responses. That header is the way to see the limit approaching before error 4 arrives.
What should you do after error 4?
Stop calling for a while, then call less.
Meta's rate limiting guide is direct about the first part: when the limit has been reached, stop making API calls, because continuing increases the call count and lengthens the time before calls succeed again.
The second part is design. Spread requests evenly instead of in bursts, filter responses so one call returns what you need, and avoid calls that fetch overlapping data. Polling is the usual culprit. An integration that asks for the same account status every few seconds spends its budget on answers it already has.
Common mistakes
- Retrying in a loop. Every extra call adds to the count and pushes recovery further away.
- Treating it as a sending limit. Code 4 counts the app's calls, while message throughput is 130429.
- Polling status endpoints on a short interval. Repeated reads of unchanged data spend the hourly budget.
EasyCoexistence monitors each connected number 24/7 on its own side, so checking connection health does not have to be built as a polling loop against your app's call budget.
Frequently asked questions
Is error 4 the same as error 130429?
No. 130429 is message throughput for a number. Error 4 is the number of API calls your app has made.
How long does error 4 last?
Until the call count in the rolling one hour window drops below the limit. Calling during that time extends it.
Where can I see how close my app is to the limit?
In the App Dashboard's Application Rate Limit section, and in the X-App-Usage header returned on responses.
Is error 4 the same as error 80007?
No. Meta uses 80007 when the WhatsApp Business Account hits its rate limit, while error 4 counts the app's own calls.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on