Rate Limits and Request Timeouts

Understanding API rate limits, timeouts, and failure strategies is crucial for optimizing the performance and reliability of your integration. Adherence to these guidelines prevents your application from being blocked due to excessive requests. Read on to learn how to work with our API, recommended retry mechanisms, and how to ensure smooth and efficient interaction with our API.

Usage of Hover's API is subject to rate limits. By limiting the number of requests by integration, we protect our internal infrastructure by being negatively affected by applications that are not operating within our terms and conditions.

Hover Rate Limit

The API rate limit is set to 120 API requests per minute (RPM) OR 7200 requests per hour. Exceeding this limit will result in a 429 Rate Limit Exceeded error message, which may temporarily block further requests from being processed. To ensure seamless integration, it is recommended to implement error handling and retry logic in your application to manage potential rate limit exceedances.

Tips For Working Within Rate Limits

• Log your requests and response codes within your integration to see how many requests you are making over the course of your highest volume hour(s).
• If you're exceeding the 120 requests per minute rate limit, add small periods of wait/sleep times between your API requests.

Timeouts

The API timeout for all operations is set to 60 seconds. If a request exceeds this duration, it will automatically be terminated.

Recommended Retry and Failure Approach

Our recommended retry and failure approach is to implement an exponential backoff strategy. Exponential backoff is a method where the wait time between retries increases exponentially, typically starting with a small delay and doubling with each subsequent retry. Ensure your application implements appropriate maximum retry limits and handles failures gracefully if the issue persists beyond the retry attempts.