Rate Limits

The Hyperswitch API has multiple checks in place to enhance its stability when faced with sudden surges of incoming traffic. Merchants who send numerous requests in rapid succession could encounter error responses indicated by the status code 429.

The default rate limit for all Hyperswitch APIs is 80 requests per second. Reach out to [email protected] if you have a requirement for higher limits.

How to handle rate limits

Effectively handling 429 errors is crucial for maintaining a seamless user experience.

• Implement retry mechanisms with progressively increasing intervals to avoid overwhelming the system with repeated requests.

• Use monitoring tools to track usage patterns and gain insights for adjusting request rates and capacity.

• Adopt a well-orchestrated strategy for managing 429 errors to prevent disruption and communicate limitations transparently to users.

Understanding API locking

If you see a 429 error with the following message, it is due to API locking and not due to rate limiting:

Error message

At this moment, access to this object is restricted due to ongoing utilization by another API request or an ongoing Hyperswitch process. Retry after some time if this error persists.

API locking is a protective feature that prevents concurrent operations on the same object which could lead to inconsistent outcomes. When an API lock is triggered, access to the object is temporarily paused to preserve integrity and performance. If you encounter this error, retry after some time.

---

Suggest edits: https://github.com/juspay/hyperswitch/edit/main/api-reference/essentials/rate_limit.mdx Raise issue: https://github.com/juspay/hyperswitch/issues/new?title=Issue%20on%20docs&body=Path:%20/essentials/rate_limit

Related:

• Error Codes: https://api-reference.hyperswitch.io/essentials/error_codes

• Go-live Checklist: https://api-reference.hyperswitch.io/essentials/go-live