> AI agents: browse all pages at [http://flutterwave-developer-docs-v4-prod.f4b-flutterwave.com/llms.txt](http://flutterwave-developer-docs-v4-prod.f4b-flutterwave.com/llms.txt) or fetch them all at [http://flutterwave-developer-docs-v4-prod.f4b-flutterwave.com/llms-full.txt](http://flutterwave-developer-docs-v4-prod.f4b-flutterwave.com/llms-full.txt).

# Rate Limits
See what happens when you send too many requests, and how to retry.
\
\
Last updated **13 September 2026**
-----------------------------------------------------

{% breadCrumbs %}
#### 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

1. **Use webhooks.** Do not poll a transaction or transfer until the status changes. Wait for the [webhook](/docs/webhooks), then verify the transaction.
2. **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.

{% callout "danger" %}
##### 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.
{% /callout %}
{% /breadCrumbs %}
