We implement rate limting in Cashfree APIs to control the number of requests a client can make within a specified timeframe. This ensures fair usage among all users, protects the API infrastructure from abuse or spikes in traffic, and maintains consistent performance. Each API endpoint may have its own rate limit, defined by the maximum number of requests allowed per minute or hour. You can view the specific rate limits for each API through these links:Documentation Index
Fetch the complete documentation index at: https://www.cashfree.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Payment API Rate limits
SecureID API Rate limits
Response Headers
Cashfree APIs include rate-limiting information in the response headers, such as:X-RateLimit-Limit: The maximum number of requests allowed in the current window.X-RateLimit-Remaining: The number of requests remaining in the current window.X-RateLimit-Reset: The time (in seconds) until the rate limit resets.
Throttling
If the limit is exceeded, the API returns a429 Too Many Requests status code. Clients are advised to respect the retry-after time mentioned in the response headers before sending further requests.
Requesting rate limit increases
If your application requires higher rate limits, you can submit a request through the support form or contact your account manager directly. When you submit your request, include the following information:- Your merchant ID.
- Current usage patterns and volumes.
- Expected future usage requirements.
- Business justification for the increase.
Best Practices
- Implement exponential backoff strategies to handle retries gracefully.
- Monitor API usage and avoid excessive calls by caching responses where applicable.
- Use API keys responsibly and ensure the application logic adheres to the documented rate limits.