Rate Limiting
Rate Limits
To ensure the stability and availability of our Real Estate API for all users, we have implemented rate limits. These limits restrict the number of requests a client can make within a specific time period.
Basic Limit
Standard limit per API key: 2000 requests per minute
Rate Limit Headers
With each response, the API sends the following HTTP headers to provide information about your current rate limit status:
| Header | Description |
|---|---|
| X-RateLimit-Limit | The maximum number of requests you can make in the current time window |
| X-RateLimit-Remaining | The number of requests remaining in the current time window |
| Retry-After | The duration in seconds a client must wait before retrying the request. (Sent only if API Key hits the limit). |
Refilling Rate Limit
The number of available requests is refilled proportionally every few seconds.
Example:
The API key is allowed to make 120 requests per minute.
Suppose the number of allowed requests drops to zero. In that case, the Real Estate API will return a 429 Too Many Requests response, with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset HTTP headers.
After 5 seconds, 10 requests will be refilled (calculated as 120 req/min ÷ 60 seconds × 5 seconds = 10 requests).
Best Practices to Avoid Rate Limit Violations
- Implement Exponential Backoff: When receiving a 429 error, wait exponentially longer between retry attempts.
- Caching: Store frequently requested data locally to avoid repeated API calls.
- Client-Side Rate Limiting: Implement your own rate limiting in your client to ensure you don't exceed the limit.