Errors & Responses

Standard HTTP status codes and JSON error bodies. Always check the status code before parsing the response.

HTTP Status Codes

200

Request processed. Response contains rows, next_start and data.

400

Missing or invalid parameters. Check the detail field.

401

Missing X-API-Key header.

403

Invalid API key, daily credit limit exceeded, or date range not allowed for your plan.

404

Symbol not found in our database, or no data available for the requested date range.

422

Feature parameters are invalid (e.g. window larger than the available bars).

429

Per-minute credit budget exceeded, concurrent backtest cap reached, or daily AI assistant cap hit. Wait 1 second and retry, or upgrade your plan.

500

Unexpected error on our side. If it persists, contact support with the request details.

All error responses follow this structure:

{
  "detail": "Simbolo 'XYZ' no encontrado en la base de datos."
}

The detail field always contains a human-readable description of the error.

A 200 OK response can contain null values. This is expected:

hourglass_top

Rolling features return null for the first window - 1 rows while accumulating history.

weekend

Weekends, holidays and trading halts result in missing bars which propagate as null.

functions

Some features (HMM, PCA) return null when the window has insufficient samples or zero variance.