Upgraded docs version is here ✨

Your documentation experience is getting an upgrade. Check it out now!

Go To Beta

Docs upgrade is here. Check it out!

Go To Beta
API ReferenceIntegrationsKnowledge Base

Pagination & Rate Limiting

Usually, when you make calls to the Razorpay APIs, there will be a large volume of responses. You can paginate the results to ensure that these responses are easier to handle.


If you want to get information on all the payments received from customers, the result could be a massive response with hundreds of payments.

Use a combination of the query parameters given below to receive a specific number of records in the API response.

Query Parameters🔗

integer Timestamp, in Unix, after which the entities are created.
integer Timestamp, in Unix, before which the entities are created.
integer Number of entities to fetch. Default is 10. This can be used for pagination, in combination with skip.
integer Number of entities to skip. Default is 0. This can be used for pagination, in combination with count.

Rate Limits🔗

Razorpay uses a request Rate Limiter to limit the number of requests received by the API within a time frame. Rate Limiter helps maintain system stability during heavy traffic loads.

  • While integrating with any APIs, watch for HTTP status code 429 and build the retry mechanism based on the requirement.
  • Use an Exponential backoff/stepped backoff strategy to reduce request volume and stay within the limit.
  • Add some randomisation within the backoff schedule to avoid the thundering herd effect.