Rate Limiting

This section of the docs discusses all rate limits applicable to our APIs.

Introduction

At Flutterwave, We always strive to provide the best payment APIs with a 99.9999% uptime for all our merchants. In order to do this and safeguard you against burst of incoming traffic, We have implement rate limits across some endpoints.

If you are being limited, you would receive a 429 (Too many requests) HTTP code response.

📘

Limits

Limits are applied on directly on the user account. If a user has multiple Flutterwave for Business (F4B) accounts, only the flagged account is limited.

Endpoint	F4B version	Rate Limited	Number of requests	Window period (mins)	Cool off period (mins)
/flwv3-pug/getpaidx/api/v2/verify	v2	Yes	300	1	30
/v3/transactions/id/verify	v3	No	N/A	N/A	N/A

Preventing Rate Limiting

1. Webhooks: Rather than poll perpetually, we recommend using listening for webhooks for changes in status of a transaction. To learn more, visit our webhooks section for V2 and V3

2. Structured polling: Do not poll indefinitely to get the status of a transaction/transfer. Instead call an endpoint in a structured and sparse manner or in response to an event.

Handling Rate limits

To gracefully handle rate limits, the best option is to look out for HTTP response code 429 and implement a graceful retry. This mechanism should have a backoff mechanism to ensure the rate limits are again not exceeded.

For more information about Rate Limits, please contact us @ [email protected]