Skip to main content
ApartmentIQ enforces rate limits to keep the API reliable for all customers. Limits can vary by endpoint, authentication context, or account configuration, so don’t hard-code a fixed request count into your integration. When you exceed a request rate limit, the API returns 429 Too Many Requests with response headers that explain when you can try again.

​
Rate limit headers

HeaderHow to use it
X-RateLimit-LimitThe limit that applied to the request. Treat this as informational and avoid assuming it is the same for every account or endpoint.
X-RateLimit-Reset-AfterThe rate limit window length, in seconds.
X-RateLimit-ResetThe Unix timestamp when the current window resets.
Retry-AfterThe number of seconds to wait before retrying the request.

​
Example 429 response

HTTP/1.1 429 Too Many Requests
X-RateLimit-Limit: <limit>
X-RateLimit-Reset-After: <window_seconds>
X-RateLimit-Reset: <reset_unix_timestamp>
Retry-After: <seconds_until_retry>
Content-Type: text/plain

You have exceeded the rate limit for this API.
If you receive 429, wait at least the Retry-After value before sending another request. For high-volume workflows, use exponential backoff, avoid automatic immediate retries, and consolidate requests where an endpoint supports batching.

​
Understanding where you are in the limit

The API does not currently return a remaining-request counter. Use Retry-After and X-RateLimit-Reset on 429 responses to determine when requests can resume, and use X-RateLimit-Limit to understand the limit that was applied when throttling occurred.