CuteMarkets Docs

API Reference

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

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

CuteMarkets supports stock market-data endpoints under /v1/stocks/. Stocks are a separate subscription product from options, with their own Stocks API keys, while sharing the same account, response envelope, pagination model, and dashboard billing workflow.

Base path

bash
https://api.cutemarkets.com/v1/stocks/

Authenticate with a Stocks API key:

bash
curl "https://api.cutemarkets.com/v1/stocks/snapshot/AAPL/" \
  -H "Authorization: Bearer YOUR_API_KEY"

Plans

Stocks use the same plan ladder as options, purchased independently.

Stock planRequests / minRequests / dayFreshnessLookbackQuotes
Free105,00015 min delayed3 years-
DeveloperUnlimitedUnlimited15 min delayed7 years-
ExpertUnlimitedUnlimitedLive10 yearsYes
CommercialUnlimitedUnlimitedLive10 yearsYes + commercial applications

Quote endpoints require an Expert or Commercial Stocks API subscription. A paid options subscription does not unlock stock quotes by itself.

Endpoint map

CategoryEndpoints
Snapshots/snapshot/, /snapshot/{ticker}/, /snapshot/movers/{direction}/
Ticker reference/tickers/, /tickers/types/, /tickers/{ticker}/, /tickers/{ticker}/related/
Trades/trades/{ticker}/, /trades/{ticker}/last/
Quotes/quotes/{ticker}/, /quotes/{ticker}/last/
Aggregates/aggs/grouped/{date}/, /aggs/{ticker}/prev/, /aggs/{ticker}/{multiplier}/{timespan}/{from_date}/{to_date}/
Open-close/open-close/{ticker}/{date}/
Indicators/indicators/sma/{ticker}/, /indicators/ema/{ticker}/, /indicators/macd/{ticker}/, /indicators/rsi/{ticker}/

Response envelope

Most stock endpoints return the standard CuteMarkets envelope:

bash
{
  "status": "OK",
  "request_id": "cm_6a7e466379af0a71039d60cc78e72282",
  "results": []
}

Paginated endpoints include next_url when more rows are available. Request that URL as-is with the same Authorization header.

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

Limit defaults and caps

Endpoint familyDefault limitMaximum limit
Trades and quotes100010000
Aggregates500010000
Indicators101000
Ticker reference1001000

How stock workflows fit together

Most stock applications start with reference data, then move into one of three market-data paths. A search box or security master should use ticker reference endpoints first. A dashboard that needs the latest market state should use snapshots. A research or charting workflow should use aggregates, open-close, trades, or quotes depending on the level of detail required.

Treat stock snapshots as current state. They are useful for watchlists, quote panels, movers pages, and stock context beside an options chain. They are not a substitute for a historical bar series. When a chart or backtest needs a price path, request aggregates or open-close data with explicit dates so the result can be reproduced later.

Trades and quotes answer lower-level questions. Trades show executed prints. Quotes show the bid and ask market. If the application is measuring spread, executable context, or market microstructure, quote access matters more than a last trade alone. Because quote endpoints are plan-gated, make the entitlement visible in your integration tests instead of discovering it only in production.

Suggested build sequence

  1. Use ticker search or stock reference to normalize the symbol.
  2. Fetch a ticker snapshot for current state in UI screens.
  3. Fetch aggregates for charts, historical returns, and indicator inputs.
  4. Fetch trades or quotes only when the workflow needs tick-level evidence.
  5. Store the request parameters with downstream calculations so the chart or signal can be reproduced.

This sequence keeps stock reference, current state, and historical evidence separate. It also prevents an options workflow from accidentally using a stock key or a stock quote endpoint when the application actually needs option-contract quotes.

Related docs

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 live and historical workflows for stocks, options, and WebSockets.