CuteMarkets Docs

API Reference

Everything you need to integrate options and stocks market data, build faster, and scale.

Tip: open /docs/overview.md directly for raw markdown (easy copy/paste into an LLM).

Overview

CuteMarkets provides a clean, developer-friendly REST API for U.S. options and stocks market data - built for quants, traders, and AI applications. Data is delivered through a simple HTTP API with consistent authentication, response envelopes, and pagination.

Base URL

bash
https://api.cutemarkets.com

All endpoints are versioned under /v1/.

WebSocket streams are available at wss://api.cutemarkets.com/v1/ws/{market}/ on Expert (€99/mo yearly or €119/mo monthly) and Commercial (€399/mo yearly or €469/mo monthly) plans only. See WebSockets for authentication, subscription, and single-connection rules.

OpenAPI

The OpenAPI 3.1 specification is published at https://cutemarkets.com/openapi.json. See OpenAPI for scope and usage notes.

Quick Start

bash
curl \
  "https://api.cutemarkets.com/v1/options/chain/NFLX/?limit=1" \
  -H "Authorization: Bearer YOUR_API_KEY"
bash
curl \
  "https://api.cutemarkets.com/v1/stocks/snapshot/AAPL/" \
  -H "Authorization: Bearer YOUR_API_KEY"

Sample Response (Option Chain)

bash
{
  "status": "OK",
  "request_id": "cm_adce10cb073745c7b859fc8131b203b0",
  "results": [
    {
      "break_even_price": 100.025,
      "details": {
        "contract_type": "call",
        "expiration_date": "2026-04-02",
        "strike_price": 100,
        "ticker": "O:NFLX260402C00100000"
      }
    }
  ]
}

What's available

CategoryEndpoints
Option ChainFull chain snapshot by underlying ticker
Contract snapshotOne contract snapshot (Greeks, IV, quote, trade, underlying)
ContractsList and detail view of contracts
Options tradesTick-level options trade data
Options quotesBid/ask quotes - Expert or Commercial options plan
StocksSnapshots, movers, ticker reference, trades, quotes, grouped bars, open-close, aggregates, indicators
AggregatesOHLC bars at any timespan
IndicatorsSMA, EMA, MACD, RSI
ReferenceTicker search, expiration dates, stock ticker reference
WebSocketsLive event streams for options and stocks - Expert or Commercial only

Research and backtesting

If you are building a simulator instead of a simple data integration, start with the Backtesting Framework knowledge base. It covers the architecture spine for realistic options backtests: point-in-time contract discovery, causal replay loops, quote-aware execution, contract selection, robustness checks, and regression tests.

The public CuteMarkets backtesting package is documented in cutebacktests.

Response format

Every response follows a standard envelope:

bash
{
  "status": "OK",
  "request_id": "cm_6a7e466379af0a71039d60cc78e72282",
  "results": [ ... ],
  "next_url": "https://api.cutemarkets.com/v1/options/contracts/?page=..."
}

request_id is unique to every request and useful for debugging. On a few routes (for example Contract snapshot), results is a single object instead of an array.

The next_url field appears only on paginated list endpoints when more data is available after the current page. It is a full URL you can request as-is with the same Authorization header. When there is no next page, next_url is omitted.

Error responses

bash
{
  "status": "ERROR",
  "request_id": "cm_abc123...",
  "error": {
    "code": "unauthorized",
    "message": "Invalid or inactive API key."
  }
}

See Error Handling for the full list of error codes. Start stock integrations at Stocks REST Overview.

System Status

CuteMarkets provides a public health endpoint you can poll from your own uptime monitors — no authentication required.

bash
curl https://api.cutemarkets.com/v1/status/
bash
{
  "status": "ok",
  "request_id": "cm_a1b2c3...",
  "services": {
    "api":      { "status": "ok" },
    "database": { "status": "ok", "latency_ms": 1.42 },
    "cache":    { "status": "ok", "latency_ms": 0.87 }
  }
}

status is either "ok" (all systems nominal) or "degraded" (one or more services impacted). You can also view the live dashboard at cutemarkets.com/status.

Next steps

Move from the docs into the product workflow

If you are evaluating the API rather than implementing a specific endpoint right now, the product pages map the live, historical, and chain workflows directly.