REST API

The REST API serves the same data as the MCP server as plain JSON over HTTPS — ideal for scripts, backends, and dashboards. Every endpoint lives under https://api.equibles.com/v1.

Base URL & authentication

All requests go to https://api.equibles.com/v1 and must include your API key as a Bearer token (or an ?api_key= query parameter — see Authentication).

curl "https://api.equibles.com/v1/stocks/AAPL/prices?startDate=2024-01-01" \
  -H "Authorization: Bearer eq_your_api_key"

Pagination

List endpoints accept limit and offset query parameters and wrap the rows in a data array alongside a meta object. Use meta.hasMore to decide whether to fetch the next page (increase offset by limit). The maximum limit is 500.

{
  "data": [ /* rows */ ],
  "meta": { "limit": 50, "offset": 0, "count": 50, "hasMore": true }
}

Response format

• All responses are JSON with camelCase field names.
• Dates are ISO yyyy-MM-dd strings.
• Successful reads return 200; see Rate limits & errors for non-2xx.
• v1 is stable — breaking changes ship under a future version, never inside v1.

Errors & rate limits

Non-2xx responses return a consistent error envelope, and requests count against a shared daily limit across REST and MCP. Full details are on Rate limits & errors.

{ "error": { "code": "not_found", "message": "Stock not found.", "status": 404 } }

Reference

• Endpoint reference — all endpoints, grouped by domain.
• Interactive docs — try endpoints live in Swagger UI.
• OpenAPI spec — generate a client from v1.json.