Rate limits
Limits are applied per key, so one busy integration cannot starve another key in the same workspace.
| Operation | Limit |
|---|---|
| Reads | 600 requests/minute |
This is the same ceiling on every plan that includes API access — Spectrum, Aurora and Cosmos all get the same throughput. Higher tiers do not buy a higher limit today.
Headers
Every response carries:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | The ceiling for this window |
X-RateLimit-Remaining | Requests left in the current window |
X-RateLimit-Reset | When the window resets (epoch milliseconds) |
X-Novex-API-Version | The API version that served the request |
A 429 additionally carries Retry-After, in seconds.
Backing off
When you get a 429, wait for Retry-After before retrying. Retrying
immediately will simply consume the next window too. If you are paginating a
large collection, prefer a larger limit (up to 100) over more requests.
If you need a higher ceiling for a specific integration, talk to us — the limit is a starting point, not a fixed property of the product.