Rate Limits
The Hyperstack API enforces a per-IP-address rate limit to protect platform stability. The limit applies across all endpoints from a single source IP.
Current limit
| Scope | Limit |
|---|---|
| All endpoints, per source IP | 500 requests per minute |
When the limit is exceeded, every subsequent request from that IP returns 429 Too Many Requests for the remainder of the one-minute window.
Backoff guidance
When the API rejects a request because of rate-limit pressure, retry with exponential backoff:
- Wait at least 1 second before the first retry.
- Double the wait on each subsequent retry.
- Stop retrying after 5 attempts and surface the failure.
Avoid concurrent bursts
Bursting many requests in parallel from a single key is the most common way to hit rate limits. For batch workloads, throttle client-side to a steady request rate rather than firing all requests simultaneously.
Pagination interacts with rate limits
When walking large result sets via pagination, the request rate scales with the page count. For result sets above a few hundred items, increase the page size rather than the request rate.
When to escalate
If your workload genuinely requires a higher rate ceiling than the default, contact [email protected] with the use case, the endpoints affected, and the request volume.