Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 4: API too many calls

Error code 4 is a rate limit on the Meta app making the calls, not on your phone number or a single recipient. It appears when the app has made more API calls than Meta allows in its current window.

4
Code
API too many calls
Meta's name
Rate limit
Type
On the API response
Where you see it
Yes, with backoff
Retry

Quick answer

The Meta app reached its API call rate limit. Slow down the calls, especially repeated reads such as polling templates or numbers, and retry with backoff.

What WhatsApp error 4 means

Meta documents code 4 as a throttling error: the app has reached its API call rate limit. Meta points developers to the application rate limit view for the app and advises trying again later or reducing the frequency or amount of API queries.

Why error 4 happens

Limits like this are triggered by sending patterns rather than single messages. The patterns that usually cause it:

  • Polling for template status or phone number details in a tight loop instead of using webhooks.
  • A sync job that reads every template or every number on each run.
  • Retries without backoff after another error, which multiply the call volume.
  • A traffic spike from many systems sharing the same app.

How to fix error 4

Most of the work is making your sending resilient so this resolves itself.

  • Replace polling with webhooks wherever a webhook exists, for example template status updates.
  • Cache data that rarely changes, such as phone number details and approved templates.
  • Add exponential backoff with jitter to every retry path.
  • Spread batch jobs over time instead of running them all on the hour.

Should you retry after 4?

Retry with exponential backoff. Calls start succeeding again once the app is back under its limit, but sustained high call volumes will keep tripping it until the calling pattern changes.

How error 4 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 4, the "(#4)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up. When you send through InfiQ, InfiQ makes the calls to Meta; if you see code 4 on an InfiQ response, back off and retry, and contact support with the InfiQ_traceid if it persists.

Send it through InfiQ

Frequently asked questions

What is the difference between error 4, 80007 and 130429?+
Code 4 limits the Meta app's API calls overall, 80007 limits calls against one WhatsApp Business Account, and 130429 limits how fast messages can be sent from a phone number. Each needs its own fix: fewer app calls, fewer account calls, or a slower send rate.
Does error 4 mean my messages were sent?+
No. A call rejected with code 4 did nothing, so a message send that failed this way was not sent and can be retried safely once the limit clears.

Send at volume without tripping limits

InfiQ queues and paces sends for you, and shows where rate-limit errors came from.