Rate limits
Requests are rate limited per API key. Limits protect the platform and are applied independently of the source IP, so distributing calls across machines does not raise your ceiling.
When you exceed a limit, the API responds with 429 Too Many Requests. Back off
and retry after a short delay.
Limits by operation
Section titled “Limits by operation”| Operation | Limit |
|---|---|
Create instance (POST /instances) | 30 / hour |
| Power actions (start / stop / restart) | 60 / minute |
| Reinstall, reset password, resize | 6 / hour |
| Snapshots (create / restore) | 6 / hour |
| Backups (restore) | 6 / hour |
| Rescue mode (enter / exit) | 6 / hour |
| Reverse DNS | 30 / minute |
| Hostname change | 30 / hour |
| Mount ISO | 12 / hour |
Read-only endpoints (listing, status, metrics) are not rate limited under normal use, but please poll responsibly.
Handling 429
Section titled “Handling 429”- Honour any
Retry-Afterheader if present. - Use exponential backoff with jitter for retries.
- For bulk workflows, serialise mutating calls rather than firing them in parallel.
# Example: a 429 responseHTTP/1.1 429 Too Many Requests{"error": "Rate limit exceeded: 6 per 1 hour"}