Learn about API rate limits and how to work with them.
Why Rate Limits?
- Prevent server overload and uphold the reliability and responsiveness of our API by controlling the rate at which requests can be made.
- Promote fair usage among all consumers of the Clik2pay API through rate limits, ensuring that no single user or application monopolizes the available resources.
- Enhance the overall security of our platform by implementing rate limits, which act as a safeguard against potential malicious activity or unintentional excessive usage.
Rate Limits
The Clik2pay API uses safeguards against bursts of incoming traffic to help maximize its stability. Merchants who send too many requests in quick succession will see error responses that show up as status code 429 "Too Many Requests". We limit the API for the following:
- A rate limiter that limits the number of requests received by the API within any given second. For the request payment API, the rate limit is 10 requests per second.
- A concurrency limiter that limits the number of requests that are active at any given time. The concurrency limit is set to 5.
We may reduce limits to prevent abuse, or increase limits to enable high-traffic applications.