Introduction
Flutterwave limits how many requests an account can send so the API stays available. When you pass the limit, the API responds with HTTP 429 (Too Many Requests). The limit applies to the account whose API key made the call.
Avoid hitting the limit
- Use webhooks. Do not poll a transaction or transfer until the status changes. Wait for the webhook, then verify the transaction.
- Poll on a schedule. If you do poll, wait between requests and stop once you have a final status.
Retry after a 429
When you receive 429, wait and try the request again. Increase the wait after each retry so you do not immediately hit the limit again.
Do not bypass the limit
If requests are sent in a way that tries to get around these limits, Flutterwave applies stricter limits to the account.