tickerbot.io
Reference

Pagination

Every list endpoint pages via opaque cursor tokens. Walk a result set by passing back the next_cursor you receive on the previous page.

The cursor contract

One pattern across every list endpoint.

List endpoints (/v2/scan, /v2/signals, /v2/signals/{signal}, /v2/tickers, /v2/tickers/{ticker}/history, /v2/tickers/{ticker}/bars/{interval}, /v2/tickers/{ticker}/holdings, /v2/events, /v2/news, /v2/universes, /v2/webhooks, /v2/webhooks/{webhook}/deliveries) return a next_cursor alongside the data. Pass it back to get the next page: as ?cursor= in the query string on GET endpoints, or in the JSON body alongside the rest of the parameters on POST /v2/scan. When there’s no more data, next_cursor is null.

Treat cursors as opaque

Don’t parse, construct or cache them: the server bakes the resume position into each token, so to change the filter, start a new walk.

The one exception is /v2/tickers/{ticker}/bars/{interval}: its cursor is the oldest bar’s epoch-ms timestamp. On a comma list, next_cursor is an object of each symbol’s oldest-bar time (null = finished); to page one symbol further, send its value as cursor with that symbol alone. That holds until 2027-01-12; from then a comma list’snext_cursor is one opaque string to pass back as cursor.

A read with a comma list of tickers in the path (history on 1m to 1w, and holdings) returns one next_cursor that carries each ticker’s own position. Send it back with the same tickers in the same order; each one continues where it stopped, and a ticker that is finished returns an empty list. History on 1q and 1y pages on one shared fiscal label, so every ticker continues from the same period.

Cursors and filters

One rule for every list endpoint.

Send the same params with every page. limit may change; anything else is a 400 naming the param that changed (a cursor sent to another endpoint is a 400 too). A param sent at its default value counts as left out, so order=ticker on page 2 continues a first page that sorted by ticker by default. Each value is compared as the API reads it: a list sent as an array or as a, b, dir=DESC and dir=desc, aapl and AAPL are the same value. Text in q, condition and search is compared as written, apart from spaces at either end. A cursor resumes only the read that returned it, so to change a filter, the order or select, drop cursor and start a new walk. Bars is the exception above: its cursor is a bar time, a position like to, so it is not checked against the other params.

Page size

Pass ?limit= to change page size. Each endpoint page states its default and maximum (history defaults to 252, one trading year). A symbol list in the path takes up to 50 symbols, and limit applies to each one. History answers a page over 25,000 points in all (tickers × limit) with a 400: 50 tickers page at up to 500 each, 25 at the full 1,000. With select=* the cap is 1,000 points: an explicit limit over it is a 400, and the default is lowered to fit (5 tickers get 200). /v2/tickers/NVDA,AMD,AVGO and its coverage read return one object per symbol and don’t page.

One rule sets the maximums. Market-wide results (scan, the tickers list, events, news, the signals catalog and a signal’s matches) page at 100 rows. Data for tickers you name (history, bars, holdings) pages at 1,000 points. Account lists (universes, webhooks, deliveries) page at 100; your custom signals page with the signals catalog. A list of tickers in one call takes up to 50. Where a maximum is higher today, it drops on 2027-01-12 (see Deprecations); a larger limit is clamped to the maximum. History’s points cap above is the one limit that answers a 400 instead. Until 2027-01-12 a List signals call with no limit returns the whole catalog in one page.

A rollup (group_by on /v2/events and /v2/news) doesn’t page: it returns up to limit groups (max 1,000), and truncated: true when there are more. Without limit, a rollup returns every group up to 1,000. Raise limit or narrow the window. The 1,000 maximum stays: only the list mode’s maximum drops to 100 (Deprecations).

Time windows

One rule for from and to on every read that takes them.

A bare date (YYYY-MM-DD) covers that whole day: from starts at its first moment and to ends at its last, so from and to on the same date return that day. On market data the day is the ticker’s market day: the ET day for stocks and ETFs, the UTC day for crypto, FX and rates, which trade around the clock. On account data (webhook deliveries) it is the UTC day.

A timestamp is exclusive at the end: from includes it, to stops strictly before it. Bars, history and webhook deliveries include a timestamp to until 2027-01-12, and follow the rule from then (see Deprecations).