Get bars

Query parameters

Returns

Status codes

Notes

• Bars are the historical stock data: daily bars run back to each ticker's first day of coverage (2003 for the oldest equities; see Tickers for depth by class), delisted names keep their bars, and intraday bars run from 1-second up. History is not only price: ?asof= on any state read rewinds a whole row, and Series pulls any columns over time on one grid.
• Supports point-in-time (asof) and back-paging (before/limit). 1d and 1h cover the full universe with full history; sub-hour intervals cover the active universe and back-fill on demand. Pass a comma-separated symbol list for a bulk response keyed by symbol.
• Prices are split-adjusted at every interval, and re-adjusted retroactively when a later split lands: a bar from before a 1-for-10 reverse split shows the tape price times 10, so a stock that closed at $2.14 that day reads $21.40 once the split is in. There is no unadjusted option today. To match a fill from your broker, scale by the splits dated after that bar; /v2/events?kind=split lists them.
• Sub-hour bars (1s through 30m) include pre-market and after-hours prints, bucketed by the SIP report time rather than the execution time. On thin names an off-exchange trade can be reported an hour or more after it executed, so a pre-market bar can carry a wick far from where the market was in that minute. 1d high/low counts regular-session trades only, per SIP rules, so the daily bar never shows those wicks. Compute intraday statistics such as MAE/MFE from regular-session bars (09:30 to 16:00 ET); there is no session filter today.
• Bars is its own family on purpose, alongside Series: sub-hour intervals, fetch-on-miss coverage, and the compact chart-ready shape live here. To get OHLCV *joined with* indicator or boolean signals on one grid, read series with columns=close,rsi_14,… instead.
• Available at all intervals. The asof point-in-time param is unlimited-depth — see As-of queries.
• 2h/4h are rollups of the hourly store and 1w/1mo of the daily store (calendar buckets, t = bucket start), so they carry the same universe and depth as 1h and 1d. Added in v2.32.0 — until then only the dashboard chart could draw them.
• 1d/1h cover the full universe with full history. Sub-hour (1m/5m/15m/30m) is pre-loaded for the active universe (the minute tier); a symbol outside it is served on demand: the first call fetches from the provider (~3–10s) and stores the result, later calls are sub-second. Each on-demand request fills up to 31 days ending at to/before/now — page further back with next_cursor. That first response carries a note saying so. /coverage reports the same as minute_tier.on_demand — included:false there is not "no data".
• 1s (1-second) bars are served on demand: from our store when it already covers the request through the latest session, otherwise passed through from the provider and served in the same call (the store is filled by earlier requests, so a full page of older stored bars is never mistaken for the latest ones). Second data is not bulk-backfilled — it accumulates as it is requested. Best paired with a tight before+limit window. When the vendor pass-through is unavailable, the response says so: a note (single-symbol) / notes[symbol] (bulk) flags that the range came from the local store only and may be under-covered.
• coverage is covered, no_data (universe-wide interval with nothing for the symbol), or not_in_minute_tier — a gap is always explicit, never a silent empty array.
• Paging is before + limit, with cursor/next_cursor as sugar. Accepts epoch-ms or YYYY-MM-DD; bars come back oldest-first.
• For an explicit historical window, pass from/to (inclusive; same bound semantics as series) and page inside it with cursor. from/to does not combine with asof (point-in-time) or before (tail-paging) — contradictory range controls are a 400, never a silent pick.
• The response echoes adjusted and session, so a cached page is self-describing.
• Path history: this was /v2/tickers/{ticker}/bars/{interval} until 2026-09-14. That spelling keeps serving forever as an alias — same handler, same response, no deprecation headers.

More examples

curl "https://api.tickerbot.io/v2/bars/AAPL,MSFT/5m?limit=2" \
  -H "Authorization: Bearer YOUR_KEY"

{
  "as_of": "2026-08-11T22:47:23.948Z",
  "interval": "5m",
  "count": 2,
  "bars": {
    "AAPL": [ { "t": 1786487400000, "o": 304.975, "h": 304.984, "l": 304.955, "c": 304.975, "v": 890 },
              { "t": 1786487700000, "o": 304.975, "h": 304.975, "l": 304.975, "c": 304.975, "v": 2622 } ],
    "MSFT": [ { "t": 1786487400000, "o": 501.9,   "h": 501.9,   "l": 501.846, "c": 501.846, "v": 617 },
              { "t": 1786487700000, "o": 501.845, "h": 501.845, "l": 501.82,  "c": 501.82,  "v": 826 } ]
  },
  "coverage": { "AAPL": "covered", "MSFT": "covered" }
}