CuteMarkets Docs

API Reference

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

Tip: open /docs/stock-aggregates-indicators.md directly for raw markdown (easy copy/paste into an LLM).

Stock aggregate endpoints return OHLC bars, previous day bars, grouped market bars, and daily open-close data. Indicator endpoints return SMA, EMA, MACD, and RSI series for a ticker.

Grouped daily bars

bash
GET /v1/stocks/aggs/grouped/{date}/
bash
curl "https://api.cutemarkets.com/v1/stocks/aggs/grouped/2026-05-06/?adjusted=true" \
  -H "Authorization: Bearer YOUR_API_KEY"

Previous day

bash
GET /v1/stocks/aggs/{ticker}/prev/
bash
curl "https://api.cutemarkets.com/v1/stocks/aggs/AAPL/prev/?adjusted=true" \
  -H "Authorization: Bearer YOUR_API_KEY"

Custom bars

bash
GET /v1/stocks/aggs/{ticker}/{multiplier}/{timespan}/{from_date}/{to_date}/
bash
curl "https://api.cutemarkets.com/v1/stocks/aggs/AAPL/5/minute/2026-05-01/2026-05-06/?adjusted=true&limit=5000" \
  -H "Authorization: Bearer YOUR_API_KEY"

timespan supports the documented bar intervals such as minute, hour, day, week, month, quarter, and year.

Open-close

bash
GET /v1/stocks/open-close/{ticker}/{date}/
bash
curl "https://api.cutemarkets.com/v1/stocks/open-close/AAPL/2026-05-06/?adjusted=true" \
  -H "Authorization: Bearer YOUR_API_KEY"

Indicators

bash
GET /v1/stocks/indicators/sma/{ticker}/
GET /v1/stocks/indicators/ema/{ticker}/
GET /v1/stocks/indicators/macd/{ticker}/
GET /v1/stocks/indicators/rsi/{ticker}/
bash
curl "https://api.cutemarkets.com/v1/stocks/indicators/sma/AAPL/?window=20&timespan=day&limit=100" \
  -H "Authorization: Bearer YOUR_API_KEY"

Limits and lookback

Aggregate endpoints default to limit=5000 and clamp to limit=10000. Indicator endpoints default to limit=10 and clamp to limit=1000.

Requests are checked against the stock subscription lookback: 3 years for Free, 7 years for Developer, and 10 years for Expert or Commercial.

Choosing bars, open-close, or indicators

Aggregates are best when the model needs a price path. Open-close is best when the model needs a single daily session summary. Indicators are best when the application wants server-calculated rolling features with consistent timestamp and pagination behavior.

NeedEndpoint familyNotes
Intraday chartCustom aggregatesChoose minute or hour bars and use explicit dates.
Market-wide daily reviewGrouped daily barsOne date across many tickers.
Previous-session contextPrevious day barsUseful for watchlist cards and percent-change displays.
One-session summaryOpen-closeClean daily OHLC with adjusted toggle.
Rolling featureIndicatorsSMA, EMA, MACD, or RSI with window parameters.
bars indicator Path first, feature second

Reproducibility notes

Store the input parameters that created each feature: ticker, timespan, multiplier, date range, adjusted flag, indicator type, window values, and series type. Without those fields, two dashboards can display the same indicator name while using different source bars or different warm-up behavior.

Choosing the right bar width

The bar width should match the decision horizon. Intraday tools usually need minute or hour bars, while allocation dashboards and end-of-day research usually need daily or weekly bars. A five-minute bar chart and a daily indicator can both be correct, but they should not be compared as if they measured the same behavior.

For production systems, define the allowed bar widths in the application layer. This prevents a user from accidentally mixing 1/minute, 5/minute, and 1/day outputs in the same ranking table. When the chart changes timespan, invalidate dependent indicators unless the indicator request explicitly uses the same source bar configuration.

Aggregates versus open-close

Aggregates are better when the application needs a sequence of bars. Open-close is better when the application needs one clean daily session summary. If a report shows "today's open and close" for a single date, open-close is direct and easy to explain. If a report computes returns, volatility, moving averages, or intraday behavior, aggregates give the model the path it needs.

Indicator workflow

Indicators are server-calculated features. Use them when you want consistent SMA, EMA, MACD, or RSI behavior without reimplementing rolling calculations in every client. Still store the source parameters. The same indicator name can imply different values when the window, timespan, adjusted flag, or series type changes.

A robust stock analytics workflow usually reads as follows: fetch reference data for the ticker, fetch aggregates for the visible chart, fetch indicators for selected overlays, and store every query that produced a displayed value. That gives a user interface that is fast while keeping the research trail reproducible.

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.