API Reference

Read this page with Stocks Data API, Stock Reference, Stock Snapshots, Stock Trades and Quotes, and Stock Aggregates and Indicators.

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

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

Authenticate with a Stocks API key:

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.

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

Endpoint map

Response envelope

Most stock endpoints return the standard CuteMarkets envelope:

{
  "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.

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

Limit defaults and caps

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

• Stock snapshots
• Stock reference
• Stock trades and quotes
• Stock aggregates and indicators
• Rate limits and plans

Stock data workflows usually combine Stock Reference, Stock Trades and Quotes, Stock Snapshots, and Market Data Access Methods. Keep ticker, primary exchange, active status, corporate action, quote, trade, aggregate, SIP timestamp, and condition code definitions aligned.

Stocks workflow notes

The stock API surface is strongest when each object keeps its job. Use reference data to validate tickers, snapshots for current state, trades for prints, quotes for bid/ask context, aggregates for completed bars, and indicators for derived series. Avoid a single "price" field in storage when the workflow needs to explain freshness or tradability.

Stock workflows often feed options workflows. Carry ticker, stock timestamp, session label, adjusted setting, quote entitlement, and signal source into Stock and Options Data Join Workflow. Then validate listed expirations and option chains before selecting contracts. This keeps stock screens, watchlists, and options scanners in one auditable sequence.

Additional implementation review

Review the stocks API workflow as a sequence of named data objects, not as a single helper call. The implementation should preserve ticker reference, snapshot, trades, quotes, aggregates, indicator window, pagination cursor, and product entitlement. Those fields make support tickets, CI fixtures, and replay notebooks easier to compare because every step can point to the exact request and response that created the displayed value.

The main failure mode is that a client can treat the stocks surface as one endpoint instead of a sequence of objects with different freshness guarantees. Before promoting the workflow, run one concrete example through discovery, retrieval, display, logging, and error handling. Keep the resulting artifact beside the code path so future changes can prove they still use the same terminology and the same market-data assumptions.