API Rate Limits

API Rate Limits

Overview

To ensure fair usage and maintain system reliability, our API service has rate limits in place for all API requests. This article provides details on these limits and how they may affect your API usage.

Rate Limits

Maximum Requests
Per
2
Second
100
Minute
4000
Hour

This means that:
  • You can send up to 2 requests per second, as long as you have not exceeded 100 requests in the past minute or 4000 requests in the past hour.
  • If you exceed any of these limits, your request will be denied with the following HTTP response code:
    • 429 - Too Many Requests
  • If your request is denied due to rate limiting, you will need to wait and retry after some time.

If you are using one of the "Userless OAuth2 Flows" (as per this documentation), then you will be specifying the "AgencyId" URL parameter on every request. In this case, the Rate Limits will apply per "AgencyId".

Best Practices

  • Review your API usage patterns to ensure compliance with these limits.
  • Implement appropriate error handling for 429 responses in your applications.
  • Consider optimizing your API requests to reduce unnecessary calls.

Need Assistance?

If you have any questions or concerns about these limits, please contact our support team by reaching out through our support channels.

    • Related Articles

    • Website Search API Specification

      JSON based API integration The Rezi Web API allows developers to populate customer's website with real time data from the software by sending specific queries to our API endpoints, it also allows you to post customer leads to Rezi. This gives the web ...
    • Enterprise API Form

      The below application can only be submitted by active subscribing customers of Rezi Enterprise whom wishes to utilise the Rezi API. This application process allows us to review, store, process the details submitted and ensure security checks are ...
    • Website Search API Form