Errors & Support
Common API response codes and support guidance.
Error Codes
| Status Code | Description |
|---|---|
200 OK | Request successful. |
400 Bad Request | Business-rule validation failed after request parsing (for example: from > to, date range longer than 366 days, data requested before 2025-01-01, batch size over 50, or invalid ticker values in batch foreign-flow requests). |
401 Unauthorized | Bearer token missing. |
403 Forbidden | Authentication or account access failed after a token was provided (for example: inactive or expired API key, expired subscription, monthly quota exhausted, or Free plan daily quota exhausted). |
422 Unprocessable Entity | FastAPI/Pydantic request validation failed before route logic ran (for example: missing required fields, malformed dates, or enum/pattern mismatches). |
429 Too Many Requests | Per-minute rate limit exceeded. |
500 Internal Server Error | An unexpected server-side error occurred. |
Most error responses expose a human-readable detail field. Validation failures (422) return a structured detail array. Some route-level 500 responses currently return { success: false, data: null, error: "Internal server error" } instead of a detail field, so do not assume every non-2xx response uses exactly the same body shape. See the Limits & Quotas page for the headers that carry quota and rate-limit status.
Support
For technical issues or to request a higher usage limit, please contact the Index Alpha Team.