Diagnosing and Resolving Facebook Graph API Rate‑Limit (HTTP 429) Errors

Recognizable condition

Your application receives an HTTP 429 Too Many Requests response from a Facebook Graph API endpoint. The response body contains a JSON object with an "error" field where "code" is 4 and the message indicates that the rate limit has been exceeded.

Cause and diagnostic table

Possible cause	What to look for
Burst of requests exceeding per‑app or per‑user limits	Sudden spike in call count; headers show usage approaching the limit.
Missing or stale access tokens causing retries	Repeated 401 responses followed by immediate retries that add to traffic.
Misconfigured batch requests multiplying call count	Each batch item is counted as a separate call; large batches quickly exceed limits.

Ordered checks

1. Inspect response headers – Look for X‑App‑Usage and X‑Business‑Use‑Case‑Usage (or Retry‑After) to see current consumption versus the limit.
2. Review recent call volume – In the Facebook App Dashboard, navigate to Insights → API Usage and check the graph for the time window when the 429 appeared.
3. Verify token validity – Confirm that the access token used in the request is not expired and that your refresh logic runs before each batch of calls.
4. Search for unintended loops or retries – Examine application logs for repeated calls to the same endpoint with identical parameters, especially after a 429 or 401.

Fixes tied to findings

• If headers show limit approached
  • Implement exponential back‑off.
  • Respect the Retry‑After value (seconds) before retrying.
  • Optionally throttle outgoing requests to stay safely below the limit.
• If tokens are stale
  • Refresh the user or page access token immediately before each request batch.
  • Store the new token securely and use it for subsequent calls.
• If batch size is too high
  • Reduce the batch to ≤ 50 calls (Facebook’s recommended maximum).
  • Alternatively, split large batches across multiple time windows, waiting for the Retry‑After interval between them.

Escalation criteria

Consider requesting higher tier limits or contacting Partner Support when:

• You have applied exponential back‑off and respected Retry‑After for more than 5 minutes and still receive 429 responses.
• API usage charts show sustained spikes that exceed your allocated limits even after optimizing token handling and batch sizes.

In these cases, submit a limit increase request via the App Review process or open a support ticket with your Facebook Partner Engineer, providing the app ID, the affected endpoint, and the observed usage data.