API
Errors, limits, and idempotency
Handle validation, authentication, plan, rate-limit, duplicate, and processing errors safely.
LiveAll plans
Common status codes
| Status | Meaning |
|---|---|
| 400 | Invalid request or failed input validation |
| 401 | Missing, expired, or invalid authentication |
| 403 | Plan, scope, ownership, or role does not allow the action |
| 404 | Resource unavailable to the caller or retired endpoint |
| 409 | Conflict such as team capacity or duplicate state |
| 429 | Rate or usage limit reached |
| 500/503 | Unexpected or temporarily unavailable service |
Retry safely
- Do not retry validation, authentication, or plan errors without changing the request or entitlement.
- Use exponential backoff for explicit transient errors.
- Respect Retry-After when present.
- Analysis creation and webhook handling include duplicate and idempotency protections, but clients should still avoid parallel duplicate submissions.
- Never invent a force or bypass field.