Introductionv1
Rate Limits
Limits protect the analysis pipeline and keep latency predictable across the workspace. They apply per API key and are reported on every response, so you can back off gracefully rather than guess.
Default limits
| Plan | Analyses / min | Requests / min | Concurrency |
|---|---|---|---|
| Clinic | 20 | 120 | 4 |
| Hospital | 200 | 1,200 | 32 |
| Health System | Custom | Custom | Custom |
Response headers
Every response carries the current window state. Read Voxtar-RateLimit-Remaining and back off before you hit zero.
Voxtar-RateLimit-Limit: 200Voxtar-RateLimit-Remaining: 187Voxtar-RateLimit-Reset: 41
Exceeding a limit
Over-limit requests return 429 Too Many Requests with a Retry-After header (seconds). The SDKs honor it automatically with exponential backoff and jitter; if you call the REST API directly, wait Retry-After seconds before retrying.
{"error": {"type": "rate_limit_exceeded","message": "Analysis rate limit reached. Retry after 41s.","retry_after": 41}}