tickerbot.io
Reference

Changelog

Notable changes to the API, newest first. A breaking change is listed with the date it takes effect; Deprecations lists every change still to come.

Releases

v2.98.02026-11-13
  • Fixed
    History dates crypto, FX and rate daily bars on their own day. Each close (and the other OHLCV names) was dated one day early, so a window starting on a date returned a row from the day before, and a mix with stored signals could put a Friday bar on a weekend day.
  • Fixed
    An as-of Get a ticker lists only the signals it serves in _meta.sources.<grain>.contributed. On a blended read it also named stored columns that are not published signals.
  • Fixed
    A Query events cursor keeps the read it started. A kind=signal walk with q lost its grain on page 2 and read another grain; a ticker, select, join or grain added beside a cursor that did not carry one now answers 400 naming it, where it narrowed or reshaped the walk.
  • Fixed
    A request body that is not valid JSON answers 400 bad_request with a request_id. It answered 400 internal, the code for a retryable server error.
  • Fixed
    Query news echoes ticker and tickers as sent: null when no list was sent, both keys always. A universe read echoed its members there.
  • Fixed
    Deleting a built-in signal answers 404 read-only even when one of your custom signals uses it; it answered 409 and offered ?force=true.
  • Fixed
    History select=* serves an OHLCV name or a custom signal sent beside it (*,close,volume). They were checked and then left out.
  • Fixed
    Intraday Bars for a range before 1970 answer 200 no_data, not a 503 that never clears.
  • Fixed
    grain=auto, the default, is accepted on a live Scan, Get a signal and Get a ticker (it was a 400 there).
  • Fixed
    More cursors resume when only the spelling changed: sort_by=market_cap and order=market_cap across pages; ticker and tickers on Series; asset_class and exchange in another case or order on List tickers; every webhook status named; select names in another case on History, Series, Get a ticker and Get a signal.
  • Fixed
    Clearer errors: an @> value that is not JSON names the signal compared and no longer suggests a match that is out of date; @> on a signal that is not an object says what @> takes; a Query news order naming a function used in select is the unknown-name 400; the subscribe and PATCH refusals on an event webhook name the event fields to check; select beside columns on a webhook PATCH says what each one does.
  • Fixed
    Query events from after to is compared on the ET day when every kind reads a bare date as the ET day (analyst, news, estimate revisions), as Query news compares it.
  • Fixed
    Every webhook object carries its health fields: last_error and last_eval_error_at are null, consecutive_failures is 0, failing_since is null and last_success_at is created_at until something happens. A new webhook left them out.
  • Fixed
    A request that cannot get a database connection within 10 seconds answers 503 unavailable with Retry-After, as the errors page says. Under load it could wait with no answer for minutes.
  • Changed
    Without limit, a select=* page on History holds 252 points (one ticker gets 252, 5 tickers get 50), not up to 1,000: five tickers of every signal was a 10 MB page. An explicit limit up to the 1,000-point cap is unchanged.
  • Fixed
    MCP tool inputs with one value from a fixed set are case-blind (dir, channel, cadence, …), as the API reads them.
v2.97.02026-11-12
  • Fixed
    Bars returns 1m, 5m, 15m and 30m bars for a symbol's earlier holder, as it does 1s, 1h and 1d. For dates when another company held the symbol (SPWR in 2022 is SunPower), these intervals answered coverage: no_data with no bars.
v2.96.02026-11-12
  • Added
    Every field that takes a fixed set of values says what each one means, in a table under the field: webhook status, disabled_reason, cadence, channel and dir; delivery event, status and channel; universe kind; the article's overall_sentiment_label; and the Query events payload fields with a fixed set, such as insider action (every SEC Form 4 code), analyst action and price_target_action, filing form and fiscal_period.
  • Added
    List event kinds gives those payload fields a values list, each value with its description.
  • Added
    Agents get the same tables: each .md page and llms-full.txt has a values table for every enum param and field; OpenAPI carries each value's meaning in the description and in x-enumDescriptions; MCP tool inputs name each value and what it means.
v2.95.02026-11-12
  • Fixed
    Bars session=regular ends at 13:00 ET on NYSE half days, such as the day after Thanksgiving and Christmas Eve. It used 16:00 ET every day, so bars from 13:00 ET on a half day, after the close, were returned as regular-session bars.
v2.94.02026-11-12
  • Fixed
    Webhooks with cadence nyse_open are checked at the 9:30 AM ET open, on NYSE trading days only. From March 1 to the second Sunday of March and from the first Sunday of November to November 30 they were checked an hour early, at 8:30 AM ET, against pre-market data; they were also checked on market holidays. The value is unchanged.
v2.93.02026-11-12
  • Fixed
    from after to is a 400 on Query events and Query news, as on History, Bars and deliveries; it returned an empty 200.
  • Changed
    A param you did not send is echoed as null in query: Query events and Query news now send the keys they left out.
  • Fixed
    /v2/status as_of is the time the response was assembled; the health check it reports is the new checked_at.
  • Changed
    The ticker sector read and an undeclared param: /v2/tickers/{ticker}/sectors and /v2/etf/{ticker}/sectors echo query and answer an undeclared param with 400 unknown_parameter, as every documented read does.
  • Added
    List signals takes interval as the older name of grain, as every other endpoint does. List event kinds gives insider a history_start.
  • Fixed
    Clearer errors: next_cursor and sort_by say to use cursor and order; History's point cap quotes the limit you sent; a condition that repeats the signal name says to drop it; Run a scan without q gives an example; Subscribe to events says why from, to, order, dir and cadence do not apply; select=* on an alert has one message on every subscribe.
  • Fixed
    MCP: an argument a tool does not take reaches the API, so its error carries a request_id; comma lists accept spaces and any case, list params accept an array, a required param accepts its older name, and error results carry _advisories.
  • Deprecated
    To 2027-01-12: on Get a signal, query.select for an unsent select changes from [] to null; on a comma-list Get a ticker, _meta.{symbol}.history_revised_at becomes the timestamp itself. See Deprecations.
v2.92.02026-11-12
  • Fixed
    A comma list where every symbol is unknown answers 200 again, with data empty and not_found naming them all, on Get a ticker, Bars, History, Coverage and Holdings. Only one symbol in the path is a 404.
  • Changed
    An unknown universe on a read answers 200 with no results and its id in not_found, on Run a scan, Get a signal, Query events and Query news (it was 404 universe_not_found). Unknown names in Query events signal are listed in not_found instead of failing the read.
  • Fixed
    Subscribes and webhook updates refuse unknown tickers, universes and devices with a 400 naming them, never a 404 (universe_not_found and device_not_found are now 400). See Errors.
  • Fixed
    Cursors compare values as the API reads them: on page 2, a list sent as an array or as a, b, dir=DESC for the default desc, ticker=aapl for AAPL, grain=1D for 1d, order=value or sort_by=default on Get a signal, and kind=custom on List universes continue the walk instead of answering 400. Text in q, condition and search is compared as written. Bars cursors are unchanged. See Pagination.
  • Fixed
    sort_by beside order on Get a signal: sort_by=market_cap&order=market_cap is accepted; any other pair, such as sort_by=default&order=default, answers 400 bad_request naming both.
  • Fixed
    Query events kind=signal paging always moves on. A page that could not read its stretch of history in time returned no results and the same next_cursor, so paging could repeat it. Each such page now tries a shorter stretch, and after three in a row the read answers 503 unavailable with Retry-After. A q or join=state read with no from now pages through history the same way instead of reading it in one pass. Rows served are unchanged.
  • Fixed
    History select=* returns every row a named list returns. On rates and FX (and on 1w, the latest week) * skipped days with no bar, and on 1h it added extended-hours rows with every signal empty. * reads the stored signals only; its vwap is the stored value.
  • Fixed
    Dates before 1900 are a 400 naming the param (any date param, any route); they returned 500. An unknown signal beside select=*, and an unknown signal in select on a Get a ticker asof read, are a 400. Bars takes 12-digit epoch milliseconds (before 2001). A timestamp with a UTC offset gets a 400 asking for Z, and a blank Bars interval= is ignored.
  • Deprecated
    To 2027-01-12: a cursor returned before 2026-11-12 answers 400 bad_request from that date. See Deprecations.
v2.91.02026-11-12
  • Fixed
    A cursor resumes only the read that returned it. Send next_cursor back with the same params as the first page (limit may change). A page whose params differ is a 400 naming the param; it used to return another read's rows. Cursors issued before this change keep working. Bars is unchanged: its cursor is a bar time, a position. See Pagination.
  • Fixed
    A date that does not exist is a 400. 2026-02-30, month 13 or T25:00 answered 500 on Get a ticker, History, Bars, Run a scan, Get a signal, Query events and Query news, and Bars read Feb 30 as Mar 2. Every date param now answers one sentence naming the param, the value and the format: "from: 2026-13-45 is not a calendar date. Use YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ."
  • Added
    select=* on Get a ticker, Get a signal and History returns every signal, as on Run a scan and Query events; on an as-of read or History, every signal the grain stores. A History select=* page holds up to 1,000 points (tickers × limit).
  • Added
    List tickers, List signals and List universes echo your request as query, as every other read does.
  • Added
    not_found on Query events and Query news. With ticker, both list the symbols you named that we do not track, as List tickers does, so a typo no longer reads as "no events".
  • Fixed
    Signal events with q or join=state over a long window no longer time out. A kind=signal read with from a month or more back reads the window in steps and returns within seconds; a page that stops early carries a next_cursor to continue. See Query events.
  • Changed
    Two names of one param in one request are a 400, with one message, for example fields with columns on Get a ticker, or sort_by with order on Get a signal: "Send one of select, fields, columns; they are the same param." Two older names together used to resolve silently. Each older name alone works as before. ticker and tickers with the same symbols are accepted everywhere, including Query events and Query news.
  • Fixed
    The docs "Try it" sandbox rejects what the API rejects: an unknown param, a value outside its list, or two names of one param answer the same 400 there as with a key.
  • Changed
    Errors say what to send instead: symbols on List tickers points to ticker, search on Query events to q, /v2/ticker/NVDA to /v2/tickers/NVDA. A list over 50 symbols and an unusable cursor each answer one message naming the fix, and an unknown_parameter 400 lists only the params of the method you called. When a query interval disagrees with the Bars path, the 400 names both widths. On custom signals, expression points to expr, updating or deleting a built-in signal says it is built-in and read-only, and compile_failed carries a message.
  • Fixed
    An Idempotency-Key reused with a different body answers 422 idempotency_key_reused instead of replaying the first response (Errors). A key sent as null counts as not sent. Only a 2xx is stored now: after a 4xx (a 409, a 429, a 400 you then corrected), a retry with the same key runs again; it replayed the error for 24 hours.
  • Fixed
    Subscribe to events and Subscribe to news check ticker: no tracked ticker is a 404, some untracked is a 400 naming them, and on Update a webhook either is a 400 naming them (a 404 there reads as "webhook not found"); such a webhook could never fire. A comma list in the Subscribe to a ticker path is a 400 that gives the Subscribe to a scan q for it. The crypto/FX 400 on Subscribe to events points at what works.
  • Fixed
    Update a webhook: sending a ticker webhook's q back as read is a no-op (it wrapped the rule in its ticker scope again); columns and fields are accepted and mean what they mean on the subscribe that made the webhook, signals added to the default row (select is exactly what each match carries); and a destination field for another channel (target_url with channel: "in_app") is a 400 here and on every subscribe, where it used to be dropped.
  • Fixed
    A webhook made with columns or fields reads select: null, with those signals under fields (Get a webhook). select listed them, but each match carries the default row as well, and sending that select back to Update a webhook cut the delivery to those signals.
  • Fixed
    Universe-scoped alerts evaluate their crypto, FX and rate members. A scan or signal webhook scoped to a universe left those members out. An alert whose universe holds such members that already match may fire once for them.
  • Added
    Webhook deliveries echo every filter of their webhook: webhook.fired adds universe, events.fired adds ticker and universe, news.fired adds min_relevance. A test fire sends a value of each signal's type (text, an ISO timestamp), not 0, and a failed one has next_attempt_at: null: it is never retried.
  • Fixed
    Stream tickers: a frame key that names another param (columns, signals, symbols, asof) or an unknown signal in select answers an error frame naming it and what to send instead; it used to be ignored or dropped.
  • Removed
    Stream tickers: the subscribe ack no longer sends dropped_signals or dropped_fields. A select naming any signal the stream does not carry is now an error frame and subscribes nothing; it used to subscribe the other signals and list the unknown ones in those keys. Remove the unknown signal from select. dropped_fields had been listed on Deprecations until 2027-01-12.
  • Fixed
    Get ETF holdings sends total on every page, and POST /v2/webhooks/{webhook}/enable has a usable Link header.
  • Fixed
    MCP: every tool's output schema declares _advisories, so a validating client accepts a result carrying a quota or deprecation warning, a blank-valued unknown argument gets the unknown_parameter 400 REST gives, and a call by a deprecated tool name carries _advisories.deprecated with its sunset date and the tool to call. Deprecations lists the MCP tools retired on 2026-11-10 with their successors.
  • Deprecated
    To 2027-01-12 (Deprecations): a param a path takes only on another method (GET /v2/universes?tickers=) becomes a 400 unknown_parameter; any other unknown stream frame key becomes an error frame; event and news webhooks stop carrying cadence, last_match_set, next_eval_at and last_evaluated_at, and no webhook carries last_predicate_value; select=ticker_data on news becomes a 400 naming mentions; on a comma list Bars count counts bars, and unknown symbols in a Bars or History list appear only in not_found; one ETF's Holdings read drops the top-level count, and Holdings drops truncated.
v2.90.02026-11-12
  • Changed
    MCP tools are named for their docs page: tickerbot_query_events (Query events) and tickerbot_query_news (Query news). The old names tickerbot_list_events and tickerbot_search_news keep working until 2027-01-12; see Deprecations. The OpenAPI operationIds follow: query_events and query_news.
v2.89.02026-11-12
  • Removed
    api_version is no longer accepted on Bars and History. It changed nothing once both kept their response shape, so it now answers 400 unknown_parameter like any name an endpoint does not take. Drop it from your requests.
v2.88.02026-11-12
  • Fixed
    select=* on Query news returns every article field plus mentions (and the mention's fields on a per-mention row). select=* on a group_by rollup is a 400, and order takes an article field or a select alias; any other name is a 400.
  • Fixed
    A cursor continues only the read that made it. On Query news, send the first page's params with every page (limit may change): a page with different params, or the cursor alone, is a 400 naming the param. On Query events, a ticker list, q or select too long for the cursor must be sent again with it, and is a 400 naming it when it is missing or different; a long ticker list used to fall away from page 3 on and return every ticker.
  • Changed
    A group_by rollup without limit returns every group up to 1,000 on Query events and Query news (it was 50). A rollup does not page, so the default is its maximum. List mode still defaults to 50.
  • Added
    Query events takes select=* in list mode: every field, the whole payload, and with join=state every signal the read's grain stores.
  • Fixed
    Every subscribe endpoint answers 400 for channel: "webhook" without target_url, as Update a webhook does; it created a dashboard-only webhook. Subscribe to a scan and Subscribe to a ticker answer 400 unknown_parameter for a name they do not take, as the other subscribe endpoints do (ticker on Subscribe to a scan says to put it in q).
  • Added
    A custom signal works in order on Run a scan, Get a signal, Subscribe to a scan, Subscribe to a signal and Update a webhook, as a built-in yes/no signal does.
  • Fixed
    Paging a scan sorted by a yes/no signal moves past the first page; page 2 repeated page 1.
  • Added
    @> matches inside an object signal: leadership @> '[{"name":"John Ternus"}]' finds the companies he leads. A value that is not JSON is a 400 naming it (it was a 500). See SQL.
  • Fixed
    A test fire has the shape of a real fire: it is built by the same code, so a sample match carries the keys a real match carries, an event webhook applies its select, and a news sample keeps id and mentions. A news webhook's test fire sends news.fired.
  • Added
    events.fired deliveries carry kind (the kinds the webhook watches) beside kinds. The Webhooks page documents every delivery body field by field.
  • Fixed
    History returns bar signals for a symbol's previous holder, as Bars does (close, open, high, low, volume, vwap, trades). A select mixing them with other signals returned no rows.
  • Fixed
    Get a ticker with asof and a pinned grain answers 400 interval_unavailable for a signal in select that grain does not store, as Run a scan and Get a signal do; it left the signal out. Without select, _meta.signals_not_stored_at_grain names the signals that grain leaves out.
  • Fixed
    A comma list where every symbol is unknown answers 404 not_found on Get a ticker, coverage, holdings and Bars, and Bars answers 404 for one unknown symbol (it answered 200 with coverage: no_data). A list with some known symbols still answers 200 and names the rest in not_found.
  • Changed
    Response key order follows one rule: History and Get a signal send query right after as_of, and Get a signal sends signal and catalog after results. List event kinds gives news history_start as 2015-01-01. Error messages say "signal" and "built-in universe".
  • Deprecated
    To 2027-01-12: History's error for a signal the grain does not store changes from bad_request to grain_unavailable; Query events echoes from and to as sent, query.kind names the six default kinds where it says all, and with join=state _meta.grain names the finest grain served (with blended) where it says auto; the scan query echo sends select and group_by as lists; a universe 400 body drops ok and reason; and List deliveries from/to take YYYY-MM-DD or a …Z timestamp only. See Deprecations.
v2.87.02026-11-12
  • Fixed
    query lists the params in their documented order on History, Query news and Query events, as on every other read. The keys and values are unchanged.
  • Changed
    /docs/schema.json uses the List signals vocabulary. One signals list (a yes/no signal is type: boolean, with boolean_kind and firing), refresh for how often each updates, and grains, keyed by stored grain, each { history, since, coverage } ({} is current value only). bars lists its grains.
  • Changed
    List signals type takes object for a JSON object; jsonb keeps working.
  • Changed
    List tickers rows carry country, currency_name and delisted_utc only. The listing_country, currency and delisted_at keys, sent since 2026-11-10, are gone.
  • Fixed
    Test fire a webhook sends a news webhook a news.fired delivery with one sample article in the shape it really receives (it sent a webhook.fired sample before).
v2.86.02026-11-12
  • Changed
    A param sent under its name and an older name at once is a 400 bad_request on every endpoint and MCP tool, for example select with fields, asof with as_of or from with since: send one. One of the two used to be dropped without a word. Each older name alone works as before (Deprecations).
v2.85.02026-11-11
  • Fixed
    Alerts no longer match delisted tickers. A scan, ticker or signal webhook checks the tickers Run a scan and Get a signal return, active ones only. It also matched delisted tickers, whose signals stopped updating the day they stopped trading, so a delivery could name one. A delisted ticker that was in a webhook's match set leaves it at the next check, which sends nothing.
  • Fixed
    A new alert fires only when a ticker starts matching, as Subscribe to a scan, Subscribe to a ticker and Subscribe to a signal say. Its first check records what already matches without firing; it used to send one delivery listing every current match. Event and news webhooks already fired only on what lands after you subscribe.
  • Changed
    An MCP tool answers an argument it does not take with the error REST gives: unknown_parameter with the parameters the endpoint accepts, and the same hints (where on tickerbot_scan says to use q). It used to leave the argument out and run the call without it. The older names REST accepts still work.
  • Fixed
    Every MCP tool's structuredContent passes its own outputSchema. A tool that still sends fields leaving on 2027-01-12 (Deprecations) has an outputSchema that allows them until then; 20 tools failed their schema before.
v2.84.02026-11-11
  • Added
    List tickers answers not_found with ticker: the symbols you named that we do not track, in request order, the same key and meaning as Get a ticker. A tracked symbol that another filter or the page leaves out is not in it.
  • Changed
    Every List signals filter takes a fixed set of values, listed with a description each on its page: group, category and asset_class join kind, type, refresh and grain. A value outside the set is a 400 that lists the valid ones; it used to return an empty list.
  • Fixed
    MCP tools take every older parameter name REST takes, for example tickers on tickerbot_list_tickers, fields and columns on tickerbot_scan, interval on tickerbot_get_history, with the same meaning as on REST. An argument a tool does not know is still left out and named in the X-Tickerbot-MCP-Dropped header.
  • Fixed
    Run a scan with group_by sends truncated on every response (false when the list is whole), and query.select is a list, as on a row scan.
  • Fixed
    A webhook made with fields or columns shows those signals in select; it showed null. Bars: the 400 for interval in the query names the ticker you sent. Query news: each mentions entry lists ticker, relevance, sentiment_score, sentiment in that order. Update a webhook: a new kind that the stored q does not fit is a 400 naming the field the new kind lacks.
  • Deprecated
    To 2027-01-12, on List signals: taxonomy, with each group's derivation. Each signal carries its group and category with their labels, and the List signals page describes every group and category.
v2.83.02026-11-11
  • Changed
    search ranks its matches on List signals, List tickers and List universes. An exact name (symbol, universe id) comes first, then names that start with the term, then names that contain it, then descriptions (a ticker's company name) that have it as a whole word, then descriptions that contain it. search=rsi now starts with rsi_14. The same rows come back, in the usual order within each rank, and paging a search never repeats or skips.
v2.82.02026-11-11
  • Added
    Get a ticker's holdings pages with cursor. next_cursor comes back beside data and inside each ETF's object, and cursor continues from the last holding (heaviest first, then by symbol). On a comma list one cursor carries each ETF's own position. total and truncated stay, now on every page that more holdings follow, so the whole of a large ETF is reachable before the per-ETF maximum drops to 1,000 on 2027-01-12.
  • Added
    query on Bars, Get a ticker, Get a ticker's coverage and Get a ticker's holdings: your request echoed with its effective values, the shape History, Query events and Query news use (ticker is always a list). The Bars comma list adds not_found, the symbols we do not track.
  • Added
    Subscribe to a signal takes order and dir, as Subscribe to a scan and Get a signal do: they sort each delivery's match lists (default market_cap, desc). Update a webhook edits them on a signal webhook.
  • Added
    New _meta names beside the old ones: signal_grains (Get a ticker), grain_scope and minute_only_signals_fell_back_to_daily (Run a scan, Get a signal) and signals_not_stored_at_grain (Run a scan). The interval_unavailable error message speaks of grain.
  • Changed
    Pagination states the time-window rule once: a bare date covers that whole day (the market day on market data, the UTC day on webhook deliveries) and a timestamp to is exclusive. Every from and to says so.
  • Changed
    The docs show the current shape only. Returns tables and the _meta reference no longer list the older keys sent beside their replacements; Deprecations lists every one. count is described the same way everywhere: the items in the response's main list.
  • Deprecated
    To 2027-01-12: a timestamp to becomes exclusive on Bars, History and List deliveries, and the error code interval_unavailable becomes grain_unavailable, with the same status and message (Deprecations).
v2.81.02026-11-11
  • Added
    List universes takes kind (builtin, custom or both as a comma list; owner keeps working) and search (id, name and description). Every universe carries kind beside system.
  • Fixed
    List universes: limit and cursor page the whole list, built-ins first. The built-ins used to come back in full on the first page whatever limit said.
  • Added
    Update a webhook edits the trigger: the filters of the subscribe that made it (q, universe, select, order, dir on a scan webhook; condition on a signal webhook; kind and ticker on an event webhook; search and min_relevance on a news webhook), checked exactly as that subscribe checks them, and the channel (channel, discord_url, device_id). A changed trigger fires only on what is new: what already matches it, or already happened, does not fire.
  • Fixed
    Update a webhook: enabled: true turns a disabled webhook back on, with the same checks as re-enable. It answered a 400 pointing elsewhere.
  • Changed
    List webhooks: status takes one or a comma list. List deliveries documents every field of a delivery and sends each on every row (redelivery_of is null and test is false unless set). Test fire answers the delivery row, with last_status_code and last_error, plus delivered and elapsed_ms.
  • Changed
    Stream tickers: the subscribe frame takes ticker (one symbol or a list; tickers keeps working) and select ("*" for every signal; fields keeps working). The ack adds dropped_signals, renamed_signals and unsupported (crypto, FX and rate symbols).
  • Fixed
    Stream tickers: a symbol we do not track comes back in not_found and takes no slot of your cap. It used to ack as subscribed, take a slot and never update.
  • Changed
    One value or a comma list on four more filters: asset_type and exchange on List tickers, kind on List signals (builtin,custom is both) and status on List deliveries.
  • Changed
    Resend a delivery answers the new delivery's row, every field List deliveries and the test fire send. The five fields it answered before are among them, unchanged.
  • Deprecated
    To 2027-01-12, page maxima follow one rule: market-wide results page at 100 rows, data for tickers you name at 1,000 points, account lists at 100, and batches stay at 50 tickers (Pagination). So the limit maximum drops to 100 on List events and Query news in list mode (from 1,000), on List signals (from 500) and on Get a signal (from 200). A larger value is clamped to the new max, as today, and next_cursor pages the rest. A group_by rollup on List events or Query news keeps up to 1,000 groups and sets truncated: true past them. List tickers and holdings were announced above.
  • Deprecated
    To 2027-01-12: POST /v2/webhooks/{webhook}/enable (send enabled: true to Update a webhook) and the MCP tool tickerbot_enable_webhook (call tickerbot_update_webhook with enabled: true); crypto, FX and rate symbols in the stream ack's invalid (read unsupported). From that date List universes without kind lists built-in and yours; send kind=custom to keep today's list.
v2.80.02026-11-11
  • Added
    Query news reads each ticker an article mentions. ticker, relevance, sentiment_score and sentiment (the fields Query events serves for kind=news) work in q, select, order and group_by, one result per article per mention: q=ticker = 'NVDA' AND sentiment_score < -0.3 is the articles negative about NVDA, group_by=ticker rolls up per ticker. tk, the older name of ticker, keeps working. Every article row carries mentions (each ticker with its relevance and sentiment) and url.
  • Changed
    Query news: ticker takes one symbol or a comma list (up to 50; tickers keeps working), and the query echo carries ticker as a list. A guessed sentiment parameter (sentiment, min_sentiment, sentiment_score_gte, …) answers a 400 naming the q that does it.
  • Added
    Subscribe to news, POST /v2/news/subscribe: a webhook on new articles matching Query news's filters (search, ticker, universe, min_relevance, q). Each article fires once, delivered as the Query news row (or your select) with its mentions, under event: "news.fired". A subscription names at least one of search, ticker, universe or q.
  • Fixed
    Query news pages whatever select leaves out. A select without the order field returned next_cursor: null on a full page; it now pages, and per-mention rows page without skipping an article's other mentions.
  • Deprecated
    To 2027-01-12, on the News family: GET and POST /v2/news/scan (use /v2/news, the same read) and the ticker_data field (read mentions).
v2.79.02026-11-11
  • Added
    Every event has a stable id, <kind>:<key>, on Query events and in every event-webhook delivery. It is built from the event's own key (an analyst action's vendor id, a filing's accession number, a dividend's ticker, ex-date, type and amount, …), so the same event has the same id on every read: use it to drop duplicates. It can be named in q and select.
  • Added
    List event kinds, GET /v2/events/kinds: every kind with its fields (the names q, select and group_by take when you ask for that kind alone), its filters, what its ts means, its id rule, and whether it is in the default stream and can be subscribed to.
  • Added
    Query events: select without group_by picks what each result carries, at the top level: id, ticker, ts and kind always, then payload, the payload fields of the one kind named, and with join=state the ticker's signals. dir=asc reads oldest first and pages forward; order=ts is accepted on a list and changes nothing.
  • Added
    kind=signal reads custom signals and a list of signals. signal takes one name or a comma list of up to 5, built-in or your own; a custom signal's flips are computed when you ask, from its yes/no value at each stored row, by the same rule as a built-in. News events carry payload.relevance (0 to 1, how much the article is about that ticker), usable in q: relevance >= 0.8.
  • Changed
    Query events speaks grain and ticker. grain names the grain (interval keeps working), ticker takes one symbol or a comma list (tickers keeps working), and symbol/symbols answer a 400 pointing to ticker. The query echo adds ticker (a list), from, to, grain and dir beside the older keys; _meta adds grain beside state_interval; signal payloads add grain beside interval. List tickers documents its filter as ticker too; tickers stays accepted.
  • Changed
    Subscribe to events takes one q over the event's fields (with one kind, its payload fields by bare name) and the ticker's signals at fire time, as Query events does with join=state; a signal wins a name clash with a payload field (price on insider, cik on filing; the event's own value is payload->>'price'), as on Query events. select picks what each delivered event carries. kind and ticker are the documented names (kinds, tickers and event_q keep working; an event_q is ANDed with q). estimate_revision can be subscribed to. The event webhook object adds kind and ticker, and its q shows the whole filter, the AND of both halves on a webhook made with the older two.
  • Added
    Subscribe to a signal is back, POST /v2/signals/{signal}/subscribe, removed on 2026-11-10. It mirrors Get a signal: condition in its grammar (none for a yes/no or custom signal), universe, select and the delivery fields.
  • Fixed
    Vendor strings in event payloads are trimmed. An analyst name came back as "Matthew Swanson ".
  • Deprecated
    To 2027-01-12, on the Events family: the firm and action params (use q: firm ILIKE 'Morgan Stanley', action = 'downgrades') and min_relevance (use q=relevance >= 0.8). Each is still accepted until then. See Deprecations.
v2.78.02026-11-10
  • Changed
    One rule names the payload key of every response. Market rows you filter or search come back as results: Run a scan (grouped too), List tickers, Get a signal, Query events and Query news. A list of things is named for them, keyed by symbol when the path names several tickers: bars, series (keyed by symbol always), signals, kinds, universes, webhooks, deliveries. One ticker's or ETF's record is data: Get a ticker, coverage and holdings. One object fetched by id comes back at the top level.
  • Added
    Holdings and coverage answer data (their top-level fields are sent beside it), and both take a comma list of up to 50 with query, count and not_found, as Get a ticker does.
  • Fixed
    Paging several tickers on History never skips or repeats a row. next_cursor is one opaque token carrying each ticker's own position; pass it back as cursor. History's one shared position could skip a crypto bar between pages when stocks and crypto were paged together. Bars keeps its next_cursor (the oldest bar's time, a map of those per symbol on a list) until 2027-01-12, when a list's becomes one opaque token; Bars' cursor takes either form.
  • Fixed
    History names the symbols it does not track. A comma list carries not_found, and a read where no symbol is tracked is a 404; an untracked symbol used to come back as an empty array, the same as a ticker with no rows in the window. History also echoes the request as query.
  • Added
    List tickers filters by ticker and active. ticker (one symbol or a comma list of up to 50) returns just those identity records, and active=true|false keeps trading or delisted tickers.
  • Changed
    select, grain and as_of across the Tickers family. Get a ticker takes select to return just the signals you name (the full row stays the default) and grain for an as-of read; History takes select and grain for columns and interval, which keep working; as_of is accepted wherever asof is. Subscribe to a ticker takes select as the scan door does. Bars answers interval sent as a query param with a 400: the bar width goes in the path (/v2/tickers/AAPL/bars/1d). Bars documents to to end at a time; before keeps working. The coverage data object uses the new names: spans 1d/1h/1m (the minute-tier roster moves into spans["1m"]), measured_signals with signal and grain, and live_row.signals/null_signals.
  • Deprecated
    To 2027-01-12, on the Tickers family: on History, _meta.sources and the transitions_only param (use GET /v2/events?kind=signal); on Bars, a comma list's next_cursor becomes one opaque string at the cut-off (the per-symbol map goes); the limit maximum drops to 100 on List tickers (from 1,000) and to 1,000 on holdings (from 5,000; a larger value is clamped, as today); the top-level fields of the holdings read; order/dir on Subscribe to a ticker (they do nothing with one ticker). Each is still sent or accepted until then. See Deprecations.
v2.77.02026-11-10
  • Added
    select on POST /v2/scan is the one projection param, as in SQL. Omitted, each result carries the default row plus every signal you used in q and order (a custom signal as its own value). A list returns exactly those items, ticker always included, and takes expressions with AS (price / sma_50 AS dist). * returns every signal. A select of aggregates alone (count(*), avg(rsi_14)) returns one summary row with no group_by; with group_by, each item must be an aggregate or a group key, and a 400 names the one that is neither. columns, fields and full keep working as before; the docs now show select only.
  • Added
    Each grouped-scan row always carries its group keys (a custom select used to drop them). count is the rows in the page; for a total, scan with select=count(*).
  • Changed
    grain names the grain of an as-of scan; interval keeps working. interval now means bar width, on bars only. as_of is accepted as a spelling of asof. As-of _meta adds grain, grain_requested, grain_reason, grains_present, frozen_signals and deprecated_signals beside the older keys, and null_coverage adds signals beside columns, on every read that sends them. The query echo lists the params in their documented order with each one's effective value. GET /v2/scan stays a permanent alias of POST.
  • Added
    A likely-but-wrong parameter name says what to use. On a scan, where, query, filter and filters point to q, order_by to order, next_cursor to cursor, tickers to q: ticker IN (…), and signals or columns=all to select=*. A cursor on a grouped scan says cursors apply to row scans.
  • Changed
    Alerts deliver what a scan returns. Each delivered match carries the scan default row plus the signals the rule uses, or exactly the alert's select, on POST /v2/scan/subscribe. The webhook object adds select and universe beside fields and universe_id, and order/dir show the sort in effect (market_cap/desc unless you chose one) instead of null. A subscribe door answers asof, grain, group_by, having, limit and cursor with a 400 that says an alert is live and per ticker, and channel: "slack" with a 400 saying Slack delivery was retired (it was a 501).
  • Added
    List signals filters, searches and pages the whole catalog. group, category, type, grain (stored history at that grain), asset_class and refresh each take one value or a comma list and combine with AND; search matches the name and description; select picks the fields of each row. limit and cursor now page the whole list (your custom signals, then the built-ins A→Z) rather than only your custom signals; a call with no limit still returns everything.
  • Added
    Catalog rows add grains, asof_support, boolean_kind and refresh beside the fields they replace. grains is keyed by stored grain, each { history, since, coverage } ({} means current value only). refresh says how often a signal updates in plain keys (1m_4am_8pm_et, 15m, 1h, daily_after_close, …). Custom signals carry type: boolean: they are always yes/no. The same row is catalog on Get a signal.
  • Added
    Get a signal takes select, order, dir and grain, and echoes query. select adds signals beside value on each match. Without order, a yes/no signal lists tickers A→Z and any other signal sorts by its value in the direction the condition implies (< ascending, > descending; it was always descending). sort_by keeps working (market_cap is order=market_cap&dir=desc), interval keeps working as grain, and _meta adds null_coverage as on scan.
  • Changed
    Creating or updating a custom signal returns the row at the top level, as webhooks and universes do. The update and delete paths are documented as /v2/signals/{signal}; the URL is unchanged.
  • Deprecated
    To 2027-01-12, on the signals family: include_active_since and the active_since/days_live fields (use GET /v2/events?kind=signal&signal=X&transition=enter); the catalog's source; type jsonb (becomes object); and a List signals call with no limit returning everything (after the cut-off it pages at a default limit).
  • Deprecated
    To 2027-01-12: the webhook object's rule_id, which is always null. It is still sent until then. See Deprecations.
v2.76.02026-11-10
  • Changed
    Everything that needs a ticker now lives under it. History is GET /v2/tickers/{ticker}/history (up to 50 tickers as a comma list in the path, on one aligned grid), bars are GET /v2/tickers/{ticker}/bars/{interval} and an ETF's holdings are GET /v2/tickers/{ticker}/holdings. The older spellings /v2/series, /v2/bars/{ticker}/{interval} and /v2/etf/{ticker}/holdings keep working, permanently, with the same responses; they now carry a Link header naming the new path. The MCP tool tickerbot_get_series is now tickerbot_get_history; calling the old name returns an error that names the new one.
  • Added
    GET /v2/tickers/{ticker}/holdings carries the ETF's sector mix too, as sectors[]. GET /v2/tickers/{ticker}/sectors and /v2/etf/{ticker}/sectors keep serving the sector mix alone, and the MCP tool tickerbot_get_etf_sectors is folded into tickerbot_get_etf_holdings.
  • Added
    GET /v2/signals/{signal} says what the signal is. Every response carries catalog, the same object GET /v2/signals lists for it. A non-yes/no signal read without condition now answers 200 with the catalog entry and a note on adding a bound, where it used to answer 400.
  • Changed
    Query events lists every kind under its kind param, with its own filters and a link to its payload: earnings, filings, dividends, splits, insider transactions, analyst actions, news, estimate revisions and signal firings. GET /v2/events itself is unchanged.
  • Deprecated
    Creating a webhook with POST /v2/webhooks is deprecated, with a cut-off of 2027-01-12. Create alerts with POST /v2/scan/subscribe, POST /v2/tickers/{ticker}/subscribe or POST /v2/events/subscribe: the same webhook object, with the fields of trigger at the top of the body. Listing, updating and deleting stay on /v2/webhooks. GET /v2/analyst/events moves to the same cut-off. See Deprecations.
  • Removed
    Six old routes answer 410 naming their replacement: GET /v2/tickers/{ticker}/history/{interval}, GET /v2/signals/{signal}/{ticker}/history/{interval}, GET /v2/tickers/{ticker}/events, GET /v2/signals/{signal}/{ticker}/events, POST /v2/signals/{signal}/subscribe (a signal alert is POST /v2/scan/subscribe with q set to the signal) and POST /v2/scan/explain. GET /v2/tickers/{ticker}/history?asof= was a second spelling of GET /v2/tickers/{ticker}?asof=; that path is now the history read.
v2.75.12026-11-07
  • Changed
    at_52w_high, at_52w_low, at_20d_high and at_20d_low definitions now name their window: the 52-week or 20-day high/low as of the previous session's close. That is high_52w_eod (and the other three) during the session, and the previous row's high_52w in daily history. After the evening update the _eod columns include the day just closed, so price >= high_52w_eod read outside the session no longer matches the flag; the flags themselves are unchanged.
  • Changed
    premarket_change_pct and premarket_price are defined: the latest pre-market trade (04:00-09:30 ET), and its percent change from the previous regular-session close. Null before the session's first pre-market trade. Live and history follow the same rule.
v2.75.02026-11-07
  • Added
    The latest split on the ticker row: last_split_date and last_split_ratio. The ratio is split_to / split_from, so 4 is a 4-for-1 and 0.125 a 1-for-8 reverse split. AAPL reads 2020-08-31 and 4, NVDA 2024-06-10 and 10. They match the latest /v2/events?kind=split row. Null when no split is on record.
  • Added
    Insider trading on the ticker row: the latest open-market trade and 90-day totals. last_insider_trade_date, last_insider_trade_action (buy or sell) and last_insider_trade_value (USD) describe the most recent day with an open-market purchase or sale (Form 4 code P or S; grants, option exercises and tax withholding do not count); a day with both counts as the side with the larger value. insider_buy_value_90d, insider_sell_value_90d, insider_net_value_90d (USD) and insider_buyers_90d (distinct insiders buying) cover trades dated in the last 90 days. AAPL reads a sale of $823,720.64 on 2026-10-27 and net selling of $18.7M over 90 days. Null for a stock with no coded insider filings, as for the insider flags. Try insider_buyers_90d >= 2 AND insider_net_value_90d > 0.
  • Added
    All nine are in daily history from 2003-09-10, so they work in as-of scans and /v2/series.
v2.74.22026-11-06
  • Fixed
    The webhook docs and dashboard say what realtime does. It is checked each time the data refreshes: about once a minute from 4 AM to 8 PM ET for stocks and ETFs, every minute around the clock for crypto and FX, and as each event lands for event webhooks; it fires when a ticker starts matching. The form had said it "fires the moment your query matches". hourly is checked once an hour and nyse_open once a day at the 9:30 AM ET open. The values are unchanged.
  • Fixed
    Code examples with a quoted string paste into a shell. On the example queries page and in the Try it panel, a q such as sector = 'Technology' printed a curl whose quotes ended the shell string; the quote is now escaped, as on every other example.
v2.74.12026-11-06
  • Fixed
    /v2/events?join=state pinned to interval=1m answers in seconds. One ticker over ten days took longer than the 30-second limit and returned 503; hourly reads under auto took close to 30 seconds. Results are unchanged.
v2.74.02026-11-06
  • Added
    Every bar from GET /v2/bars carries vw and n. vw is the bar's volume-weighted average price and n its trade count, on every interval from 1s to 1mo. A rolled-up bar (5m to 30m, 2h, 4h, 1w, 1mo) sums the trade counts of the bars inside it and weights their average prices by volume; with adjusted=false, vw is un-adjusted like the other prices. Both are null where the trades behind a bar were not recorded. /v2/series already served the same figures as vwap and trades.
v2.73.02026-11-06
  • Changed
    dividend_yield is null for companies that pay no dividend. It read 0 for them, live and in history, including companies that stopped paying. A yield of 0 claimed a dividend of nothing; null says there is none. A screen on dividend_yield = 0 no longer matches non-payers: use dividend_yield IS NULL. Screens like dividend_yield > 0.03 and the high_dividend_yield flag return the same tickers as before.
  • Fixed
    ipo_in_7d fires for IPOs expected in the next 7 days. The IPO calendar it read listed pending IPOs without a date, so the flag was never true. It now reads an IPO calendar that carries each expected listing date, and ipo_date holds that date for upcoming IPOs.
v2.72.22026-11-06
  • Fixed
    /v2/series refuses ticker and tickers with different values. ?ticker=NVDA&tickers=AMD used to return NVDA alone and drop AMD without saying so; it now returns 400 naming both. Send every symbol in tickers. The same value in both is still accepted.
v2.72.12026-11-06
  • Changed
    A live-only column on an as-of scan says so. Minute and premarket columns (min_low, above_premarket_high and the like) have no history, so POST /v2/scan with asof can't read them. The 400 used to call them unknown and guess a neighbour (above_premarket_high → "Did you mean above_yesterday_high?", a different signal); it now reads min_low is live only, with no history, so it can't be used with asof. Remove it, or drop asof to read today's values. A name asked for in more than one place (q, fields, order) is listed once.
  • Changed
    "Did you mean" suggests fewer wrong names. A suggestion no longer swaps a name for its opposite (52_week_high → 52_week_low), no longer guesses short names by spelling (gap → vwap; it now offers gap_up / gap_pct), and a word match must share the most specific word of what you typed. Same 400 invalid_query envelope.
  • Changed
    An unfinished comparison is named. q=rsi_14 > used to return the raw database text syntax error at or near ")", pointing at a parenthesis the API adds; it now reads rsi_14 > needs a value to compare to, for example rsi_14 > 10. Other syntax errors read q is not a valid where clause near ….
v2.72.02026-11-06
  • Added
    instrument_scope on every signal in GET /v2/signals and /docs/schema.json. company means the signal has values on operating companies and is null on ETFs and funds (fundamentals, sector, analyst targets, insider fields); fund means ETFs only (the etf_* fund facts); all means both. Use it to pick the columns that apply before screening a list of ETFs or a list of companies.
v2.71.52026-11-06
  • Fixed
    approaching_52w_high and approaching_52w_low mean the same thing in history as they do live. Live, a ticker is approaching its 52-week high when its price is within 5% of the high as of the previous close and not at it, it is trending up (above its 20-day and 50-day averages, or up on 3 of the last 5 days), and its volume is above the 10-day average. Daily history used the 5% band alone against a window that included the day itself, so it flagged days the live row never would (on 2026-11-05, over 100 tickers on below-average volume). Daily history is recomputed with the live rule; if you backtested on these flags, re-run it.
v2.71.42026-11-06
  • Fixed
    profitable, value_stock and high_margin follow the figures they are defined on. They were set before the night's last update to net income, P/E and profit margin, so on companies that report once a year (most foreign listings) they described the earlier figures: TSM, ASML and NVS read profitable false with net income in the tens of billions. They now follow net_income_loss, pe_ratio and profit_margin_ttm live, and daily history is corrected where the stored flag contradicted the same day's figures.
  • Fixed
    earnings_published and earnings_approaching follow days_to_earnings. They were computed from the previous day's count, so a company that had just reported read published with 90 days to its next report, and one three days out read neither. Daily history is corrected where they disagreed with the stored days_to_earnings.
  • Fixed
    Price-target history matches the consensus target. From 2025-03-31, daily analyst_target_upside_pct, above_price_target and below_price_target were built from single analysts' targets rather than the stored analyst_consensus_target_price: TSLA on 2025-06-02 read 45.9% upside at a price above its consensus target. They are now recomputed from each day's price and consensus target.
  • Fixed
    A scan that divides by zero returns a 400 that says how to fix it. A q such as (session_open - previous_close) / previous_close >= 0.03 returned a 500 when any row in scope held 0 in the divisor. It now returns invalid_query naming the fix: wrap the divisor in NULLIF(previous_close, 0).
  • Fixed
    pending_ipo is false on stocks that trade. The IPO calendar keeps old entries for names that listed long ago, so 21 trading stocks read pending_ipo true. A symbol with a daily bar is no longer pending, live and in daily history.
v2.71.32026-11-06
  • Fixed
    asset_classes in GET /v2/signals lists crypto, FX and rates wherever a signal has values for them. 149 signals, the indicators, flags and price fields among them, had said stocks only although crypto, FX and rate rows carry them (rsi_14, golden_cross and sma_50 on all three). A signal whose only value on a class is a placeholder, such as zero volume averages on rate rows, is not listed for it.
  • Fixed
    change_1w_pct, change_1m_pct, change_3m_pct, change_6m_pct, change_1y_pct and change_ytd_pct report a post-close cadence. They are computed after each close and hold through the next session; GET /v2/signals had listed them as updating every minute. The from_* distance fields do update every minute.
  • Fixed
    Twelve flag definitions state the rule they use. at_52w_high reads price >= high_52w_eod (the 52-week high as of the previous close), in_uptrend reads price > sma_50 AND sma_50 > sma_200, macd_above_signal reads macd_line > macd_signal, and likewise for the 20-day, Bollinger and earnings-week flags.
v2.71.22026-11-06
v2.71.12026-11-06
v2.71.02026-11-06
  • Added
    history_by_interval on every signal in GET /v2/signals and /docs/schema.json. A signal can be stored at several intervals with different depth: above_sma_50 is stored daily and hourly from 2003-11-18 and every minute from 2003-09-10 for the most liquid names. history_by_interval gives history, history_since and ticker_scope for each stored interval, keyed like resolutions ({} for a current-only column). history and history_since keep their meaning, the daily figures. The asof field on each signal describes a read with a date asof; resolutions lists the intervals a read with a timestamp asof can use.
  • Fixed
    Signals stored only hourly and every minute list their intervals. in_opening_range, above_opening_range and below_opening_range returned resolutions: [] and no history in GET /v2/signals; they now list ["1m", "1h"], and history and history_since give their hourly figures. In /docs/schema.json, signals of the flags block now carry history, history_since and history_by_interval like fields.
v2.70.42026-11-06
  • Fixed
    An as-of scan accepts the same functions a live scan does. round(), sqrt(), extract(), current_date and now() in q returned 400 "Unknown column" when asof was set. They now run, and now() and current_date mean the asof moment (a bare date is that day's 4 PM ET close), so last_earnings_date >= now() - interval '7 days' with asof: "2026-10-01" returns the companies that reported in the week before October 1.
v2.70.32026-11-06
  • Fixed
    expires_at on webhook deliveries is epoch seconds. GET /v2/webhooks/{id}/deliveries served it as an object ({"_seconds": 1799665276, "_nanoseconds": 0}) while every other time on the row is epoch seconds; it now reads 1799665276, the moment the row leaves the 90-day delivery history.
v2.70.22026-11-06
  • Fixed
    Bank cash_on_hand is the SEC cash total: cash and due from banks plus interest-bearing deposits at other banks and the Fed. It held only cash and due from banks, a small part of a bank's cash (JPM as of 2026-09-30 reads $309.8 billion; it read $24.7 billion). Daily history is rewritten from 2009, each value taking effect on its SEC filing date. cash_ratio is now null for banks, which report no current liabilities. If you stored bank cash history, re-pull it.
v2.70.12026-11-06
  • Fixed
    Warrants and rights no longer show an EPS. They carried the issuing company's diluted_eps_ttm beside their own price, which made it read hundreds of times that price (CDROW -428.55 at $0.07) and is not earnings per warrant. diluted_eps_ttm and dividend_payout_ratio are now empty on every warrant and right, live and in daily history, as market_cap already is.
v2.70.02026-11-05
  • Changed
    Signal events are the flips of the stored state, so they match /v2/series. /v2/events?kind=signal returns the moments a signal changed between two consecutive stored rows at one grain, the same rows as /v2/series?transitions_only=true at that interval. It returned every span edge from five generations of the firing log, overlapping, so a daily signal such as above_sma_200 showed open/close flips on most trading days, rows with no price from older definitions, and on AAPL an exit on 2026-09-29 with nothing after it while the stock stayed above its 200-day average. AAPL now shows one exit on 2026-03-30 and one enter on 2026-03-31 since March, as /v2/series does. Re-read any signal history you stored from this endpoint.
  • Added
    interval on kind=signal picks the grain: 1m, 1h or 1d. The default is the coarsest grain the signal is stored at (above_sma_200 and golden_cross read daily flips, consolidating_15m minute flips); a grain the signal is not stored at is a 400 interval_unavailable naming its grains. Every flip carries interval in its payload. Daily flips are stamped at the session close of their date (16:00 ET; 23:59 UTC for crypto, FX and rates). A few live detectors with no stored state (vwap_cross_up, volume_burst_3x, …) keep their minute-exact log, reported as 1m.
  • Changed
    A bare date on signal events and signal spans is the home-market day. On /v2/events?kind=signal, a YYYY-MM-DD in from or to is the ET day for stocks and ETFs and the UTC day for crypto, FX and rates, row by row when no ticker is named; on /v2/signals/{signal}/{ticker}/events it is the ET day. It meant the UTC day, so in winter the 19:00-20:00 ET hour landed on the next date. Summer dates return the same rows as before.
  • Fixed
    kind=signal&ticker=AAPL&from=2026-10-30&to=2026-10-30&limit=500 answers in under a second. It ran past the 30-second limit. A read without from now walks back in windows and may return a short page with a next_cursor; keep paging.
v2.69.202026-11-05
  • Fixed
    relative_volume uses one baseline live and on past dates: today's volume over the mean daily volume of the 10 sessions before today. Live divided by a 10-day average that included today's volume so far, and daily history by a 30-day average, so a live scan and an as-of scan disagreed (AAPL on 2026-10-30 read 1.75 in history; it now reads 1.64). Intraday, today's volume is the volume so far. Daily history was rewritten on 2026-11-04.
v2.69.192026-11-05
  • Fixed
    52-week highs and lows use the same window live and as-of: the 365 calendar days ending on the session. Daily history took the last 252 trading days, so a scan as of a past date could count a bar from 366 or more days back (AAPL as of 2026-09-10 read low_52w 225.95 from 2025-09-10; it now reads 226.65 from 2025-09-11), and a stock that trades on few days could reach back more than a year. The live row ran one day wider. A stock listed less than a year ago still uses every bar since it listed. high_52w, low_52w, their dates, days_since_52w_high/low, from_52w_high_pct, from_52w_low_pct, position_in_52w_range_pct and the at_52w_* / approaching_52w_* booleans are rewritten across daily history (3.4 million days). position_in_52w_range_pct is 50 when the high equals the low; history had it null.
v2.69.182026-11-05
  • Fixed
    bollinger_width as of a past date is a fraction of the middle band, as it is live. History held the band span in price units (bollinger_upper - bollinger_lower), so AAPL as of 2026-10-30 read 17.605 while live read 0.0507, and an as-of scan such as bollinger_width < 0.06 never matched. Every date now holds (bollinger_upper - bollinger_lower) / bollinger_middle, the documented formula. If you stored or thresholded historical bollinger_width, re-pull it.
v2.69.172026-11-05
  • Fixed
    Trailing EPS in daily history is back, on a correct share count. v2.69.8 emptied 708,638 history days whose diluted_eps_ttm read over 20 times the share price. Most of them were not reverse splits: history divided trailing net income by the share count copied from the quarterly statement, and many fourth-quarter statements carry a negative or tiny figure (Coca-Cola's 2011 Q4 read -6 million shares, so KO read -1,439 on 2012-02-21). Days before 2026-06-29 now divide by the statement's diluted share count only where it agrees with market cap over price, and by market cap over price otherwise, which puts every day on today's split basis; a day needs four quarters of net income. KO on 2012-02-21 reads 2.82 and JPM on 2015-02-19 reads 5.93. Days that sat on a share count from before a later split are corrected too (SBUX in 2012 read 1.67, now 0.85). revenue_per_share_ttm and dividend_payout_ratio are recomputed with it. Current values are unchanged: a reported EPS over 20 times the price is still not served.
v2.69.162026-11-04
  • Added
    fiscal_year_end_month on the ticker row (GET /v2/tickers/{ticker}): the month the company's fiscal year ends, 1 to 12, from its SEC filings. AAPL reads 9, MSFT 6, WMT 1. Unlike fy_period_end, it is present before a company's first annual report and follows a change of fiscal year end. A 52/53-week year that ends in the first days of a month counts as the month before (TGT, year ending 2026-01-31 or 02-01, reads 1). Refreshed nightly for new filers and in full every Saturday.
v2.69.152026-11-03
  • Fixed
    /v2/events with a crypto, FX or rate symbol and an equities-only kind answers 400 naming the asset class. ticker=X:BTCUSD returned an empty 200 for dividends, splits and the other corporate kinds, which read as "nothing happened"; it now says the symbol is crypto or FX and points to kind=signal, as /v2/news already did. Event webhooks on those kinds refuse the same symbols at create.
  • Fixed
    kind=signal serves crypto and FX symbols in tickers too, and a single-ticker read is fast whatever the ticker. tickers=X:BTCUSD&kind=signal returned 400, and ticker=X:BTCUSD&kind=signal without a date range could run past the 30-second limit.
v2.69.142026-11-03
  • Fixed
    A query that runs past the 30-second limit answers 503 unavailable with Retry-After on every endpoint. Several routes, among them /v2/events?kind=signal with a large limit, answered 500 internal instead, and some put the raw database code in error. A 500 now means a fault on our side; a 503 means retry the same request.
v2.69.132026-11-03
  • Fixed
    /v2/news with from and to on the same date returns that day. A bare to was read as the start of that day, so from=2026-11-02&to=2026-11-02 returned nothing and every bare to left out the date it named. It now runs through the end of the day.
  • Changed
    A bare date on news, analyst and estimate-revision events is the ET calendar day. On /v2/news and on /v2/events with kind=news, analyst or estimate_revision, a YYYY-MM-DD in from or to now means 00:00 to 24:00 ET. It meant the UTC day, so items published from 20:00 ET (19:00 ET in winter) to midnight landed on the next date; they now land on the date they were published in New York, all year. Timestamps are unchanged, and dated kinds (dividends, splits, earnings, insider) already used market dates.
  • Fixed
    /v2/series requests that mix stocks with crypto or FX use each ticker's own day. With a bare date at 1m or 1h, a stock in the same request as X:BTCUSD now gets its ET day (through the 19:59 ET bar) and the crypto symbol its UTC day, as a stock alone has since v2.69.11.
v2.69.122026-11-03
  • Added
    Computed signals carry their formula. GET /v2/signals returns definition on 49 computed numeric signals (moving averages, RSI, MACD, ATR, Bollinger bands, stochastics, ADX/DI, distances from moving averages, multi-period changes, average volumes, gap, short-term highs and lows), as it already did for booleans. Each signal's docs page shows it in its Facts table, along with the asset classes it covers.
v2.69.112026-11-03
  • Fixed
    A bare date on an intraday read covers that whole trading day. On /v2/bars (1s through 4h) and /v2/series (1m, 1h), a YYYY-MM-DD in from, to or asof for a stock or ETF now means the ET calendar day. It meant the UTC day, which matched the 04:00-20:00 ET session only while daylight saving was on: since 2026-11-01, from=2026-11-02&to=2026-11-02 stopped at the 18:59 ET bar, and a read of 2026-11-03 started with the 19:00 ET hour of 11-02. Reads of summer dates return the same bars as before. Crypto and FX keep the UTC day, as do 1d and longer intervals.
v2.69.102026-11-03
  • Fixed
    Intraday bars hold final prices. Minute bars from 2026-10-07 (and 5m/15m/30m built from them) and hourly bars from 2026-07-13 (and 2h/4h) held the preliminary same-day version of each bar, which rounds prices and includes minutes whose only trades were odd lots. They now hold the final bars, and the same repair covers earlier minute bars back to 2026-06-16 for less-traded symbols fetched on request. Each morning the previous session's minute and hourly bars are replaced with the final version, so bars for a session can change once overnight, and occasionally again up to three trading days later. If you stored intraday bars from these dates, re-pull them.
v2.69.92026-10-31
  • Fixed
    Annual and quarterly statements on interval=1y and interval=1q show figures as first reported. A fiscal year that a later 10-K restated carried the restated figures under its original reported date, so a read as of that date saw numbers that were not yet public: MSFT fiscal 2016 read net_income 20,539M dated 2016-07-28, while the 10-K filed that day said 16,798M (the 20,539M came from its 2018 restatement). Each year now carries its original report's figures, from SEC filings. A line the original report did not state on the same basis is null for that year rather than restated (most often ebitda). Quarterly rows follow the same rule (MSFT fiscal 2017 Q1 operating_income 6,715M restated, 5,225M as filed); a fiscal fourth quarter is the annual report's year minus the first three quarters as first reported, and ratios built on a restated quarter are null. The daily revenue_fy, net_income_fy and eps_diluted_fy history follows the annual figures. If you backtested on annual fundamentals, re-run it.
v2.69.82026-10-27
  • Fixed
    Foreign companies' fundamentals are in US dollars or empty, never in their home currency. Some foreign filers carried their home-currency revenue as if it were dollars (SK hynix revenue_ttm read 189 trillion, its won revenue; Telkom Indonesia 147 trillion rupiah; VinFast 67 trillion dong). Foreign common stock that reports to the SEC in another currency (Royal Bank of Canada, Canadian National, Enbridge and others) now takes its company totals from its annual SEC filings, converted at the Federal Reserve's New York noon rates as the listed ADRs have since v2.56.6, and diluted_eps_ttm is that filing's diluted EPS per share, converted the same way (CNI 5.42). reporting_currency names the original currency and fundamentals_basis reads annual on these rows. Where the Federal Reserve publishes no rate for the currency (Argentine peso, Chilean peso, Colombian peso, rupiah, tenge, dong and others), or a listed ADR files no financial figures with the SEC (SK hynix, Grupo Cibest, ICICI Bank), the company totals and the ratios built on them are empty rather than wrong. Daily history is included.
  • Fixed
    diluted_eps_ttm is empty where it was impossibly large. On 217 small stocks the trailing EPS ran across reverse splits the vendor never adjusted, so it read many times the share price (WOK -51,993 at $1.16, DCX 405,249 at $1.16). Those values are no longer served, and dividend_payout_ratio, which divides by them, is empty with them. Daily history had the same defect on 2,921 stocks from 2010 on (KO read 1.57 million in some years); those 708,638 days are empty too.
v2.69.72026-10-27
  • Changed
    consolidating_15m compares the last 15 minutes with the 30-minute ATR. It is true when the high-low range of the last 15 minute bars is under 2.5 times the average true range of the last 30. It used to require a range under 1/30 of the spread of the last 30 closes, which almost never happens on a traded stock: it was false on every minute of AAPL, MSFT, SPY, JPM, XOM and INTC checked, and fired mostly on illiquid symbols with flat bars. Minute history back to 2003 and its events on /v2/events?kind=signal were recomputed. If you used this flag, re-run it.
v2.69.62026-10-26
  • Added
    interval=1q on /v2/series serves the full financial statements. The income statement, balance sheet and cash flow columns of interval=1y are now quarterly columns too, under the same names and definitions: net_income, operating_income, ebitda, total_assets, total_equity, operating_cash_flow, capital_expenditures and 32 more. Income and cash flow columns cover the quarter, balance sheet columns are at quarter end, and free_cash_flow is operating cash flow minus capital expenditures, as at 1y. Per-share columns stay annual; quarterly EPS is eps. MSFT's four fiscal 2026 quarters add up to its annual revenue (331,839M) and net_income (133,749M).
v2.69.52026-10-26
v2.69.42026-10-26
  • Fixed
    Older hourly and minute history reads its percent fields in percent-points, stamped at the end of each bar. Rows written before mid-July 2026 held eleven percent fields 100 times too large: change_1d_pct, gap_pct, from_open_pct, from_vwap_pct, from_52w_high_pct, from_52w_low_pct and from_sma_10/20/50/100/200_pct (AAPL at 2024-06-12 18:00Z read change_1d_pct 499.16; it now reads 4.99). The same rows were stamped at the start of their bar, so a read as of an instant could see up to one bar ahead; each now sits at the end of its bar, so an as-of read only sees prices printed by then. History from 2003 is corrected on /v2/series, /v2/scan and GET /v2/tickers/{ticker}?asof=. If you backtested on intraday history, re-run it.
v2.69.32026-10-26
  • Fixed
    Missing quarters are back on GET /v2/series?interval=1q. Quarters the vendor did not serve on the day a stock's history was first loaded never came back: COST had no rows for the quarters ended 2024-05-12 and 2025-02-16 and no revenue on 2024-09-01. 8,943 quarters were reloaded from the vendor, and 1,299 the vendor does not have were filled from the companies' SEC filings (ILMN's quarters ended 2017-04-02, 2017-07-02 and 2017-10-01: revenue 598M, 662M and 714M), each dated by the filing that first reported it.
  • Fixed
    Quarters that held a full year of income now hold the quarter. For 69 stocks, a fiscal year's last quarter carried the whole year's revenue and income: ILMN's quarter ended 2017-12-31 read revenue 3,371M and now reads 778M, and CAKE's ended 2024-12-31 read 4,459M and now reads 921M. Figures come from the companies' SEC filings; where none was filed, the quarter is empty.
  • Changed
    Daily revenue_ttm is null on days when no four consecutive filed quarters are on record. It used to add up the four newest quarters on record even when one was missing, so it summed five quarters and read too high: C on 2021-05-10, with no quarter ended 2020-12-31 on record, now reads null. The same holds for gross_profit_ttm, profit_margin_ttm, operating_margin_ttm, return_on_equity_ttm and return_on_assets_ttm; revenue_growth_yoy_pct, revenue_growth_yoy_quarterly_pct and earnings_growth_yoy_pct are null when the year-ago quarter is missing. Daily history before 2026-06-29 was recomputed on the repaired quarters above. If you stored these columns before 2026-10-19, read them again.
v2.69.22026-10-26
  • Fixed
    Opening-range flags on hourly and minute rows follow the opening range. in_opening_range, above_opening_range and below_opening_range compare a row's price with the high and low of the 09:30-09:44 ET minute bars. On interval=1h they were wrong or empty on rows back to 2025, because the range came from the vendor's provisional bars or the rows had been moved by an hour: AAPL at 2026-08-20T15:00Z read below_opening_range at 317.14 against a range of 316.67-320.28, and now reads in_opening_range. On interval=1m the rows written live from 2026-10-06 were wrong or empty on up to half of a day's minutes. Hourly history and minute history from 2026-10-06 were recomputed from the vendor's final bars, and each session is now recomputed the next morning.
  • Fixed
    Intraday signal events match the minute series. For in_opening_range, above_opening_range, below_opening_range, consolidating_15m, range_break_15m_up, range_break_15m_down, repeated_test_of_high, repeated_test_of_low, pre_close_drift_up and pre_close_drift_down, the events on /v2/events?kind=signal and /v2/signals/{signal}/{ticker}/events were a log written live and disagreed with the same flag on interval=1m on about a third of minutes; some spans stayed open for weeks (MSFT repeated_test_of_high from early October). An event is now each run of minutes where the flag is true on the minute series, starting and ending on whole minutes and never crossing a session. History was rebuilt for the stocks and days that already had these events, and each session is rebuilt the next morning. If you stored these events, read them again.
v2.69.12026-10-26
v2.69.02026-10-26
  • Changed
    Webhook deliveries retry for about a day, and a webhook is disabled only after 72 hours with no successful delivery. Each delivery now retries 7 times over about 22 hours (30s, 2m, 10m, 1h, 3h, 6h, 12h). A webhook used to be disabled after 5 deliveries in a row ran out of retries; it now stays active until nothing has reached your endpoint for 72 hours, and we email you the first time a delivery fails for good, before that happens. consecutive_failures still counts but no longer disables. Additive: no field is removed or renamed.
  • Added
    POST /v2/webhooks/{id}/deliveries/{delivery_id}/redeliver resends a past delivery with its original body, to the webhook's current target. The resend carries the original delivery id in X-Tickerbot-Delivery-Id, so a receiver that dedupes on that header recognizes it. New on the webhook: last_success_at (when a delivery last reached your endpoint) and failing_since (when the current failure streak began; null while deliveries succeed).
v2.68.32026-10-26
  • Fixed
    GET /v2/news rollups whose select names volume sort by volume again. v2.68.1 made a custom select sort by its last column, which also moved calls like select=tk, COUNT(*) AS volume, AVG(overall_sentiment_score) AS s off volume. A select that names volume sorts by it, as before v2.68.1; one that does not sorts by its last column.
v2.68.22026-10-26
  • Fixed
    The news signal docs describe what is computed. news_volume was described as a count of the last 24 hours' articles; it is that count divided by the ticker's median daily count over the prior 30 days (1.0 = a typical day). news_volume_weighted_sentiment was described with a tanh(news_volume / 15) scale; the scale is tanh(max(0, news_volume − 1) / 1.5), so a normal or quiet day reads 0. Values are unchanged.
  • Fixed
    The schema docs for news_article now give the shape of ticker_data (per-company rel, sent_score, sent_label) and topics, and the /v2/news page says how to get all 16 columns and when next_cursor is null for a custom select.
v2.68.12026-10-26
  • Fixed
    GET /v2/news rollups with a custom select sort by its last column. A group_by call whose select had no volume column failed with 400 unless order was passed, because the default sort was always volume. It now defaults to the last select item's alias (as /v2/scan and /v2/events do); when that item has no alias, the 400 asks for order.
  • Fixed
    cardinality() is allowed in queries. cardinality(tickers) counts the companies an article tags (e.g. q=cardinality(tickers) = 1 for single-company articles). It applies on /v2/scan, /v2/news and /v2/events.
v2.68.02026-10-26
  • Added
    min_relevance on GET /v2/news and GET /v2/events?kind=news. An article is tagged with every company it mentions, and each tag carries a relevance score from 0 to 1 (ticker_data.<TICKER>.rel). Pass min_relevance=0.8 to keep only articles about the ticker you asked for and drop passing mentions. On /v2/news it applies to the ticker/tickers/universe scope; on /v2/events it requires kind=news alone. Omitted, both return what they returned before.
  • Fixed
    /v2/events?kind=news carries each ticker's own sentiment. payload.sentiment_score and payload.sentiment held the article's overall sentiment on every tagged ticker's row, while the docs described them as per-ticker. They now hold the article's sentiment toward that row's ticker (ticker_data.<TICKER>.sent_score / sent_label), null on articles that carry a label only.
  • Fixed
    The /v2/events docs said ticker wins when both ticker and tickers are passed. The API answers 400 for that combination, and the docs now say so.
v2.67.22026-10-21
  • Fixed
    /openapi.yaml loads in strict YAML parsers again, and declares the fields of predecessors[] and prior_symbols[]. Five column descriptions carried mis-encoded characters (−, –, —, ≥) that made PyYAML reject the file; they read correctly now there and in /docs/schema.json. The ticker row schema now lists each earlier holder's name, cik, composite_figi, tenure_start and tenure_end, and each earlier ticker's ticker, tenure_start and tenure_end; the MCP ticker and scan tools declare the same identity fields. Responses are unchanged.
v2.67.12026-10-21
  • Changed
    The 2026-10-31 sunset moves to 2026-12-15. The six deprecated reads keep serving unchanged until then, and their Sunset header now reads Tue, 15 Dec 2026: GET /v2/tickers/{ticker}/history/{interval}, GET /v2/tickers/{ticker}/history?asof=, GET /v2/signals/{signal}/{ticker}/history/{interval}, GET /v2/tickers/{ticker}/events, GET /v2/analyst/events and GET /v2/signals/{signal}/{ticker}/events. minute_tier on GET /v2/tickers/{ticker}/coverage moves to the same date. The replacements are unchanged; see Deprecations.
v2.67.02026-10-21
  • Added
    OpenAPI describes every response. /openapi.yaml now carries a 200 schema for every operation, built from the same field lists as the docs pages, nested fields and the per-kind event payloads included. A field has a type where we have confirmed it against live responses, and every typed field also allows null; the rest are listed with their description and no type, so a client generated from the spec never rejects a real response.
  • Fixed
    MCP output schemas match what the tools return. Each tool's outputSchema described list fields such as results as arrays of strings, and typed fields that can be null (next_cursor on the last page) without null, so a client that validates results against the schema would reject most of them. The schemas now carry the nested fields, typed where confirmed. Tool inputs and results are unchanged.
v2.66.32026-10-19
  • Fixed
    Bars next_cursor is null on the last page. GET /v2/bars/{ticker}/{interval} set next_cursor whenever a page held limit bars, so a page that already held the last bars of a from/to window, or of the whole history, sent you to an empty page: AAPL 1d from 2020-08-28 to 2020-09-02 with limit=4 returned all four sessions and a cursor. A cursor is now set only when at least one more bar remains, on single-symbol, bulk and asof + limit reads, as on every other paged endpoint. The bars returned are unchanged.
v2.66.22026-10-19
  • Fixed
    The insider buy and sell signals read open-market trades. insider_c_suite_buy was true when a top officer or director received a stock grant, insider_c_suite_sell was never true, and insider_cluster_buy counted grants. They now read SEC Form 4 open-market purchases and sales: buy and sell look back 7 days, and cluster buy needs two or more insiders buying within 14 days. Daily history back to 2003 was rebuilt the same way; AAPL had 1,080 buy days and now has 53. If you stored these signals before 2026-10-17, read them again.
  • Changed
    These three signals are null for a stock with no transaction-coded insider filings on record, where they used to be false. A filter like NOT insider_c_suite_sell now leaves those stocks out; use insider_c_suite_sell IS NOT TRUE to keep them.
v2.66.12026-10-19
  • Fixed
    Quarterly rows are dated by the filing that first reported them. On GET /v2/series?interval=1q, a fiscal year's last quarter carried the date of the next year's annual report, which repeats it, so reported read about a year late and an asof read could not see that quarter for a year. AAPL's quarter ended 2022-09-24 now reads reported 2022-10-28 (it read 2023-11-03), and interval=1q&asof=2023-01-15 ends with that quarter. Dates come from each company's SEC filings.
  • Fixed
    Quarters of 53-week fiscal years are no longer dropped. A quarter ending in the first week of a calendar quarter (AAPL's ended 2023-07-01) shared a grid slot with the next one and one of the two was lost. Each quarter is now placed by its end date less 7 days, so AAPL 2023-Q2 is the quarter ended 2023-07-01 (revenue 81,797M).
  • Fixed
    Daily revenue_ttm history takes in a new quarter on the day it was filed. Because of the late dates above, history added a fiscal year's last quarter 50 days after the period ended, not on its filing date: AAPL read 387,542M from 2022-10-28 to 2022-11-10 and now reads 394,328M from 2022-10-28, the day its 10-K was filed. The other columns built from the same quarters moved with it: gross_profit_ttm, profit_margin_ttm, operating_margin_ttm, return_on_equity_ttm, return_on_assets_ttm and the three growth columns. revenue_ttm is the sum of revenue over the four most recent fiscal quarters filed by that day, and equals the sum of those four rows on interval=1q.
  • Fixed
    Second, minute and hourly bars from before a split are split-adjusted. Bars stored before a stock split stayed on the old basis, while daily bars were right: VCIG's last 1m bar on 2026-07-30 read 0.3493, the unadjusted price, against a 5.2395 daily close after its 1-for-15 reverse split on 2026-08-24, and adjusted=false divided it a second time. It now reads 5.2395. Stored bars were re-adjusted for every stock that split, and a new split now re-adjusts that stock's 1s, 1m and 1h bars the night it executes, so the 5m to 4h roll-ups follow. Bars you stored for these stocks before 2026-10-18 will not match a fresh read.
  • Fixed
    Signal history moves onto the new share basis when a stock splits. Daily, hourly and minute signal values from before a split (price, moving averages, VWAP, 52-week and 20-day highs and lows, volume averages and the other per-share and share-count columns) stayed on the old basis after the bars were adjusted: RUSHA on 2026-07-31 read a price of 79.79 against a 53.19 close after its 3-for-2 split on 2026-09-01, and APH hourly history before its 2-for-1 split on 2026-09-03 read twice the true price. Daily history was rebased for every stock with a split, and hourly and minute history for the 316 stocks that split between 2026-07-01 and 2026-10-12. A new split now rebases that stock's history the evening it executes. Scans, /v2/series and asof reads across a split date no longer jump by the split ratio. If you stored signal history for one of these stocks before 2026-10-12, read it again.
  • Fixed
    Per-share history is on the current share basis for stocks that split after their statements were last updated. For 262 stocks, daily history before the split kept the old share count, so diluted_eps_ttm, revenue_per_share_ttm, market_cap, pe_ratio and dividend_payout_ratio were off by the split ratio: KLAC on 2026-06-10, two days before its 10-for-1 split, read a pe_ratio of 6.64, diluted_eps_ttm of 32.00 and market_cap of $28.1B. It now reads 60.23, 3.55 and $281.3B, in line with the days after the split. History was rewritten on 2026-10-09. If you stored these fields for one of these stocks before that date, read them again.
  • Fixed
    A date range on a symbol that passed between companies returns one company, the same on /v2/series and the bars endpoint. A from/to range now means the company that held the symbol on to; when nobody held it that day, the last company that held it inside the range; with no to, today's holder. Series used to resolve on to or, without it, on from, and returned no rows when to fell after the earlier company left: NLTX from 2008-01-01 to 2011-12-31 was empty and now returns Nile Therapeutics' 694 sessions. The bars endpoint always served today's holder, so BNY for the first days of 2010 was the bank there and the BlackRock fund on series; both now return the fund (14.48 on 2010-01-04). A series read of BNY with only from=2005-01-03 now returns the bank, as it did with from=2003-09-10. Reads without from/to, and asof reads, are unchanged.
  • Fixed
    An as-of read in the two weeks after a symbol changed hands names the company whose price it shows. An as-of read serves the latest daily row up to 14 days old, and in that window right after a handover it named today's company over the earlier company's last price: WM on 2008-09-29 said Waste Management at Washington Mutual's 0.1604, and NYX on 2013-11-15 said NYIAX at NYSE Euronext's 45.29. The name, cik and tenure now come from the company that held the symbol on the served row's date, on GET /v2/tickers/{ticker}?asof= and /v2/scan. Past that window the read is still 404.
  • Fixed
    Three daily highs and lows cut by the daily-bar check are restored. The check that replaces a vendor daily high or low no minute bar reached (v2.52.4) judged the newest session the same evening, on the vendor's provisional minute bars, which can miss a real extreme. JAGX on 2026-10-06 read a high of 7.187 and now reads 7.27; AMRO on 2026-10-16 read a low of 3.95 and now reads 3.87. RUBI on 2026-09-17 was judged against minute bars already adjusted for its 3-for-2 split and read a high of 0.9599; it now reads 1.4399. atr_pct and the other indicators built on these bars are recomputed. A session's daily bar is now checked the next trading day, once the vendor's minute bars are final.
v2.66.02026-10-19
  • Added
    available_at and available_at_source on earnings events and on interval=1q series rows. available_at is when the market could first trade on the report: 9:30 AM ET on the report date for a pre-market release, else 9:30 AM ET of the next session; statements from the first session after filing. available_at_source says what decided it (report_time, filing_date or assumed). An event's ts is unchanged: it is still the report date. See When a report counts as public.
  • Changed
    GET /v2/series?interval=1q&asof= shows a quarter only from its available_at. It used to show a quarter from midnight UTC of its report date, so a post-market report was visible hours before it came out: ticker=AAPL&asof=2026-07-30T21:00:00Z returned the June quarter, which Apple reported after that day's close. It now returns 2026-Q1 until 2026-07-31T13:30:00Z. A bare date still means that day's 4 PM ET close.
  • Changed
    Daily earnings history was rewritten by availability. On every interval=1d row, last_earnings_date, last_fiscal_quarter_end, last_reported_eps, last_eps_estimate, last_estimated_eps, last_earnings_surprise, last_earnings_surprise_pct and earnings_report_time now come from the newest report public by that day's close, all from the same report. Before, a post-market report showed on its own report day, and for days after some reports the row mixed one report's date with another's numbers (AAPL on 2026-07-31 read the July 30 date with the April EPS). Re-pull these columns if you stored them before 2026-10-17.
v2.65.02026-10-19
  • Added
    Every as-of read says when each ticker's history was last rewritten. _meta.history_revised_at maps each ticker in the response to the last time a job rewrote its stored history (split re-adjustments, corrections, re-keyed renames), or null if none since tracking began on 2026-08-26. If the stamp is newer than your last pull of a ticker, re-pull that ticker; the rest are unchanged. It is on /v2/series, /v2/bars (every read, with or without asof), GET /v2/tickers/{ticker}?asof= (single and batch), /v2/scan and /v2/signals/{signal} with asof, and /v2/events?join=state. The newest session is provisional until the next morning's settled-close patch, which is not counted as a rewrite. See _meta reference.
v2.64.42026-10-17
  • Changed
    ex_dividend_date is the nearest announced ex-dividend date, or the most recent one once it passes with none announced. This holds on the ticker row and on every daily history row, as of that row's date. It used to be the furthest-out announced ex-date, so a fund that publishes a year of payout dates showed a date up to a year away (SHYG on 2025-09-15 read 2026-10-01; it now reads 2025-10-01).
  • Fixed
    Daily history no longer shows an ex-dividend date before it was announced. Some dividends in the vendor data carry an announcement date years too early, and history trusted it: MAIN read 2021-10-28 on every day from 2002 to 2021. An announcement dated more than 1,100 days before its ex-date is now treated as known from the ex-date, and MAIN on 2010-02-01 reads 2010-01-19.
v2.64.32026-10-15
  • Fixed
    A symbol that passed between companies names the earlier company on dates before the handover. Where today's holder had been recorded as holding a symbol from the start of our history, an as-of read before the takeover named today's company over the earlier company's prices: WM on 2007-09-14 said Waste Management at Washington Mutual's 35.53. Each earlier holder now has its own record, so WM before 2008-09-27 is Washington Mutual, BUD before 2008-11-18 is Anheuser-Busch and NYX before 2013-11-13 is NYSE Euronext. symbol_reused and predecessors[] list them, tenure_start on today's holder is its first day after the handover, and a series read of today's holder no longer includes the earlier company's prices. Splits belong to the company that went through them, so UPST no longer carries a 2012 split from before Upstart listed.
  • Fixed
    Daily prices of delisted stocks are adjusted for their splits. These stocks had no split records, so a reverse split showed as a jump on the split day (SSH read 0.295 then 8.19 across its 1-for-30 reverse split on 2017-01-13; it now reads 8.85 then 8.19). Split records were loaded for every stock with a split inside its stored history, and daily prices that disagreed with the split-adjusted series by more than 2% were re-adjusted. Bars you stored for these stocks before 2026-10-07 will not match a fresh read.
v2.64.22026-10-13
  • Fixed
    from_open_pct, from_vwap_pct and change_ytd_pct of a symbol's earlier holder are in percent-points. v2.63.1 corrected the other _pct columns on these as-of reads and left these three 100 times too small (RPT on 2009-06-01: from_open_pct 0.0799 for a 9.01 open and 9.73 close). All three now match the prices on /v2/scan, /v2/series and GET /v2/tickers/{ticker}?asof=.
v2.64.12026-10-13
  • Fixed
    A sub-hour bars read of one date is answered for that date. GET /v2/bars/{ticker}/{interval} remembered an empty load per symbol: once a window with nothing in it (a weekend, a date before the first session) came back empty, other dates of the same symbol answered no_data for up to 30 minutes. Each window is now judged on its own.
  • Fixed
    Concurrent sub-hour reads of different windows for one symbol each get their bars. Two requests for the same symbol at once shared a single load even when they asked about different dates, and the second could come back empty with no_data. A request now shares a load only when that load covers its window.
  • Fixed
    A narrow sub-hour window loads its trading sessions whole. A first request for part of a past day (from=…T15:00Z&to=…T16:00Z) stored only that hour, and a later request for the whole day was answered with the hour, labelled covered. A first load now stores each finished 04:00–20:00 ET session it touches in full; the response is still bounded by the window you asked for.
v2.64.02026-10-13
  • Added
    A Shell in the dashboard Workbench. Type any API call and see the response: tickers get NVDA, signals get above_sma_200 --sort_by market_cap, bars get AAPL 1d --limit 30, or a bare WHERE clause such as short_float_pct > 20 AND earnings_this_week, which runs as a scan. Every command maps one-to-one onto a /v2 request, its flags are the request's parameters, and each response comes with the curl that reproduces it from your code. help lists every command, and pasted /v2 paths and curl commands run as-is. Under the Tickers, Signals, Scan and Webhooks tabs it opens with Inspect, which runs the request behind what the tab is showing. Calls typed in the Shell count toward the Free monthly quota, like calls made with a key.
  • Changed
    Try-it runs count toward the Free monthly quota when you are signed in. Every call you compose now counts the same way, whether it comes from your code with a key, from MCP, or from a Try-it panel on these pages. Signed-out Try-it is unchanged: it runs on a per-IP budget of 30 calls an hour and 60 a day. Free-plan responses to a signed-in Try-it carry the X-Quota-* headers, and a run past the quota returns the same 402 monthly_quota_exceeded your code would get.
  • Changed
    The dashboard's tool tabs are capped at 10,000 calls a day per account. Tickers, Signals, Scan and Webhooks refresh on their own and do not count toward the monthly quota; the cap only stops a script from driving the dashboard instead of the API. Past it the dashboard returns 429 dashboard_daily_cap, resetting at 00:00 UTC. Programs use an API key.
v2.63.12026-10-13
  • Fixed
    Percent columns of a symbol's earlier holder are in percent-points. On an as-of read of a company that held a symbol before today's holder, change_1d_pct, change_1w_pct, from_sma_20_pct, position_in_52w_range_pct and the other _pct columns came back 100 times too large on /v2/scan (RPT on 2009-06-01: 799 for a 7.99% day). They now match the company's closes. The same read on GET /v2/tickers/{ticker}?asof= now names those columns as every other read does (change_1d_pct, not day_change_pct).
  • Fixed
    GET /v2/series serves an earlier holder's rows with the default columns, and at interval=1w. A read without columns (ticker=BLD&asof=2003-09-15) returned 400 invalid_query; interval=1w returned no rows. Both now return the holder's rows.
v2.63.02026-10-10
  • Added
    kind=filing on GET /v2/events, and as a webhook trigger. One event per annual or quarterly report a company files with the SEC — 10-K, 20-F, 40-F, 10-Q — dated the filing day, with form, accession, period_end, fiscal_year, fiscal_period, available_at (9:30 AM ET of the next session, the instant point-in-time reads should key on), cik and the EDGAR url. Filings from 2011 on. It joins the default stream as the sixth corporate kind; POST /v2/events/subscribe and webhook trigger.kinds accept it, firing the morning after the filing lands. What is in the filing stays on Series (interval=1y / 1q); this is that it happened.
v2.62.02026-10-10
  • Added
    Revenue breakdown history on the Series fiscal grids. revenue_by_segment, revenue_by_geography and revenue_by_product are now columns at GET /v2/series?interval=1y and interval=1q: one list per fiscal period, back to filings from 2011, in the same element shape as the ticker row's latest-period columns, beside revenue and the other statement columns, with asof, from/to and cursor paging as on every Series read. _meta.sources names them filings.
  • Removed
    GET /v2/tickers/{ticker}/segments (v2.58.0) is gone; it served the same history in a second shape. Read the three columns on Series instead: /v2/series?ticker=AAPL&interval=1y&columns=revenue,revenue_by_segment.
v2.61.02026-10-08
  • Added
    Annual financial statements: GET /v2/series?interval=1y. One row per fiscal year from fiscal 2010 on, in the same shape as interval=1q: income statement, balance sheet and cash flow columns (revenue, net_income, eps_diluted, operating_cash_flow, free_cash_flow, total_assets and 40 more; the list is on Series). Each year carries reported, the filing date of the original 10-K, 20-F or 40-F, and available_at, 9:30 AM ET of the next session: under asof a year appears only from then, so a backtest never sees a year before it was public. ticker=AAPL&interval=1y&columns=revenue,net_income returns fiscal 2025 revenue of $416.16B and net income of $112.01B.
v2.60.02026-10-08
  • Added
    revenue_by_segment, revenue_by_geography and revenue_by_product on the ticker row: the latest published revenue breakdown for each axis, as a list of {name, revenue, revenue_usd, share, period_end, fiscal_year, fiscal_period, currency}. Each is the newest fiscal period (annual or quarterly) whose members sum to the company's total revenue within 0.5%; null when no breakdown has been published for that axis. Select in fields or test with jsonb_array_length(revenue_by_segment) > 0. Backed by GET /v2/tickers/{ticker}/segments (see v2.58.0) for the full history back to ~2011.
v2.59.02026-10-08
  • Changed
    Update cadence on every signal page now comes from the job that writes the signal. The catalog, the per-signal pages, /docs/schema.json and /docs/refresh-cadence read one derived label. The one-minute bucket is live_1m_4am_8pm_et, rendered "1 min · 4 AM–8 PM ET" (for a few hours on 2026-10-08 it was served as live_1m_extended_hours): it was live_1m_market_hours, rendered "1 min · mkt hrs", for 262 signals that are rewritten every minute from 4 AM to 8 PM ET, pre-market and after-hours included. A once-a-day signal shows its clock ("daily · 8 AM ET"). Signals that never change after listing (sector, industry, asset_class) show static. A field that crypto and FX carry too, such as price, says so: "1 min · 4 AM–8 PM ET · crypto and FX 24/7".
  • Fixed
    Wrong cadences corrected. golden_cross, death_cross, bollinger_squeeze, the earnings_* and estimate_* flags, the market-cap buckets and the other nightly flags were labelled as one-minute signals on the ticker row; they are post-close daily. The recent_* analyst-action booleans were labelled every 15 minutes; they refresh hourly, 24/7. golden_regime and death_regime were labelled post-close daily; they are one-minute. earnings_today is set daily at 4:01 AM ET.
  • Changed
    /docs/refresh-cadence: the as_of paragraph now says that as_of minus price_asof measures the row's age only on fair-value-priced rows; on a trade-, quote-, bar- or previous-close-priced row, price_asof is that source's own time.
v2.58.22026-10-07
  • Fixed
    full=true works on past-dated scans again. A scan with asof and full=true on the daily grain (a bare date, or interval=1d) returned 400 invalid_query naming an internal column, __full_row__, instead of the whole row. It now returns every signal for each match, as documented. A misspelled signal in q under full=true is still a 400 that names it, and full=true with interval=1m or 1h is still 400 interval_unavailable.
v2.58.12026-10-07
  • Fixed
    Renamed companies appear in past-dated scans before their rename. A scan leaves out a symbol before its listing date, and for 74 renamed companies the listing date on today's symbol is the rename day, so their whole earlier history was missing from as-of scans and signal lists while the single as-of read served it. Cara Therapeutics (CARA, now TVRD) was absent from every scan before 2025-04-16. Those rows now appear under the symbol the company traded as, with current_ticker naming today's symbol.
v2.58.02026-10-07
  • Added
    Revenue by segment, geography and product line. GET /v2/tickers/{ticker}/segments returns a company's revenue split by business segment, by geography and by product or service line, for each fiscal year (10-K, 20-F, 40-F) or fiscal quarter (10-Q), read from the company's own SEC filings and named with its own labels. A breakdown is shown only when its lines add up to the company's total revenue within 0.5%; when they do not, the period says so and why, with no numbers. Amounts are in the reporting currency and in US dollars at the Federal Reserve's average exchange rate for the period. With asof, you get only the periods that had been filed by then, for the company that held the symbol then. Loaded now: the latest annual and quarterly filing of every listed company over $2B market cap. Earlier periods (from 2011) and smaller companies will follow. See /docs/endpoints/tickers/segments.
v2.57.02026-10-07
  • Changed
    Past-dated scans list each company under the symbol it traded under that day. A company that changed its symbol used to appear in an as-of scan under today's symbol: a 2020 scan listed Facebook as META, a 2004 scan listed Charles Schwab as SCHW. POST /v2/scan and GET /v2/signals/{signal} with asof now return FB and SCH for those rows, so a scan row and the as-of read of the same symbol (GET /v2/tickers/FB?asof=2020-06-01) agree. In q, ticker matches the symbol at the date, and a universe naming the old symbol finds the company. Measured at mid-month dates from 2003 to 2026, 342 renamed symbols of 322 companies are affected, a median of 58 rows per date (29 in mid-2005, 121 in mid-2020, 185 in mid-2024). Live reads and scans without asof are unchanged.
  • Added
    current_ticker on as-of rows. Every as-of scan and signal row, and data on GET /v2/tickers/{ticker}?asof=, carries current_ticker: the symbol the company's history is filed under today, which is the one /v2/series and the bars endpoint take. It equals ticker except on a renamed company's rows before the rename. On the single read, data.ticker is now the symbol at the date (META?asof=2020-06-01 returns FB there), while the top-level ticker is still the symbol you asked for. GET /v2/tickers/FB?asof=2020-06-01 now serves Meta's stored row for that date, naming META in _meta.identity.stored_under.
v2.56.62026-10-07
  • Fixed
    Foreign companies listed in the US report fundamentals in US dollars. For the 379 exchange-listed ADRs (TSM, BABA, SONY, NVO, ASML…), company totals now come from their annual SEC filings (20-F, 40-F or 10-K), converted to dollars at the Federal Reserve's New York noon rates: revenue and profit at the fiscal year's average rate, balance-sheet lines at the rate on the fiscal year's last day. Before, some of these columns carried the company's home-currency figure as if it were dollars (TSM revenue_ttm read 4.4 trillion, its Taiwan-dollar revenue). Covered: revenue_ttm, gross_profit_ttm, revenues, net_income_loss, operating_income_loss, assets, liabilities, equity, cash_on_hand, cash_and_short_term_investments, long_term_debt, the margins and returns built from them, and price_to_sales, pe_ratio and price_to_book from the market cap. These companies report once a year, so the _ttm fields carry the latest fiscal year. Per-share fields (diluted_eps_ttm, book_value, revenue_per_share_ttm) are blank on ADRs until we have a reliable count of ordinary shares per ADR. 335 of the 379 have SEC data in a currency we can convert; the rest stay blank. History follows the same rule, each fiscal year taking effect on the day its report was filed.
v2.56.52026-10-07
  • Fixed
    Only a company's primary listing carries a market cap. Notes and baby bonds, warrants, rights, SPAC units, tangible equity units and operating-partnership units carried their own price times the issuing company's share count as market_cap, along with enterprise_value, pe_ratio and the other valuation ratios built on it, and the cap-size flags. A Comcast note (CCZ) read $231.9B on 2024-01-22 and Ford notes near $100B. These fields are now null on those securities, live and in history, as they are for preferred shares since v2.52.5. Partnership, trust and LLC units that are the company's equity (for example MNR, TXO, PRT) keep their market cap.
v2.56.42026-10-07
  • Changed
    Second-source news articles now carry a summary and a per-ticker sentiment label. On articles from the second news source (Motley Fool, Zacks, GlobeNewswire and others), summary is now the publisher's description, and each ticker's sent_label in ticker_data is the vendor's call for that company: Bullish, Bearish or Neutral. The label is categorical and unscored, so sent_score stays null on these articles and the score-based metrics are unchanged. search now matches text in their summaries. Articles already stored were rewritten the same way.
  • Added
    News history from the second source goes back to 2016. Articles from the second source before 2026-08-30 are being loaded back to the vendor's start (2016-06-22; the feed is sparse before late 2020), and recent_news_count / highly_relevant_news_count history is recomputed to include them.
v2.56.32026-10-07
  • Fixed
    session_open and the fields built on it use the real open. From 09:30 ET, session_open, from_open_pct, above_session_open, gap_filled_today, gap_up and gap_down read a pre-market trade as the open until the official opening price reached us, a median of 17 minutes after the bell. They now use the same open as gap_pct: the first regular-session minute's open, then the official open once it arrives, fixed for the rest of the day. Before 09:30 they are unchanged. Hourly and minute history is being rewritten to the same rule.
v2.56.22026-10-07
  • Fixed
    gap_pct is set by the open and stays set. The gap is the move from the previous close to today's open. Before 09:30 ET, gap_pct is the live gap: the current price against the previous close, updated every minute. From 09:30 ET it is the official open against the previous close, and it does not change for the rest of the day. It used to show a stale pre-market figure until a median of 17 minutes after the open (for example AAPL on 2026-10-07 read 0.10% until 09:46 ET; the gap was 1.00%). For about the first 15 minutes after the open, until the official opening price reaches us, gap_pct uses the first regular-session minute's open, then switches once to the official open. Hourly and minute history is being rewritten to the same rule.
v2.56.12026-10-07
  • Fixed
    repeated_test_of_high and repeated_test_of_low follow their definition. They counted every minute that closed within 0.1% of the session high (or low), starting at 4 a.m., so they were true on most stocks for most of the day, often both at once. A test now counts once each time the price comes back within 0.1% of the regular-session high (or low) after moving away from it, during regular hours only; three tests make the flag true; once the price breaks through and holds beyond the old level for five minutes, the flag is false for the rest of the session. History is being recomputed.
  • Fixed
    Time-of-day flags hold for the rest of the session. morning_strength, afternoon_drift_up, last_hour_rally, last_hour_selloff, pre_close_drift_up and pre_close_drift_down were true for a single minute, so a read at any other time never saw them. Each is now decided when its window ends — morning_strength at 11:30 ET, the others at 16:00 ET — and stays set until the next session starts. They also fired up to 15 minutes late; they now run on our own clock. last_hour_rally and last_hour_selloff compare the 16:00 close with the 15:00 close (±0.5%), as documented. History is being recomputed.
  • Fixed
    hourly_reversal_bullish and hourly_reversal_bearish compare whole hours. They compared two single minutes an hour apart. They now compare each completed regular-session hour (09:30–10:30, …, 15:30–16:00) with the hour before, and stay set through the following hour. History is being recomputed.
  • Fixed
    earnings_today names today's reporters all day. It was set at 20:05 ET for the session that had just ended, so the next trading day showed the previous day's reporters until the evening. It is now set at 04:01 ET from the earnings calendar.
v2.56.02026-10-07
  • Changed
    One _meta vocabulary on every as-of read. The shared keys — interval, interval_requested, interval_reason, blended, intervals_present, sources, frozen_fields, coverage_gap, identity, scope, deprecated_columns and the deprecated alias resolution — are now defined once, at /docs/asof#meta, and every as-of read emits them in that order before its own keys. No key was added, renamed or removed; the order of keys inside _meta may differ from before on scan, signals, series and events join=state. Each endpoint page now lists only the keys that are its own.
  • Added
    _meta on bars. GET /v2/bars/{ticker}/{interval} declares an optional _meta block, present when the read has something to disclose, with the same shared keys.
v2.55.22026-10-07
  • Fixed
    as_of on point-in-time series and bars. GET /v2/series and GET /v2/bars/{ticker}/{interval} with asof now stamp as_of with the instant you asked for, as every other as-of read does and as the envelope documents. They used to stamp the server clock.
  • Fixed
    Bars cursor pages under asof stay bounded by the instant. Following next_cursor from an as-of bars page used to drop asof, so a cursor newer than the instant served bars after it, and a page on a symbol a different company held at the instant left that company's history. Both bounds now apply and the holder is carried across pages.
  • Added
    _meta.frozen_fields on grouped as-of scans. POST /v2/scan with asof and group_by now discloses the seven identity signals served from current state, as row-mode scans already did — group_by=sector groups by today's sector.
  • Changed
    coverage_gap says when it is still being measured. A whole-market scan or signal read pinned to 1m/1h measures its coverage in the background; the first request at a new instant used to report no gap at all, which read as full coverage. It now returns coverage_gap with pending: true, null counts and a note; a repeat a few seconds later carries the count.
  • Fixed
    Point-in-time series no longer suggest from. An intraday asof on the 1h/1m grid carried _meta.from_defaulted and a note to "pass from", a parameter that read refuses with a 400. Both are gone under asof; the grid's look-back is documented on the parameter.
  • Fixed
    last_available on an as-of ticker 404 follows the instant rule. GET /v2/tickers/{ticker}?asof=<instant on day D> that finds no state named a last-available date that could be D itself; it is now at most D−1, the same rule every state read applies, and so is the retired-company state read behind it.
v2.55.12026-10-07
  • Fixed
    Intraday-only signals in the events replay. join=state on /v2/events accepted only the daily table's signal names at every grain, so an hourly- or minute-only signal (morning_strength, top_gainer) was an "unknown column" even with interval=1h or 1m pinned. The names now follow the grain, as on scan: any signal stored at the pinned grain is valid, and under auto any daily or hourly signal is. A signal the chosen grain does not store is a 400 interval_unavailable naming the grains that carry it, including the pin to use for a minute-only signal under auto.
v2.55.02026-10-07
  • Added
    Bulk bars page per symbol. A comma-list request to /v2/bars/{tickers}/{interval} now returns next_cursor keyed by symbol, like coverage: limit caps each symbol, a symbol with more bars in the window than limit carries its own token, and a symbol served in full carries null. Before this, a bulk request for a from/to window wider than limit returned the newest limit bars per symbol with no cursor, so a client could not tell that a symbol had been cut. Continue a cut symbol with a single-symbol request passing its token as cursor. Additive: no existing field changed.
v2.54.12026-10-07
  • Fixed
    Pre-split prices corrected on 141 stocks. When a split was recorded before its effective date, our daily bars were never re-adjusted on the real day, so prices before the split read at the wrong scale (APH and IESC at twice the true price, RUSHA, RUSHB, SF and XRX at 1.5 times). Daily bars for those stocks were re-adjusted on 2026-10-06 and match the vendor's adjusted prices. Our split records are now reconciled with the vendor every night: a split the vendor withdraws or re-dates is no longer applied, and /v2/events?kind=split no longer serves it. If you pulled daily bars for these stocks before 2026-10-06, pull them again.
  • Fixed
    Pre-market and after-hours history for symbols late in the alphabet. From about 2026-09-01 the five-minute extended-hours sweep stopped partway through the market, so symbols after roughly MIUYF (MSFT, NVDA, TSLA and WMT among them) got no premarket_price, premarket_change_pct, afterhours_price or afterhours_change_pct in daily and hourly history. The sweep was fixed on 2026-10-06 and those days are being refilled.
v2.54.02026-10-07
  • Added
    price_source on the live ticker row (GET /v2/tickers/{ticker}, scan fields, the stream): where the row's price came from. fair_value, minute_bar, trade, quote, day_bar or previous_close on stocks and ETFs; exchange_rate or minute_bar on crypto, FX and metals; published_rate on rates. Refresh cadence has the table of sources, in the order we try them, with what price_asof reads for each.
  • Changed
    price_asof is the time of the data behind the price. On a row priced from a trade, a quote or a one-minute bar, and on crypto and FX rows, it is that trade, quote or bar's own time. From 2026-10-06 16:08 UTC until this release those rows carried the time we fetched the price, so a price that had not moved for an hour read as current. A fair-value price keeps the time we fetched it, which is within the last minute.
  • Changed
    When a stock's newest one-minute bar is newer than its last trade or quote, price is that bar's close. price_source reads minute_bar on those rows.
  • Fixed
    On crypto and FX rows, when the exchange-rate quote missed a minute, price could keep the previous one-minute bar's close instead of moving to the newest bar. It now moves.
v2.53.42026-10-06
  • Fixed
    In daily history, the sessions from 2026-08-03 to 2026-09-04 held the 9:00 PM ET live price instead of the settled close, so price, change_1d_pct, session_high, session_low and the indicators computed from them were off on most of those sessions (AAPL on 2026-09-04 read a change of −2.14% instead of −2.51%). Those sessions are being recomputed from the settled daily bars. Sessions from 2026-09-08 on already match the bars.
  • Fixed
    In daily history, dividend_yield divided a dividend stated on its own day's share count by a price stated on today's, so on any stock that later split the yield read too high by the split ratio (AAPL on 2018-06-29 read 6.31% instead of 1.58%), and high_dividend_yield was set on that value. dividend_payout_ratio had the same mismatch against earnings per share (AAPL read 0.95 before its 2020 split and 0.24 after it). Both are being rewritten for every stock that split. dividend and dividend_ttm keep the amount paid on that day's share count.
v2.53.32026-10-06
  • Fixed
    A renamed company no longer carries a previous company's history. Where a company took over a ticker another company had used before, stitching its history across the rename also moved the earlier company's rows onto today's symbol: ELTX (Elicio, which traded as ANGN from 2021) carried Angeion Corporation's 2003 to 2012 ANGN history. 25 symbols were affected, ELTX, CPAY and SPRU among them. Those rows are back under the old symbol with their own holder. tenure_start on the current symbol is the company's real first day (ELTX 2021-02-05, CPAY 2010-12-15), an as-of read before that day answers 404 on the current symbol, and the old symbol at that date returns the earlier company (ANGN?asof=2010-01-04 is Angeion). FB no longer holds a second copy of Meta's 2012 to 2022 daily history, and prior_symbols on META ends FB on 2022-06-09. If you pulled history for a renamed company before 2026-10-06, pull it again.
  • Fixed
    Signal runs carry the minute they started and ended. From early August to 2026-10-04, runs of above_sma_10, above_sma_20, above_sma_50 and above_sma_200 on /v2/events?kind=signal started and ended at 20:00 UTC whatever minute the cross happened, because a nightly job replaced the minute-level runs with daily ones. It no longer does, and the minute-level runs for that period are restored for the roughly 1,240 tickers we hold minute history for (AAPL crossed above its 50-day average at 2026-09-25T16:04Z). Other tickers keep the 20:00 UTC times for that period.
  • Fixed
    gap_up and gap_down in daily history follow the 3% rule. Until 2026-09-18 the nightly write of daily history flagged gaps from 0.5%, so an as-of read or /v2/series at 1d showed gap_up on a day that opened 1% higher (NVDA on 2026-09-04, a 1.16% gap). The write was corrected that day and daily history was rewritten from 2003 on: both flags agree with gap_pct on every daily row. The live row was not affected.
  • Fixed
    volume_today and day_dollar_volume in daily history hold the settled volume. The daily row was saved with the evening's provisional volume and never picked up the vendor's overnight revision, so an as-of read or /v2/series at 1d returned 63% to 90% of the day's final volume on liquid names while /v2/bars/{ticker}/1d was right. Daily history from 2026-06-05 was rewritten from the settled bars on 2026-09-18, and the morning settlement step has carried volume since.
  • Added
    Twelve signals have daily history. earnings_beat_streak, earnings_next_week, recent_upgrade, recent_downgrade, insider_cluster_buy and insider_c_suite_buy from 2003, above_price_target and below_price_target from 2016, high_beta and low_beta from 2004, and high_volume_alert and volume_change_vs_avg from 2003. Each used to start on the day we first computed it: earnings_beat_streak on AAPL began in August 2026 and now reads 8 on 2015-01-06. Filled on 2026-09-18; history_since in GET /v2/signals gives each start date.
  • Added
    recent_news_count, highly_relevant_news_count and news_sentiment_volatility are on the ticker row and in daily history from 2015. Over the trailing 7 days: the articles that mention the ticker, those that score its relevance at 0.6 or higher, and the spread of sentiment across the relevant ones (null under three). Refreshed every 15 minutes. They returned on 2026-09-19; v2.2.0 had removed them.
  • Fixed
    During the trading session on 2026-10-06, price_asof on stocks priced from fair value read about 16 minutes old while price was current, because v2.52.7 stamped it from a vendor time that lags the price. From 15:57 UTC that day price_asof on those rows is current again. A staleness check such as price_asof < now() - interval '15 minutes' no longer flags actively traded names.
  • Fixed
    On crypto and FX rows, price and price_asof no longer step back within a minute. Two updates wrote the row each minute, one from the minute bar and one from the fresher exchange-rate quote, so a caller polling X:BTCUSD could see the older price return. The quote now stays whenever it is the newer of the two.
  • Fixed
    A q that compares a list signal with a quoted word, such as leadership = 'x', answers 400 invalid_query with the test to use instead (IS NOT NULL or jsonb_array_length(...) > 0). It used to answer 500 internal.
v2.53.22026-10-06
  • Fixed
    A reported cash balance of exactly zero is now checked against the SEC filing. Our balance-sheet source sometimes reports zero cash for a company that filed real cash with the SEC (Devon Energy, DVN, read $0 for its June 2026 quarter; its 10-Q shows $950M). A zero is now kept only when the company's own SEC filing also shows zero for that quarter, as it does for Antero Resources; otherwise cash_on_hand, cash_ratio and cash_and_short_term_investments are null for that quarter, on the ticker row and in daily history.
v2.53.12026-10-05
  • Fixed
    In daily history, dividend_date held the date the dividend was paid, while the live ticker row holds the ex-dividend date, so an as-of read and a live read of the same field disagreed (KO on 2026-06-10 read 2026-04-01, the pay date, instead of 2026-03-13, the ex-date). Daily history is being rewritten to the ex-date over the coming nights, matching the live row.
v2.53.02026-10-05
v2.52.102026-10-05
  • Added
    Pre-market and after-hours history back to 2003. premarket_price, premarket_change_pct, afterhours_price and afterhours_change_pct are in daily, hourly and minute history for every stock we hold minute bars for, from 2003-09-10 on, so as-of reads and /v2/series return them. premarket_price is the opening price of the first trade between 04:00 and 09:29 ET, compared with the previous regular-session close; afterhours_price is the closing price of the last trade between 16:00 and 19:59 ET, compared with that day's 16:00 close.
  • Fixed
    Daily, hourly and minute history from 2026-09-21 to 2026-10-02 is missing premarket_price and afterhours_price (the percent changes are present), because the live update was erasing the prices before the day was saved. The cause is fixed (see v2.52.2) and those days are being refilled over the next two nights.
v2.52.92026-10-05
  • Changed
    A query that runs out of time now answers 503 unavailable with Retry-After, not 500 internal. Reads that run a database query (scan, series, ticker reads, events, news) stop after 30 seconds. Until now that stop came back as 500 internal with "Query failed.", which reads as a server bug. It now comes back as 503 unavailable with a Retry-After header and a message saying the query ran past the limit; the same answer applies when the database cannot take a connection. The first read of a historical date is the slow one, so retrying the same request usually answers in seconds. Clients that already retry on 5xx need no change.
  • Fixed
    A q that compares a number column with a quoted word, such as price > 'DOCN', now answers 400 invalid_query naming the value and suggesting the comparison that was probably meant (ticker = 'DOCN'). It used to answer 500 internal.
  • Added
    leadership on the ticker row: the company's current C-suite as a list of {name, title} (CEO, President, CFO, COO, CTO, other Chief officers, General Counsel), from the officers' SEC Forms 3, 4 and 5 and refreshed daily. It is empty for companies that file none, such as foreign private issuers and funds. Select it in fields or test it in q (for example jsonb_array_length(leadership) > 0); it cannot be used in order.
v2.52.82026-10-05
  • Added
    total_debt: total debt from the latest reported balance sheet, in USD. It is short-term borrowings and the current portion of long-term debt, plus long-term debt including capital-lease obligations. Daily history back to 2009 is filling over the next few nights; each value takes effect on the date the company filed it, as cash_on_hand does.
v2.52.72026-10-05
  • Fixed
    price_asof now shows how old a fair-value price is. For stocks priced from the vendor's fair value, price_asof carried the time we fetched the market snapshot, so every such row looked current to the second even when the stock had not traded or been requoted for hours. It now carries the vendor's own update time for that stock: a quiet name after hours reads the time of its last trade or quote. Reverted on 2026-10-06 (v2.53.3): a fair-value price carries the time we fetched it.
  • Fixed
    price_asof is populated on crypto and FX rows (the time of the vendor's exchange-rate quote) and on rates rows (the date of the published observation). It was null on all of them.
v2.52.62026-10-05
  • Added
    GET /v2/tickers/{ticker}/coverage carries live_row: how many published columns the ticker's current row has, how many are populated, and which are null. An OTC-traded ADR such as TCEHY lists its missing fundamentals there.
  • Changed
    GET /v2/health no longer returns last_error in its log and stream blocks. The route needs no key, and the text was raw server output. The error counts and last_error_at are unchanged, so a monitor can still see that an error happened and when.
v2.52.52026-10-05
  • Fixed
    Signal runs no longer end on weekends. The nightly job that keeps signal runs current closed every long-running run on Saturdays (and market holidays) although the signal was still true, so /v2/signals/{signal}/{ticker}/events and /v2/events?kind=signal showed an exit that never happened: AAPL above its 200-day average since 2026-03-31 read as ending on 2026-09-19. Runs closed this way are being reopened. Webhooks were not affected; they evaluate the live row.
  • Fixed
    Preferred shares no longer carry a market cap in daily history. It was computed with the issuer's common share count, so Bank of America's series L preferred read $9.57 trillion on 2024-01-22 and ranked above Apple in historical scans ordered by market_cap. market_cap, enterprise_value and the price-based valuation ratios are null on preferred shares in history, as they already are on the live row.
  • Fixed
    delisted_utc is null on every active symbol. A new security listed on a reused symbol showed the previous holder's delisting date (PCPC, an ETF listed in September 2026, read 2022-12-15), so filtering out delisted names also removed 21 live securities.
v2.52.42026-10-05
  • Fixed
    A daily high or low that no trade reached is now corrected from the minute bars. Our vendor's daily aggregate occasionally carries a high or low that none of that day's minute bars reaches: NVDA on 2024-06-10 read a high of 195.95 where every minute bar tops out at 123.10, which lifted atr_pct from about 3.8 to 8.1 for two weeks and set the 52-week high to 195.95 for a year. Such a high or low is now replaced by the regular-session high or low of the minute bars, at ingest and across stored history; the open and close are never changed, and atr_pct, the 52-week high and low and the other indicators built on daily bars are recomputed for the year after each corrected day. NVDA 2024-06-10 and MSFT 2005-10-27 are corrected now; the sweep of the rest of history runs over the next days.
v2.52.32026-10-05
  • Fixed
    Daily history recomputes a whole row when the closing price settles. Each morning we replace the previous session's provisional closing price with the settled one. Until now only price, change_1d_pct and the volume fields followed; the moving averages, from_sma_*_pct, RSI, MACD, ATR, 52-week and 20-day highs and lows, the multi-period changes and the cross and regime flags kept the values computed from the provisional price. They are now recomputed in the same morning step, and sessions since 2026-09-05 are being recomputed over the next few nights.
  • Fixed
    Daily history is being refilled on the nights a failed vendor request had blanked diluted_eps_ttm, beta, book_value and the other company-overview fields, or last_reported_eps and the last earnings surprise. A blank is filled only where the values on both sides of it are identical and the gap is at most ten trading days, so no value is inferred across a change. Blanks whose neighbouring values differ stay blank.
v2.52.22026-10-05
  • Fixed
    high_52w_date, low_52w_date, last_20d_high_date, last_20d_low_date, days_since_52w_high and days_since_52w_low carry values on the live row. They were null on most tickers, including AAPL, MSFT and TSLA, because the minute update only carried a date forward when the row already had one.
  • Fixed
    premarket_price and afterhours_price hold the extended-hours prices on the live row. The minute update wrote null over them every minute, so they read null while premarket_change_pct was populated.
  • Fixed
    analyst_count on estimate_revision events is populated from the 2026-10-05 evening refresh on. It was null on every event because we read the wrong vendor field. Earlier events keep it null: the vendor keeps no history of analyst counts.
  • Fixed
    long_term_debt (now including capital-lease obligations) and net_cash_flow_continuing fill again from reported statements, starting with the next nightly fundamentals run. Both were null on every row.
  • Changed
    wages, benefits_costs_expenses and income_tax_expense_benefit_deferred are no longer listed on the ticker row. Our financial-statements source does not report these lines, so they were null on every row.
  • Added
    OTC-traded ADRs. About 2,067 foreign companies that trade over the counter as ADRs, among them Tencent (TCEHY), DiDi (DIDIY), Nestlé (NSRGY) and Roche (RHHBY), are rows like any other stock since 2026-09-29, with exchange = OTC Markets (MIC OTCM). They are priced once a day from the previous session's close: price_asof is that close, and day_change, change_1d_pct, volume_today and the session fields are null on them all day. Most fundamentals are null, because these companies do not file US financial statements.
v2.52.12026-10-05
  • Fixed
    dividend_payout_ratio now agrees with diluted_eps_ttm on every row. It was blank on 86 large caps that had both earnings and a dividend (Visa, Costco and Stryker among them) and out of date on others, because it was computed before that night's earnings update. It is recomputed whenever earnings per share changes.
  • Fixed
    A failed nightly request to our fundamentals vendor no longer blanks the fields it would have refreshed. On any given night up to about 150 large caps lost diluted_eps_ttm, beta, book_value, forward_pe and the other company-overview fields, or last_reported_eps and the last earnings surprise, until a later night's request succeeded. Those fields now keep their previous values, and the affected tickers were refreshed on 2026-10-05. Daily history for the nights in question still has the gaps.
v2.52.02026-10-05
  • Added
    cash_and_short_term_investments: cash and cash equivalents plus short-term investments, in USD, from the latest reported balance sheet, on the ticker row and in daily history. When a balance sheet reports no short-term investments the value equals cash_on_hand. History uses the same filing dates as cash_on_hand and is being filled back to 2009 over the next few nights.
v2.51.12026-10-05
  • Fixed
    Sub-hour bars stay current through the session for every symbol. The newest 1m bar on GET /v2/bars/{ticker}/{interval} is the last minute that has closed, and 5m/15m/30m follow it. For a stock or ETF whose bars are loaded on first request, the bars used to stop at that first request and stay there until the next trading day, on the latest-bars read and on asof, before and from/to reads reaching into the same day. Symbols that were already current trailed by up to ten minutes; they follow the last closed minute too.
  • Fixed
    The last bar of an asof read on 5m, 15m, 30m, 2h and 4h carries its whole period. It was built from the first minute (or hour) of the bar only, so its high, low, close and volume differed from the same bar read with from/to: AAPL 5m at asof=2026-09-15T15:00:00Z returned volume 72,352 for the 14:55 bar where the bar is 523,570. 1m, 1h, 1d, 1w and 1mo were never affected.
  • Fixed
    Paging bars with next_cursor or before, and asof at an instant off the interval's grid, answer in about 0.2 s. Each such call used to take 2 to 6 s.
  • Fixed
    The Get bars notes said there was no unadjusted option and no session filter. Both exist and are documented on the same page: adjusted=false and session=regular.
v2.51.02026-10-05
  • Fixed
    cash_on_hand is back, as cash and cash equivalents in USD. It comes from the latest reported balance sheet and does not include short-term investments. Daily history is being filled back to 2009 over the next few nights; in history each value takes effect on the day the company filed it with the SEC, and when only a later re-filing date is known, 90 days after the quarter ended, so a backtest never sees a figure before it was public.
  • Added
    cash_ratio: cash and cash equivalents divided by current liabilities, from the same balance sheet, on the ticker row and in daily history (same filing dates). Null when current liabilities are not reported.
v2.50.02026-10-05
  • Added
    A second news source: Motley Fool, Zacks and GlobeNewswire articles. /v2/news now also carries articles from a second news feed, refreshed every 15 minutes and filled back to 2026-08-30. On names covered mostly by press releases this adds the editorial layer: since 2026-08-30, TOST goes from 10 articles to 21 and ASTS from 51 to 75. A release both sources carry appears once. The response shape is unchanged.
  • Changed
    These articles carry no sentiment score: overall_sentiment_score, overall_sentiment_label, summary and each ticker's sent_score / sent_label in ticker_data are null on them. Their per-ticker relevance (rel) is 1 divided by the number of companies the article is about, so a single-company article counts toward highly_relevant_news_count and news_volume. Every article counts toward recent_news_count; news_volume_weighted_sentiment and news_sentiment_volatility average only the articles that carry a score.
v2.49.22026-10-05
  • Fixed
    cash_on_hand is null until it is re-sourced. The column carried the cash ratio (cash and equivalents divided by current liabilities) rounded down to a whole number, not a dollar amount, so most companies read 0. Treat any value you stored from it as invalid. It is now null on the ticker row and in daily history, and will return as cash and equivalents in USD from reported balance sheets, dated from each filing.
v2.49.12026-10-02
  • Fixed
    /v2/series serves a renamed company's whole history under its current symbol. An unbounded GET /v2/series?ticker=META started on 2022-06-09, the day the symbol changed, while /v2/bars/META/1d and /v2/tickers/META/coverage served the 2012 IPO onward: series floored each ticker at its tenancy on that one symbol, bars at the company's earliest tenancy across every symbol it has held. Both now use the same floor, so META, FISV, SCHW, HOG, VYX, TXNM and every other re-keyed rename read from their first day on series too. Reported by a customer building a backtester.
  • Fixed
    prior_symbols on GET /v2/tickers/{ticker} no longer lists other funds from the same trust. A ProShares ETF listed SKK, GGOV, ZBIO and OILU as its own earlier tickers because every ProShares fund files under one registrant. Identity across symbols is composite_figi first; a registrant cik counts only where it is not shared across several listed securities.
  • Fixed
    GET /v2/tickers/{ticker}?asof=&interval=1d on a date a previous holder owned the symbol answers with that holder (held_at_asof, its tenure window, its retired state) instead of 404 interval_unavailable. The explicit-grain path returned its own 404 before the tenure resolution that the interval=auto path already ran.
v2.49.02026-10-02
  • Changed
    interval=auto on as-of reads now blends grains instead of picking one. At an intraday asof, every signal comes from its freshest grain at or before the instant: minute, then hourly, then the last closed daily session. A scan or signal match set no longer drops to the daily close for every signal because one of them is daily-only, and no ticker is left out because a finer grain lacks it. _meta.blended, _meta.intervals_present and _meta.sources say what contributed; _meta.interval is the finest grain present. Applies to /v2/scan and /v2/signals/{signal} (/v2/tickers/{ticker} already worked this way). On /v2/events with join=state, auto blends hourly and daily on rows and uses daily on group_by, and _meta.state_interval reads auto. To keep a single-grain cross-section, pin interval (1m, 1h or 1d): that read is unchanged, and it is also the fastest, since it reads one grain instead of three. A bare-date asof is unchanged.
  • Fixed
    Paging /v2/scan by a numeric order column at the hourly or minute grain could repeat the last row of one page at the top of the next. The cursor now compares at the precision the response carried.
v2.48.32026-10-02
  • Fixed
    An intraday asof no longer sees that day's close. At a timestamp on day D, daily-grain values (indicators like rsi_14 and sma_50, fundamentals, and the daily price a scan falls back to) came from D's own daily row, which holds D's close: hours after the moment asked about. They now come from the last session that had closed, D-1, the rule bars asof already used. Applies to /v2/tickers/{ticker}, /v2/scan, /v2/signals/{signal}, /v2/series at 1d/1w, and /v2/events with join=state (an event on day D joins the state through D-1). A bare YYYY-MM-DD still means that day's close. If you ran backtests on intraday asof reads, re-run them.
  • Fixed
    next_cursor on as-of reads. GET /v2/series with asof returns next_cursor: null: a point read is one row per ticker, all on one page. It used to return a cursor that asof then refused with a 400. GET /v2/bars/{ticker}/{interval} with asof and limit now accepts its own next_cursor alongside asof, so following the cursor with the same parameters keeps paging back instead of returning 400. asof with before is still a 400.
v2.48.22026-10-01
  • Fixed
    As-of scans serve the identity columns again. sector, industry, asset_type, name, exchange, asset_class and ticker_category work in fields, q, order and group_by on POST /v2/scan with asof. Since 2026-08-24 they were refused with 400 (not available at interval=1d, then Unknown column).
  • Removed
    momentum is no longer a signal. It left the catalog on 2026-09-09 and its history was dropped on 2026-09-18; a query that names it returns 400 Unknown column momentum. momentum_up / momentum_down and the momentum_strong_* flags are unchanged.
v2.48.12026-10-01
  • Fixed
    /docs/schema.json now says which columns /v2/series serves. available_at_intervals had read ["1d"] for every field, including the 75 current-only columns (identity, analyst consensus, estimates, the min_* session fields) that live on the ticker row and have no stored history, so a validator built on the file sent names series rejects. It now lists the stored tiers only (1m/1h/1d/1w), is empty for current-only columns, and each field carries series: true|false, history and history_since. A bars block lists open, high, low, close, volume, vwap and trades, which series serves at every interval; they are not spec signals and had been absent.
  • Changed
    The as-of page no longer describes the forward-only vendor columns (forward_pe, short_interest, days_to_cover, float_shares, institutions_pct, insiders_pct) as awaiting a backfill. Their vendors publish a current value only; they have been held since 2026-06-05 and a snapshot before that returns null.
v2.48.02026-10-01
  • Fixed
    Every as-of ticker read now states which holder it resolved to. GET /v2/tickers/{ticker}?asof= carried held_at_asof, the tenure window, the identifiers and _meta.identity only when a different company held the symbol on that date. When today's holder also held it then, the row shipped the frozen name/asset_type/exchange and nothing to show the date fell inside its tenure — SHLD?asof=2026-01-02 named the Global X ETF with no composite_figi, no tenure_start and no _meta.identity, which read as labelled with today's holder rather than resolved to it. Now every as-of read carries held_at_asof: true, tenure_start/tenure_end (start inclusive, end exclusive, null while open), cik, composite_figi, share_class_figi and _meta.identity with resolved_by: "ticker_tenure". Reads that resolve to a previous holder are unchanged. Additive: no field is removed or renamed.
v2.47.02026-09-29
  • Added
    Trailing dividend and payout ratio. dividend_ttm is the dividends per share paid over the last twelve months — the most recent regular payments at the company's own frequency plus any specials, adjusted for splits — and dividend_payout_ratio is that over diluted_eps_ttm (null when EPS is zero, negative or missing). On the ticker row and in daily history.
  • Added
    When a company last reported. last_earnings_date and last_fiscal_quarter_end give the date of the most recent earnings report and the quarter it covered.
  • Added
    Projected earnings dates. Where no published calendar date exists, earnings_date is projected from the company's own history (last year's report for the same quarter, same weekday) and earnings_date_projected is true. Backtested on 26,320 reports: 87% within a week, median error one day.
  • Added
    ETF fund facts. etf_expense_ratio, etf_net_assets, etf_inception_date, etf_leveraged, etf_turnover and etf_dividend_yield on each ETF's ticker row, in the new fund_facts category.
  • Added
    ratios_asof — the date of the financial data behind pe_ratio, price_to_book, ev_to_ebitda and the other valuation ratios. It was visible as the unpublished _ratios_date until 2026-09-23; it is now published under this name.
  • Fixed
    next_eps_estimate_low / _high, next_revenue_estimate and the revision counts now describe the same upcoming fiscal quarter as next_eps_estimate. They had come from the fiscal-year estimate, so the range sat far above the point estimate (META 6.39 against 27.93–40.31). Companies whose calendar date was missing no longer carry the quarter they had already reported.
  • Fixed
    currency is populated on analyst events. It was null on events since 2026-05-12; the history is filled.
  • Fixed
    News coverage. The news feed had been missing articles its source indexed late — about 90% of the feed since late August, and two gaps in the spring. The missing days are refilled (400k+ articles) and recent_news_count and the other news metrics are recomputed.
  • Changed
    When a row's price is the previous session's close (no trade yet today), price_asof is that close's time instead of null, and day_change and above_yesterday_close are null instead of 0 / false.
v2.46.02026-09-29
  • Added
    Estimate revisions on the event timeline. GET /v2/events?kind=estimate_revision (opt-in) returns each move in the consensus EPS estimate for a fiscal quarter or year: fiscal_date, horizon, old_estimate, new_estimate, change_pct, direction, analyst_count, all first-class in q. History starts 2026-08-22, when we began keeping every consensus change. The default stream is unchanged. See /docs/endpoints/events/query#estimate-revisions.
v2.45.02026-09-28
  • Fixed
    A sub-hour bars page is never answered from an incomplete store. GET /v2/bars/{ticker}/{interval} loads bars for a symbol on its first sub-hour request and serves them from the store after that. Under load, a first request could come back count: 0 with coverage: "not_in_minute_tier", or asof could return a months-old bar labelled covered, and a retry seconds later was right. Now a request waits for the load, concurrent requests for the same symbol share it, and if the bars still cannot be loaded the response is 503 unavailable with Retry-After — never an empty or stale 200.
  • Changed
    coverage on bars is covered or no_data. not_in_minute_tier is no longer emitted: it named an internal precompute roster that has no bearing on what bars you can read.
  • Changed
    A from/to window on a sub-hour interval fills the whole window on first load (up to a year), not only its last 31 days.
  • Deprecated
    minute_tier on GET /v2/tickers/{ticker}/coverage — same internal roster; still returned unchanged until 2026-10-31, then removed. Sub-hour bars are available for every active symbol regardless of it.
v2.44.02026-09-26
  • Changed
    One answer for a wrong column name, everywhere. Every place a column name enters the API — /v2/scan q, fields and order (live and asof), /v2/series columns, /v2/signals/{signal}, custom signal expressions, and the q / columns of a webhook or subscription — now checks the name against the published catalog the same way and says the same thing when it is wrong: 400 invalid_query (404 unknown_signal on the signals path) with Unknown column <name>. It is not a published signal. Did you mean <closest published names>? Catalog: /v2/signals. Before, the wording depended on which check caught it first, and the as-of read said not available at interval=1d about names that exist at no interval.
  • Changed
    Renamed-only columns from the 2026-09-07 percent cutover are served under their old names. atr_percent, free_float_percent, percent_insiders, percent_institutions, short_percent_of_float and bollinger_pct_b — the six whose values did not change — resolve to atr_pct, free_float_pct, insiders_pct, institutions_pct, short_float_pct and bollinger_b anywhere a column is named, and the response says so in _meta.deprecated_columns (requested, use, note). A rename that did not change a value should never have broken a job. The 22 rescaled columns (fraction → percent) stay a 400 with the rename sentence: serving those under the old name would hand back the wrong unit. A custom signal saved with an old name is stored with the new one.
  • Changed
    A column the catalog does not publish is refused in a /v2/scan predicate as it already was in fields — the same rule on both, not only on what comes back.
v2.43.02026-09-23
  • Changed
    Context refs in q accept any catalog symbol. <ticker>.<column> on /v2/scan and webhook q was limited to 15 ETFs (SPY, QQQ, IWM, DIA and the SPDR sectors); it now takes any symbol /v2/tickers returns — an equity (aapl.day_change_pct > 0), a rate (r:sofr.close > 4), a crypto or FX pair (x:btcusd.day_change_pct). The cap of five refs per query is gone; the 4,000-character limit on q is the only bound. Dotted symbols (BRK.B) cannot be qualifiers.
  • Added
    400 unknown_context_ticker names a qualifier that is not in the catalog, checked before the query runs. A typo used to come back as a raw SQL error. 400 context_ticker_ambiguous covers a qualifier that case-folds to two symbols.
  • Changed
    Ticker ids may be up to 64 characters and contain underscores, ahead of the universe rows (U:big_tech) landing in the catalog.
v2.42.02026-09-23
  • Fixed
    GET /v2/signals/{signal} and the signal trigger accept timestamp, date and string signals. The condition grammar was numeric-only and every non-boolean signal was parsed as a number, so the 52 timestamp, date and string signals the catalog lists (price_asof, earnings_date, asset_class, …) returned 400 whatever you sent. condition is now typed like the signal: <2026-09-22T19:00:00Z for a timestamp, >=2026-10-01 for a date, =ETF or !=ETF for a string; numerics are unchanged. The 400 for a missing or mis-shaped condition names the signal's type and the shape it takes. Same grammar on the live read, the as-of read, POST /v2/signals/{signal}/subscribe and POST /v2/webhooks with a signal trigger. Relative windows ("older than 15 minutes") stay a /v2/scan query.
v2.41.02026-09-23
  • Added
    price_asof on the live ticker row (GET /v2/tickers/{ticker}, scan columns, the stream): when the market data behind the row's price was produced, as an ISO timestamp. as_of is when we answered; as_of minus price_asof is the age of the row's live signals. A row whose price_asof is old is priced from data that old; How price is set says what it is for each source, and the price_asof page has the scan that lists them. On the live row; the as-of reads disclose their row time in _meta.sources. price_asof is the time of whichever source produced the price.
  • Removed
    The ticker row returns only the columns the catalog lists. GET /v2/tickers/{ticker} was SELECT * and returned 46 columns /v2/signals never advertised. Gone from the live row: 22 internal fields (every _-prefixed name: _last_trade_timestamp, _repaint_state, _data_quality, _branding_icon_src, _min_timestamp, …) and 23 dead ones (bid, ask, bid_size, ask_size, market, ex_dividend_date, gap_pct_v2, breaking_above_20d_high, breaking_below_20d_low, the seven guidance_* / last_guidance_* fields, and six unpublished financial-statement lines). The as-of read (?asof=) and full=true on /v2/scan hide the same two statuses on the history tables (for example average_volume, consolidating, macd_above_zero, volume_spike, definition_version). fields on /v2/scan now rejects a name the catalog does not list with 400 invalid_query instead of returning it. If you read _last_trade_timestamp for the market-data time, price_asof is the published replacement. Everything /v2/signals lists is unchanged, on every plan.
  • Changed
    Stream update frames: as_of is now the time the frame was pushed, the same meaning as on every REST response. It was the minute-bar time, which read as two minutes staler than the price_asof in the same frame.
  • Added
    GET /v2/health also carries a log block: console errors and warnings in the last five minutes and the last error line, so a fault in the API process is visible from a plain HTTP probe.
  • Fixed
    _meta.null_coverage on a live /v2/scan counted a live-only column such as price_asof as NULL on every row while the rows carried values (it measured the history copy of the table). It now measures the table the scan read.
v2.40.12026-09-23
  • Fixed
    /v2/stream delivers again. From 2026-09-07 the stream sent no update frames to subscriptions with fields:"all", and from 2026-09-18 to none at all: a column named in the stream's field list no longer existed on the table (first atr_percent, renamed to atr_pct by the percent cutover; then 52_week_high and 52_week_low, which the stream's own identifier check rejected), and because the stream reads one query for every subscriber, one bad name failed every push for everyone. Auth, subscribed acks and pong kept working, so a client saw a healthy connection that never spoke. Fixed: the field list is checked against the live table before each push and a stale name is dropped for the subscribers who asked for it instead of failing the tick; the identifier check is the shared one every other endpoint uses; and the stream now reads the live database, so price_asof streams with a value. If you subscribed in that window and saw nothing, nothing was wrong with your client.
  • Added
    GET /v2/health carries a stream block: connections, subscribed tickers, last delivery time and fanout_failures_10m, so a stalled stream is visible from a plain HTTP probe. The three fields the route already returned (rss_mb, event_loop_lag_ms, uptime_s) are now documented.
v2.39.12026-09-21
  • Removed
    Deprecated routes are no longer listed in /openapi.yaml, the endpoint index (/docs/endpoints, /docs/endpoints.md) or /llms-full.txt. The five reads sunsetting on 2026-10-31 (GET /v2/tickers/{ticker}/history/{interval}, GET /v2/tickers/{ticker}/events, GET /v2/signals/{signal}/{ticker}/history/{interval}, GET /v2/signals/{signal}/{ticker}/events, GET /v2/analyst/events) were still in the spec with deprecated: true, and new integrations kept being generated against them. They still serve, still carry Deprecation/Sunset/Link headers, and their docs pages stay up until the sunset; they are just not offered as current to a code generator, an agent or a reader of the index. An alias (an old spelling that serves forever, such as /v2/tickers/{ticker}/bars/{interval}) is documented only on the page of the route it aliases. Successors: /v2/series and /v2/events.
v2.40.02026-09-18
  • Changed
    As-of reads name the company that held the symbol that day. GET /v2/tickers/{ticker}?asof= used to serve a reused symbol's old prices under today's holder (SHLD?asof=2010-06-30 returned Sears' 2010 tape labelled as the Global X Defense Tech ETF). Now, when a different company held the symbol at the requested date, name, cik and composite_figi are that company's, held_at_asof is true with its tenure window, _meta.identity names it, and the current holder's classification fields (sector, industry, asset_type, exchange, asset_class, ticker_category) are null rather than wrong. Symbols held by one company throughout are unchanged.
v2.39.02026-09-18
  • Added
    issuer_country and incorporation_country on the ticker row (GET /v2/tickers/{ticker}, scan columns): where the company is run from and where it is legally incorporated, as ISO 3166-1 alpha-2 codes, from the issuer's SEC EDGAR filings. HUIZ reads issuer_country: cn, incorporation_country: ky; AAPL reads us for both. country is unchanged: it is the listing locale and reads us for every US-listed symbol, ADRs included. Both new fields are null for symbols with no SEC filer identifier (most ETFs, non-SEC filers). Refreshed nightly at 2 AM ET for new and changed filers, and in full every Saturday (the schedule since 2026-09-19).
v2.38.02026-09-18
  • Fixed
    Company icons and logos now load. branding_icon_url and branding_logo_url on the ticker row used to be the image host's own URLs, which answer 401 to anyone without that host's API key — so to every customer the two fields were dead links. They now point at GET /v2/tickers/{ticker}/icon and GET /v2/tickers/{ticker}/logo, which serve the image bytes (PNG, JPEG, SVG or WebP, with the right Content-Type) under your own Tickerbot key — the same Authorization: Bearer header as every other call. Both fields stay null when the issuer has no image on file. Responses carry a year-long Cache-Control and an ETag; the image behind a URL never changes (a new image is a new nightly row value).
v2.37.02026-09-18
  • Changed
    Parameter values are checked at the door. Every documented enum, integer and boolean on a public endpoint is now enforced before the handler runs: an out-of-vocabulary value (dir=up, interval=5m, kind=earnings,foo, asset_type=crypto) or a mis-shaped one (limit=abc, full=maybe) is a 400 bad_request naming the parameter and the accepted values. Previously each handler decided for itself and a few fell through silently (a junk boolean read as false; an unknown asset_type matched nothing). Enum matching is case-insensitive; booleans accept true/false/1/0/yes/no. The docs enums, the MCP tool enums and the server now read one constant, so a value the docs list is a value the API takes.
  • Fixed
    GET /v2/tickers documented exchange as a closed list that included NYSE Arca, Cboe BZX, NYSE American and OTC Link — values the endpoint has always rejected (letters only). It is an open filter: any exchange name or MIC code, as the description said. The list is gone.
  • Fixed
    Comma-list parameters are typed consistently as string[] across every page (scan columns/group_by/select/asset_class, analyst tickers, webhook columns); action and transition on /v2/events now show their closed lists.
  • Added
    MCP tools now declare what they return. Every tool on api.tickerbot.io/mcp (and the npm server) carries an outputSchema — the same key set and field descriptions as the endpoint's Returns table, derived from one declaration — and tools/call returns structuredContent beside the text block. The server negotiates the protocol version (2025-06-18, 2025-03-26 or 2024-11-05, whichever your client asks for) instead of pinning 2024-11-05; both additions are additive, so existing clients keep working unchanged.
  • Fixed
    Every endpoint documents exactly what it returns. The eleven write endpoints (create/update webhook, enable, test, the four subscribe doors, create/update universe, create/update custom signal) had no Returns section; they do now, from the live wire. Bars gained adjusted and session on 2026-09-14 and the page never said so; scan, events and news aggregate mode return truncated (and no next_cursor); the as-of reads of a ticker or a signal carry _meta. Each Returns table is now held equal to the server's own declaration in CI, and the sandbox's live responses are checked against the same declaration, so a field cannot appear or disappear undocumented again.
v2.36.02026-09-17
  • Changed
    MCP: tool names now follow the docs rail — one name per endpoint, derived from the same source as the docs. Renamed: tickerbot_list_signals_catalog → tickerbot_list_signals, tickerbot_get_signals_match → tickerbot_get_signal, tickerbot_get_ticker_bars → tickerbot_get_bars, tickerbot_get_ticker_holdings → tickerbot_get_etf_holdings, tickerbot_get_ticker_sectors → tickerbot_get_etf_sectors, tickerbot_patch_webhook → tickerbot_update_webhook. Folded: tickerbot_get_ticker_history into tickerbot_get_ticker (pass asof), tickerbot_list_system_universes into tickerbot_list_universes (pass owner=system). tickerbot_scan now posts to POST /v2/scan; tickerbot_search_news reads the canonical GET /v2/news. Every retired name answers with a tombstone naming its successor, as the 2026-08-07 retirements do. MCP clients refetch the catalog at session start, so no client config changes.
  • Changed
    MCP: every tool description and parameter list is now the same text the endpoint docs show, plus a short agent-only note where a model needs one. Previously a second hand-written copy — it had drifted (the events tool omitted earnings; three tools kept names from before the bars and ETF path families).
v2.35.12026-09-16
  • Changed
    invalid_query messages are written for the reader. Three mistakes in a q used to come back as raw database text. An unknown column (rsi_99 < 30) now reads Unknown column rsi_99. Did you mean rsi_14 or rsi_7? Catalog: /v2/signals. A numeric or text column standing alone where a condition is needed (rsi_14) reads rsi_14 is a number, not a condition. Compare it to a value, for example rsi_14 < 30. A true/false column compared to a number (high_volume_alert > 30) reads high_volume_alert is true/false. Use it bare, or high_volume_alert = true, not compared to a number. Same on /v2/scan, /v2/events, /v2/series, and the dry-run that validates a webhook rule at creation. The envelope is unchanged: same 400, same error: invalid_query, same request_id; only the text moved. Every other message is exactly what it was.
v2.35.02026-09-14
  • Added
    Two new path families, old paths kept forever. GET /v2/bars/{tickers}/{interval} is the canonical spelling of the OHLCV feed (it was also the most-guessed wrong path on the API), and GET /v2/etf/{ticker}/holdings / /sectors the canonical spelling of ETF composition. /v2/tickers/{ticker}/bars/{interval}, /holdings and /sectors keep serving as permanent aliases — same handler, same response, no deprecation headers, no sunset. The docs, OpenAPI and the MCP tools name the new paths.
  • Added
    Bars: adjusted=false and session=regular. adjusted=false returns prices as they printed on the tape that day instead of split-adjusted (a broker fill from before a reverse split now lands on the chart); volume scales the other way. session=regular keeps sub-hour bars in 09:30–16:00 ET only, which drops late-reported off-exchange prints that land in pre-market minutes; limit counts after the filter. Both are read-time options, echoed in the response. From a customer report; the store is unchanged.
  • Added
    merge_gap_seconds on GET /v2/events?kind=signal. Runs of a flag separated by at most N seconds collapse into one before the unpivot, so a flag with thousands of per-tick fragments yields one enter and one exit per real run (3600 for hourly flags, 86400 for daily). Requires signal and an explicit tickers list, filter mode only; a cursor pins it.
  • Deprecated
    GET /v2/signals/{signal}/{ticker}/events (signal spans) — sunset 2026-10-31, with the rest of the TB-82 slate. It reads the same rows GET /v2/events?kind=signal&signal=X&tickers=Y unpivots into enter/exit point-events, and gap merging moved there. Responses are unchanged until the sunset and carry Deprecation / Sunset / Link headers. The MCP tool tickerbot_list_signal_events is retired; a stale client calling it is told to use tickerbot_list_events.
  • Changed
    Docs reorganised around one vocabulary per family: overview · catalog · state · subscribe. A state page carries both tenses — the live read, then the same call with asof as its ` section. Old page URLs redirect: tickers/symbols → tickers/catalog; tickers|signals|scan/live and /asof → …/state; series/get → series/state; events/all → events/query; tickers/bars → bars/get; tickers/holdings|sectors → etf/…`. The sidebar folds each family into a disclosure row.
v2.34.02026-09-08
  • Added
    GET /v2/tickers/{ticker} takes a list. Put up to 50 comma-separated symbols in the path — GET /v2/tickers/AAPL,MSFT,NVDA — and the response carries data keyed by symbol, requested, count, and not_found (symbols we do not track, which never fail the request). ?asof= works the same way on the list form and means what it means on the single form: the row, and the company that held the symbol, at that instant, with _meta keyed by symbol. One call for a holdings list. The single-symbol response is unchanged.
  • Removed
    BREAKING — GET /v2/tickers is now the symbol catalog and nothing else. It walks every tracked symbol (active and delisted) and returns identity rows only: ticker, name, asset_class, asset_type, exchange, exchange_mic, currency_name, country, cik, composite_figi, list_date, delisted_utc, active. Price, market cap and the day change are gone from the walk. search now ranks an exact ticker first, then ticker prefixes, then name matches, alphabetical within each rank (it used to sort by market cap). Five parameters are retired and return a 400 naming the replacement:
    RetiredUse instead
    ?tickers=A,B,C (full rows)GET /v2/tickers/A,B,C
    ?universe=<id> (full rows)POST /v2/scan with universe and q=price > 0
    ?asof= (who held the symbol)GET /v2/tickers/{ticker}?asof= — resolves the holder and returns its state
    ?min_market_cap=POST /v2/scan with q=market_cap > 1e10
    ?sector=POST /v2/scan with q=sector = 'Technology'
  • Changed
    The spec's profile group is re-cut to match: identity is exactly the catalog row above, classification keeps sector, industry, sic_code, sic_description, ticker_category, and a new company category holds the issuer profile (description, homepage_url, address, phone, branding, total_employees, round_lot, share_class_figi, ticker_root, inactive_at, inactive_reason). Every column is still on the state row; only its catalog tag moved. Why: the same word asof meant symbol tenure on /v2/tickers?tickers= and a state snapshot on /v2/tickers/{ticker}, and the same path returned an 8-column row or a 475-column row depending on a query flag. The catalog now answers only "what is this symbol"; the state route answers only "what is it doing".
v2.33.02026-09-07
  • Changed
    Every percent-typed field returns percent numbers, not fractions: 0.043 → 4.3. One instant — Monday, September 7 at 9:00 AM ET — across REST, scan, webhook payloads, MCP, and the WebSocket stream; no mixed state, no grandfathering. Previously the same field could return a fraction on a live read and a percent number on a historical one, a silent 100x ambiguity. There is now one unit, percent, everywhere. Nearly every affected field is also renamed, so old code fails loudly instead of silently reading wrong numbers — and a request using an old name returns an error naming its replacement. The full mapping:
    Old nameNew nameValues
    day_change_pctchange_1d_pctfraction → percent (0.043 → 4.3)
    change_1wchange_1w_pctfraction → percent
    change_1mchange_1m_pctfraction → percent
    change_3mchange_3m_pctfraction → percent
    change_6mchange_6m_pctfraction → percent
    change_1ychange_1y_pctfraction → percent
    change_ytdchange_ytd_pctfraction → percent
    pct_from_sma_10from_sma_10_pctfraction → percent
    pct_from_sma_20from_sma_20_pctfraction → percent
    pct_from_sma_50from_sma_50_pctfraction → percent
    pct_from_sma_100from_sma_100_pctfraction → percent
    pct_from_sma_200from_sma_200_pctfraction → percent
    pct_from_52w_highfrom_52w_high_pctfraction → percent
    pct_from_52w_lowfrom_52w_low_pctfraction → percent
    position_in_52w_rangeposition_in_52w_range_pctfraction → percent
    pct_from_vwapfrom_vwap_pctfraction → percent
    from_open_pcfrom_open_pctfraction → percent
    premarket_change_pcpremarket_change_pctfraction → percent
    afterhours_change_pcafterhours_change_pctfraction → percent
    revenue_growth_yoyrevenue_growth_yoy_pctfraction → percent
    revenue_growth_yoy_quarterlyrevenue_growth_yoy_quarterly_pctfraction → percent
    earnings_growth_yoyearnings_growth_yoy_pctfraction → percent
    atr_percentatr_pctunchanged (already percent)
    free_float_percentfree_float_pctunchanged
    percent_insidersinsiders_pctunchanged
    percent_institutionsinstitutions_pctunchanged
    short_percent_of_floatshort_float_pctunchanged
    bollinger_pct_bbollinger_bunchanged (stays 0–1)
  • Changed
    gap_pct keeps its name and its value multiplies by 100 (0.03 → 3.0) — the one field that changes scale without changing name. If you filter or alert on it, update your thresholds at the cutover or your rules will effectively never (or always) fire.
  • Removed
    gap — redundant beside gap_pct, which replaces it.
v2.32.02026-08-27
  • Changed
    The sandbox is the API without a key. /v2/sandbox/* now runs every endpoint exactly as /v2/* does: the 365-day as-of floor, the 50-row page clamp, the shorter q limit, the 5-ticker cap on series/events, the latest-day-only bars scope, and the refused-parameter 400s (projections, aggregates, universes, sort_by, events q/join) are all gone. The only thing that differs without a key is the per-IP budget — 30 requests/hour and 60/day — which returns 429 sandbox_limit. 400 history_window_exceeded and 403 free_scope are no longer emitted. The Run buttons in these docs return the same response a keyed call would.
  • Added
    Bars at 2h, 4h, 1w, and 1mo. /v2/tickers/{ticker}/bars/{interval} now serves eleven intervals from 1-second to monthly: 2h/4h roll up the hourly store, 1w/1mo roll up daily bars into calendar weeks (Monday start) and months, with t = bucket start. Same limit/before/from/to/asof controls as every other interval. (These four were previously drawn only by the dashboard chart through a private route, which is gone — the dashboard reads the public endpoint.)
v2.31.02026-08-17
  • Changed
    The signal taxonomy has been rebuilt — category values on /v2/signals rows have changed. Every signal was re-filed bottom-up into 33 categories under 9 groups: grab-bag categories (indicators, edge_alerts, bands) were dissolved into real subjects; the indistinguishable highs_lows/price_extremes pair merged into one highs_lows; the 96-field fundamentals monolith split by statement (income_statement, balance_sheet, cash_flow, margins_ratios, valuation, share_structure, plus short_interest); analyst_ratings split into consensus_ratings, analyst_actions, price_targets, estimates; events split into earnings, dividends, ipos, capital_changes, insider_activity. category has always been output-only metadata — no query parameter accepts it — so no request breaks, but anything displaying or switching on the old strings should re-sync from the catalog.
  • Added
    Signal rows carry their full taxonomy membership, and the response carries the tree. Each built-in row on /v2/signals now includes category_label, group, and group_label beside category (slugs are stable — switch on those; labels are display strings), and flag rows carry definition — the precise firing rule, previously available only in the static schema.json. The response gains a taxonomy block: the 9 groups in derivation order — record (Price, Volume), behavior (Price action), indicator (Technicals), then reported / calendar / reference / opinion / text — each with its definition and its categories' definitions, once per response rather than repeated per row. The same tree ships in /docs/schema.json for offline/agent use.
v2.30.02026-08-15
  • Changed
    Your custom signals are kind: "custom". Catalog rows, create/update responses, and the per-signal history route tagged user-authored signals kind: "expression" while everything else about them said custom — the count_custom counter beside those very rows, _meta.sources on series, error codes, and all prose. One word now means one thing: custom is what a user-authored signal is (the kind value, counterpart of builtin); expression refers only to the SQL text in expr. If your client matches on kind === "expression", switch to "custom"; the ?kind=expression filter value keeps working as a legacy alias, as ?kind=custom always had in the other direction.
v2.29.02026-08-13
  • Fixed
    A ticker returns one company's history, not several. Prices were stored under whatever symbol they traded as, so a symbol that changed hands carried every occupant's history glued into one series: Q returned Qwest, Quintiles and Qnity as a continuous line, and SHLD returned Sears attached to the Global X defence ETF that holds the symbol today. 1,074 symbols carried a prior company's prices; they no longer do, and every indicator derived from them has been recomputed.
  • Fixed
    A company that changed its ticker keeps its history. The other face of the same bug: META began in 2021 and showed a collapse in mid-2022 that never happened, because Facebook's 2012–2022 history was still filed under FB. Renamed companies have been reunited with their own past — META now runs continuously from its 2012 IPO — across 136 symbol changes.
  • Fixed
    Delisted companies are in the universe. The ticker universe was built from the currently-active list, so any company that died before we started tracking was absent entirely: LEH, SIVB and SBNY returned nothing. 6,147 delisted companies have been restored with their real delisting dates and full price history, which makes a backtest over a past universe survivorship-bias-free rather than silently limited to the survivors.
  • Added
    Ticker records carry their symbol's ownership history. tenure_start and tenure_end give the dates the company on the record has held the symbol; symbol_reused is true when an earlier, unrelated company held it; predecessors[] lists those earlier holders with name, cik and composite_figi; and prior_symbols[] lists the same company's own earlier tickers. So META reports prior_symbols: [{ ticker: "FB", … }] and SHLD reports Sears Holdings as a predecessor.
  • Added
    asof resolves which company a symbol meant. GET /v2/tickers?tickers=SHLD&asof=2010-06-30 and GET /v2/tickers/SHLD?asof=2010-06-30 both return Sears Holdings; without the parameter you get the company holding the symbol today. GET /v2/tickers/{ticker}/bars/{interval}?asof= returns that company's prices, not just its name. On /v2/series there is no asof — it is the range endpoint, and the from/to window you request selects the era, so from=2010-06-01&to=2010-06-30 on SHLD returns Sears' prices. asof keeps its one documented meaning everywhere it exists: the state at that instant.
  • Changed
    Bars are no longer clamped at list_date. History used to be cut at the symbol's listing date to avoid serving a previous occupant's prices. That cut too much: a share-class conversion reset Criteo's listing date to 2026 and hid thirteen years of CRTO. The boundary is now the company's actual tenancy, so legitimate history that was hidden is served again.
v2.28.12026-08-12
  • Fixed
    before on GET /v2/tickers/{ticker}/events is exclusive again, as its docs have always said. The bound had been overshooting: before=2026-06-16 returned the 16th, and a time-carrying bound returned up to two extra days (before=2026-08-09T12:00Z returned events dated the 10th). The route converted your bound to a bare date before handing it to the events primitive, and when a date-only window bound came to mean "through the end of that day" (v2.23.0), that conversion silently gained a day. Your bound is now passed through as the exact instant you named — a bare date as its own midnight. If you were compensating by subtracting a day, remove that adjustment. Back-paging with next_cursor is unaffected, and so is to on the successor route /v2/events, which was always correct.
v2.28.02026-08-12
  • Fixed
    Aggregating over a payload field works. Naming a rollup key whose alias matched a payload field — group_by=payload->>'firm' AS firm on /v2/events?kind=analyst, the flagship example on All events — returned 400 invalid_query "syntax error at or near (". Single-kind payload fields are rewritten to their payload->> expression before the query is compiled, and that rewrite was also hitting the name after AS, producing … AS ((payload->>'firm')). Aliases (and cast targets) are now left alone wherever the rewrite runs: /v2/events payload fields, and custom signals on /v2/scan, /v2/news and join=state. The same fix lands an aliased key on /v2/scan, where group_by=sector AS s was syntax error at or near "AS" — the alias reached GROUP BY, where SQL does not allow one.
  • Changed
    No rollup column comes back as ?column?. An un-named group key or select item that Postgres declines to name — payload->>'firm', a || b — was keyed by the literal placeholder ?column? in the JSON body. Such columns are now named: a payload read takes its key (payload->>'firm' → firm), a field you spelled bare keeps your word (group_by=firm → firm), and anything else falls back to group_1, group_2. Columns Postgres already names — bare columns, casts of them, function calls like lower(source), COUNT(*) FILTER (…), and CASE — are untouched, so no existing key changes. Applies to /v2/events, /v2/scan and /v2/news aggregate mode. order= can now name a derived key.
  • Changed
    On /v2/events, the echoed query object returns q, select, group_by and having exactly as you sent them. It previously echoed the compiled SQL — group_by=firm came back as ["((payload->>'firm'))"] — which made a diff of sent-vs-returned look like the request had been rewritten. /v2/scan has echoed your spelling since v2.20.0; the two now match.
v2.27.02026-08-11
  • Deprecated
    GET /v2/tickers/{ticker}/history?asof= (the no-interval second spelling of the as-of read) now carries Deprecation + Sunset: 2026-10-31 + successor Link headers, joining the four reads deprecated in v2.17.1 on the same sunset date. The canonical spelling, GET /v2/tickers/{ticker}?asof=, returns the byte-identical response — migration is a one-line URL swap, nothing else changes. On or after the sunset date the alias may return 410 Gone. (v2.17.1 called this spelling "blessed" and kept it; that call was reversed — one capability, one URL.)
v2.26.02026-08-10
  • Changed
    Numeric fields are now JSON numbers everywhere. A handful of endpoints — /v2/scan (live and as-of), /v2/tickers/{t}, /v2/tickers/{t}/holdings, /v2/tickers/{t}/sectors, and webhook payload rows — returned numeric quantities as strings ("price": "307.1440", "weight": "0.07760000") while the docs showed bare numbers ("price": 121.09) and other endpoints (series, bars, events) already emitted numbers. The whole surface now follows one convention: every numeric quantity is a JSON number; strings are reserved for text, identifiers (CIK, FIGI, cursors), and dates/timestamps. Values are numerically identical — only the type and insignificant trailing zeros change ("0.07760000" → 0.0776). The sole exception: integers too large for a JSON double to hold exactly (beyond 2^53) keep their string form — today that is only the nanosecond-epoch columns _last_trade_timestamp, _last_quote_timestamp, and _snapshot_updated_ns on the full ticker row, which were strings before and are unchanged. If your client declared the flipped fields as strings, loosen it to a number type; parsers that already called parseFloat/float() are unaffected. This moves the API to its long-documented contract.
v2.25.02026-08-10
  • Fixed
    transitions_only on /v2/series dated the same flip differently depending on which other columns rode along: with a bar column (say close) in columns, a flip recorded on a weekend/holiday carry row was re-dated to the next trading day by the non-trading-day drop; without one it kept its original date. Flips now always keep the date the state table recorded them — the drop no longer applies under transitions_only (its output is already sparse, so there are no gap-looking rows to protect). Bar columns on such a row are null and count in _meta.coverage.*.missing_bar_cells.
  • Fixed
    On GET /v2/events with kind=signal, request validation now runs before the signal-log readiness check. A malformed query (group_by over kind=signal, or q/join=state without signal=) sent while the log was unavailable answered 503 kind_unavailable — documented as retryable — instead of its 400, so a well-behaved client would retry a request that could never succeed. A 503 now guarantees the query itself is well-formed.
  • Changed
    Unknown-path 404 bodies now point somewhere. Every "no such endpoint" response carries docs_url (the API reference), and recognized near-misses of real routes additionally carry suggestion — the route you probably meant — echoed in the message as "Did you mean …?". GET /v2/bars suggests /v2/tickers/{ticker}/bars/{interval}; /v2/news/query suggests /v2/news/scan; /v2/events/all suggests /v2/events. Resource 404s (unknown ticker, webhook, delivery) are unchanged. If your client sees suggestion, switch routes — retrying the same path will 404 forever.
v2.24.02026-08-08
  • Removed
    /openapi-gpt.yaml (the ChatGPT custom-GPT Actions spec) retired: the GPT Store path was dropped 2026-06-12 (Actions support only shared-key auth), ChatGPT connects via the MCP server with per-user OAuth instead, and the spec had no remaining consumers. The full spec remains at /openapi.yaml; GPTs built from the old URL keep working (Actions snapshot schemas at import).
  • Added
    to on GET /v2/webhooks/{id}/deliveries — the upper window bound, completing from. Same value grammar as from (epoch seconds, epoch milliseconds, or ISO datetime); a date-only to means through the end of that UTC day, matching bars, series, spans, and events. from after to is a 400.
  • Changed
    sort_by on GET /v2/signals/{signal} now rejects unrecognized values with a 400 naming the two valid ones (default, market_cap). A typo like sort_by=marketcap previously fell through silently to the default order, so results looked plausible while ignoring what you asked for. Note sort_by is deliberately a two-position switch — for ordering by arbitrary columns, use /v2/scan with order/dir.
  • Changed
    PATCH /v2/signals/{name} and PATCH /v2/universes/{id} now reject unknown body fields with a 400 listing what each accepts, matching webhook PATCH. Unknown keys were previously ignored, so a PATCH of only unknown fields returned 200 with an unchanged record — reading as success.
  • Fixed
    fields (the documented alias of columns) now works on /v2/series?interval=1q. The quarterly arm only read columns, so ?interval=1q&fields=eps was a 400 while the same request with columns=eps worked.
  • Fixed
    A malformed from/to on GET /v2/signals/{name}/{ticker}/history/{interval} for a custom signal now returns a clean 400 naming the expected format, instead of a database cast error surfacing as a 500.
v2.23.02026-08-07
  • Added
    from/to time windows on GET /v2/tickers/{t}/bars/{interval} and GET /v2/signals/{s}/{t}/events (signal spans). Same conventions as /v2/series: from inclusive, a bare YYYY-MM-DD to means through the end of that day, and cursor pages backward inside the window. On bars these params used to be silently ignored; on spans they were advertised and ignored — "golden crosses in June" returned all-time data. Contradictory combinations (from/to with asof or before) are a 400, and a spans cursor now carries its window, so replaying it without resending from/to stays in-window (resending conflicting values is a 400).
  • Changed
    A date-only to/until on GET /v2/events (and its per-kind views and /v2/analyst/events) now means through the end of that day, matching bars, series, and spans. to=2026-06-30 previously bound at that day's midnight and silently excluded the whole named day on timestamp-grained kinds. Timestamp-bearing values keep their exact exclusive semantics.
  • Added
    from (alias since) on GET /v2/webhooks/{id}/deliveries accepts epoch milliseconds (13+ digits) alongside epoch seconds and ISO datetimes — bare digit values on bars/series/spans are milliseconds, so a value reused across surfaces no longer lands ~50,000 years out.
  • Added
    New error code unknown_parameter (400): a query/body parameter name the endpoint does not accept is rejected, and the message lists every accepted name — ghost parameters (tickr=, condtion=) no longer succeed while meaning something else. Rolling out in warn mode first (unknown names are logged, requests pass through); enforcement follows.
  • Changed
    MCP: four tools retired with graceful tombstones — get_ticker_history_series and get_signal_history → tickerbot_get_series, get_ticker_events → tickerbot_list_events with ticker=, list_analyst_events → tickerbot_list_events with kind=analyst. Calling a retired name returns an error naming the successor and the argument mapping instead of a bare "Unknown tool". Four tools added in the same pass: get_series, get_ticker_coverage, create_webhook, patch_webhook. list_events also gains the structured firm/action analyst filters (case-insensitive firm match).
  • Changed
    The GPT Action spec (/openapi-gpt.yaml) restores list_signal_events — the only span-shaped read; /v2/events?kind=signal returns point edges, not spans — and drops get_stream_usage (a dashboard concern), staying at 29 operations under ChatGPT's 30-op cap.
v2.22.02026-08-06
  • Removed
    POST /v2/scan/explain (and its GET form). The endpoint now returns 410 Gone. Its job — telling you whether a query would run — is already done by the scan itself: an invalid q returns the same 400 with the same message, and every scan response echoes the query it executed (query, plus _meta on as-of reads for the resolved interval). If you used explain as a pre-flight in CI or before subscribing, run the scan with limit=1 instead; subscribing also validates the query and creates nothing on failure.
v2.21.02026-08-05
  • Added
    interval on as-of reads (/v2/scan, /v2/signals/{signal}): 1m, 1h, 1d, or auto (the default, which is the previous behavior). State is stored at three grains and they do not carry the same columns, so a cross-section — which must resolve to ONE grain — had its grain decided implicitly by the projection list, the universe scope, and how far back the instant was. Asking for one 1d-only column such as rsi_14 re-dated every other column in the request. With interval set that is a 400 interval_unavailable naming the column and the grains that carry it. Same parameter name and values as /v2/series and /v2/tickers/{t}/bars.
  • Fixed
    ?asof= on /v2/tickers/{t}/bars/{interval} returned bars from the FUTURE relative to the requested moment. The read was bounded 24 hours past the instant, and because daily bars are stamped at the session date's midnight ET, a mid-session timestamp pulled in the NEXT session's close: ?asof=2026-07-29T14:00:00Z (10:00 ET) returned close 333.43, which is the 07-30 close — the 07-29 close was 338.19. asof now returns the most recent bar whose period had CLOSED at or before the moment. A bare YYYY-MM-DD still means that day's close and is unchanged. If you built a backtest on intraday asof bars, re-run it.
  • Fixed
    GET /v2/tickers/{ticker}?asof= returned none of the columns its own _meta.frozen_fields advertised — name, sector, industry, asset_type, exchange, asset_class, ticker_category were absent from data entirely, while the live read of the same endpoint returned them. They are now joined from the current ticker row, as /v2/scan?asof= already did.
  • Changed
    _meta.interval (1m/1h/1d) replaces _meta.resolution (minute/hourly/daily) on every as-of response, and _meta.state_interval replaces _meta.state_resolution on /v2/events?join=state. The old keys remain as deprecated aliases with their old values. This makes interval the single vocabulary for "which grain" across series, bars, as-of reads and the state join — it was previously spelled three different ways. Also new: _meta.interval_reason (always present, says which grain ran and why) and _meta.coverage_gap now reports on the fallback path too, not only when the chosen grain was already fully covered.
  • Fixed
    Whole-market intraday as-of reads were pinned to 1d by a coverage check with an absolute 25-ticker tolerance. Measured on 2026-07-31, hourly missed 30 of 13,732 tickers (0.22%) and failed by five — while the minute tier's 92% shortfall was judged by the same constant. The tickers involved are active SPAC warrants, units and rights that simply never print intraday, so no fixed count could be correct. The threshold is now a fraction of the universe, and the gap is disclosed either way.
  • Fixed
    The as-of grain for a given instant no longer depends on which date another caller asked about first. Coverage verdicts for every instant inside the last 7 days shared one cache entry, so the same request could return 1h or 1d depending on cache state. Verdicts are now per instant.
  • Fixed
    Default columns a grain does not store (for example market_cap at 1m) are returned as null and named in _meta.columns_not_stored_at_interval, instead of being dropped from the row. The response shape no longer changes with the grain.
  • Fixed
    The three /v2/sandbox/* as-of routes (/tickers/{t}, /tickers/{t}/history, /signals/{s}) now run the same handlers as the keyed endpoints. Their own implementations had no staleness floor, answered as_of with the CURRENT time on a historical row, silently truncated an intraday asof to a date, and emitted no _meta. This also fixes the 500 on /v2/sandbox/tickers/{t}/history?asof=, which was an unbounded scan.
  • Fixed
    A ticker whose most recent state sits exactly on the staleness boundary is no longer served by /v2/scan and /v2/signals while 404ing on /v2/tickers. The coverage probes used an exclusive bound and the serving queries an inclusive one; all of them now share one definition.
  • Changed
    ?asof= on bars honors an explicit limit (the last N closed bars) instead of silently overriding it, and asof combined with before/cursor is now a 400 instead of asof quietly winning. A malformed asof is a 400 rather than falling through to the live tail.
v2.20.02026-08-05
  • Added
    GET /v2/events?kind=signal now takes the q grammar and join=state — scoped with two new params, signal=<flag> and transition=enter|exit. signal= is required for q/join=state (filter mode needs neither) — naming the signal binds the query to an index over the ~175M-row firing log, so "every golden_cross enter across the market this week" returns in milliseconds instead of timing out. transition= is an ordinary optional filter. group_by over kind=signal remains unsupported — an aggregate has no limit to stop at, so its cost tracks how often the signal fires. See /docs/endpoints/events/query#signal-firings.
  • Changed
    Breaking, kind=signal only: the payload field direction is renamed transition. /v2/series has always called this exact primitive a transition (transitions: { above_sma_200: "enter" }) and both are computed by the same shared rule, so direction was the lone dissenting name. Values are unchanged: enter / exit.
  • Fixed
    kind=signal with q or join=state covering BOTH transitions no longer times out on high-frequency signals. Each edge branch now carries its own sort order, so the database merges two ordered streams and stops at your limit instead of reading the whole window and sorting it. above_vwap over 7 days went from a 30-second timeout to 31 ms.
  • Fixed
    Event-trigger webhooks carrying tickers returned 500 (POST /v2/events/subscribe, POST /v2/webhooks) — a missing import left over from the shared-ticker-parser refactor.
v2.19.02026-08-04
  • Added
    Rates, FX and crypto are now first-class on the ticker-scoped endpoints. /v2/tickers/{t}, /v2/tickers?tickers=, /v2/series, universes and ticker-scoped webhooks all accept prefixed symbols — R:SOFR, R:UST10Y, X:EURUSD, X:XAUUSD, X:BTCUSD. They were already returned by /v2/scan; now the whole surface agrees. Daily history runs deep: rates to 1990, spot metals to 1968, crypto to 2010. See Asset symbols for what each class carries.
  • Added
    The signal catalog reports per-field as-of behavior: historized (the value at that instant), frozen (an identity column joined from the current row — sector as of 2020 is today's sector), or unavailable. Previously the three were indistinguishable.
  • Fixed
    As-of scans no longer silently drop requested static columns. ?fields=ticker,sector&asof=… returned everything except sector, while _meta.frozen_fields advertised it as available — filtering and grouping on those columns had always worked, only projection was broken.
  • Fixed
    Bars for instruments with no intraday range (interest rates) return null for open/high/low/volume instead of 0. A stored NULL was being coerced on serialization, which floored any min() computed over the response and drew a zero candle on charts.
  • Fixed
    Well-formed non-equity symbols get an error naming their asset class instead of "Invalid ticker". /v2/news, /v2/events and /v2/analyst remain equities-only by definition — a rate pays no dividend — but they now say so. /v2/events also validates ticker format on the first page, not only on cursor pages.
  • Removed
    BREAKING — GET /v2/tickers?asset_type=crypto is rejected. It served a separate crypto table that stopped updating on 2026-06-18, so it had been returning weeks-stale prices. Crypto now lives in the main ticker list under its X: symbols: use ?tickers=X:BTCUSD,X:ETHUSD or scan for it. asset_type keeps its real meaning — the instrument type within equities (CS, ETF, ADRC, …), which is a different axis from asset class.
v2.18.02026-08-03
  • Added
    columns is now the one projection parameter name across the API — on /v2/scan (additive to the defaults), /v2/tickers/{t}/history (replaces the defaults), /v2/series, and webhook subscribe payload fields. The original fields spelling is accepted forever.
  • Added
    /v2/news gains the events-style scoping sugar: ticker, tickers (≤50), universe, and from (inclusive) / to (strictly before) AND into the WHERE — and q becomes optional once any of them is present. ?ticker=NVDA&from=2026-07-01 needs no SQL.
  • Added
    from/to are now the canonical range names on /v2/events and /v2/analyst/events too; since/until accepted forever.
  • Added
    Ticker subscribe (POST /v2/tickers/{t}/subscribe) takes q — it was always the scan grammar wearing the name condition; condition accepted forever.
  • Added
    Cross-ticker context refs (spy.sma_50) now work identically on webhook subscribe and the docs sandbox, and signed-in users' custom signals inline on the sandbox — the same query is valid live, pushed, or sandboxed.
  • Added
    New error code expanded_query_too_large: your q is under the 4,000-char limit but expands past the 100,000-char execution bound after custom-signal inlining. Distinct from bad_request so you can tell "too long" from "expands too much". Any q /v2/scan accepts is now subscribable — the old subscribe-side 1,500-char post-expansion cap is gone.
  • Added
    Cursors everywhere they were missing: the tickers crypto list, 1q history, sandbox signals, and the admin tickets list now emit real next_cursor tokens.
  • Changed
    Date params parse ONE strict ISO subset everywhere: YYYY-MM-DD or YYYY-MM-DDTHH:MM[:SS[.sss]]Z. /v2/events and /v2/analyst/events previously accepted loose formats ("March 3 2024") that every neighboring endpoint rejected — those now 400.
  • Changed
    Fail-loudly pass: unknown keys in a webhook PATCH body are rejected instead of ignored (the trigger and channel are immutable by design — the error now says so); a condition sent with a boolean/custom signal subscribe 400s instead of being silently ignored; sending both ticker and tickers 400s on events read + subscribe (each side used to pick a different silent winner); /v2/stream names malformed symbols in an invalid array instead of silently dropping them; /v2/events cursor pages reject query-string filters that conflict with the cursor's pinned set; the docs sandbox 400s on unsupported params (tickers/scan/signals) instead of silently ignoring them, honors limit up to its 50 cap, and gains the POST scan form.
  • Changed
    BREAKING — order on /v2/news and /v2/events now takes a bare column name or SELECT alias only; SQL expressions in order are rejected (alias the expression in select and order by the alias). Expression order is also what broke news aggregate paging.
  • Changed
    BREAKING — one aggregate cap set everywhere: group_by ≤ 1,000 chars and 1-6 keys, select ≤ 2,000, having ≤ 1,000, on scan, news, and events alike.
  • Changed
    Analyst events cursor pages now apply your filters on every page (page 2 of a ?ticker=AAPL walk used to return other tickers). Resend the same filters alongside the cursor — see the pagination guide for the two cursor models.
  • Changed
    DELETE returns 204 No Content uniformly (custom signals joined universes/webhooks/devices). Device records use snake_case keys (device_name, created_at, last_seen; expo_push_token on register) — camelCase spellings accepted forever on input.
  • Removed
    Internal identifiers (userId/keyId on webhooks, ownerType/ownerId/createdByKeyId on universes) no longer appear in responses. They were bookkeeping, not contract — use system: true to distinguish platform universes.
v2.17.12026-07-31
  • Changed
    Anonymous sandbox rate limits raised: 30 queries/hour (was 10) and 60/day (was 30) per IP. Signed-in callers were and remain exempt from the IP budget.
  • Added
    Sandbox mirrors for the two new primitives: GET /v2/sandbox/series and GET /v2/sandbox/events — the docs pages for /v2/series and /v2/events now have Try-it. Sandbox clamps apply (5 tickers, 50 rows, 1-year window), and sandbox events is filter mode only: q, aggregates, join=state, and universes need an API key.
  • Fixed
    Sandbox GET /v2/sandbox/tickers/{ticker} silently ignored ?asof= and returned the live row. It now honors asof within the sandbox's 1-year window, same semantics as the authed read.
  • Changed
    The sandbox demos for two deprecated reads were retired: per-ticker events (it served a legacy archive, not what the real endpoint returns) and per-signal history. Their successor pages — /v2/events and /v2/series — carry the live Try-it demos.
v2.17.02026-07-31
  • Deprecated
    Four legacy reads now carry Deprecation + Sunset: 2026-10-31 + successor Link headers. Each has a strict superset: GET /v2/tickers/{t}/history/{interval} → /v2/series?ticker=, GET /v2/signals/{s}/{t}/history/{interval} → /v2/series?ticker=&columns=, GET /v2/tickers/{t}/events → /v2/events?ticker=, GET /v2/analyst/events → /v2/events?kind=analyst. Responses are byte-identical until the sunset date; after it the routes may return 410 Gone with a pointer at the successor. NOT deprecated: GET /v2/tickers/{t}/history?asof= (the blessed second spelling of the as-of read), /v2/news/scan (answers forever), the /subscribe shortcuts, /v2/tickers/{t}/bars, signal spans, and ?condition=.
v2.15.12026-07-28
  • Added
    GET /v2/tickers/{ticker}/coverage — per-ticker data coverage: data spans per resolution (bars, daily, hourly, minute), minute-tier membership, and per-field measured backfill depth where the backfill engine has probed. Answers, before you query, whether "no rows" would mean "the signal never fired" or "no data at that depth". Available on every plan. See /docs/endpoints/tickers/coverage.
v2.16.02026-07-30
  • Added
    GET /v2/series — the canonical series read: up to 50 tickers × 25 columns on one shared, aligned time grid. OHLCV names, schema columns, and your custom signals mix freely in columns; sources and per-ticker coverage are disclosed in _meta; a missing cell is null, never a silently dropped row. A bare /v2/series?ticker=X returns the ticker-history default columns. See /docs/endpoints/series/get.
  • Added
    transitions_only=true on /v2/series: rows filter down to the state-change edges of boolean columns — built-in flags and custom signals both — with non-boolean columns riding along (the price at the flip). Computed by the same shared rule that fires webhooks.
  • Added
    interval=1w on /v2/series — real weekly resampling: state columns sample the week's last observation, OHLCV aggregates (first open, max high, min low, last close, summed volume), rows keyed by the ISO week's Monday. /v2/signals/{s}/{t}/history/1w now applies the same rule — previously 1w returned daily rows with no resampling.
  • Added
    interval=1q on /v2/series — quarterly fundamentals (eps, eps_estimate, eps_surprise, eps_surprise_pct, revenue, gross_profit, free_cash_flow) on the fiscal grid, keyed by calendar quarter (2026-Q2) with each ticker's exact fiscal_period per row. Quarterly columns can't mix with daily ones in one request.
  • Added
    Two opt-in kinds on GET /v2/events: signal — boolean-flag firings as enter/exit point-events with the price at the edge (the span shape stays first-class at /v2/signals/{s}/{t}/events) — and news, mirroring the article archive into the timeline. The default stream is unchanged: the four corporate kinds. kind=signal is filter-mode only: q, aggregates, and join=state over the signal log are refused with a 400 rather than timing out. See /docs/endpoints/events/query#signal-firings.
  • Added
    join=state on GET /v2/events: ticker-state columns become legal in q/select/group_by/having, evaluated against each event's ticker as of the event's timestamp — point-in-time replay. "Downgrades on stocks above their 200-day" is one call. Daily resolution, echoed as state_resolution in the response's query object. Available on every plan.
  • Added
    q_truncated: true on /v2/events responses whose q was too long to ride inside the cursor — resend q alongside cursor proactively instead of discovering it on a 400.
  • Changed
    Per-call caps unified at 1,000 rows across the cursor-paged read surfaces. Custom-signal history previously allowed 5,000 rows on one page (an accident of routing — which cap you got depended on whether the name was custom); it now pages at 1,000 like everything else. Signal spans (/v2/signals/{s}/{t}/events) deliberately keeps its 5,000 clamp — it has no cursor, so a lower cap would strand spans past it.
  • Fixed
    The dashboard mirror of the per-ticker event log served a divergent legacy implementation reading a different archive. It now serves exactly what GET /v2/tickers/{ticker}/events serves. The public path is unchanged.
v2.15.02026-07-27
  • Changed
    Event webhooks now support all four kinds — insider joins dividend, split, and analyst as subscribable. The insider archive gained the ingestion timestamp the fire-on-ingest trigger needs; only filings recorded after 2026-07-27 are eligible, so historical rows can never fire. The short-lived kind_not_subscribable (400) error is retired.
  • Added
    Aggregate scans: group_by (with optional select and having) switches /v2/scan from ticker rows to rollups — market breadth by sector, counts of new highs, average RSI per group — on both the live and asof paths. Same grammar as /v2/news and /v2/events aggregation.
  • Added
    GET /v2/events — one cross-ticker timeline over dividends, splits, insider transactions, and analyst actions, with kind/tickers/universe/since/until filters. It also speaks the same SQL grammar as /v2/scan — q / select / group_by / having over (ticker, ts, kind, payload) — for filtered timelines and rollups (insider buys by sector, dividend counts per month). The per-ticker /v2/tickers/{t}/events and /v2/analyst/events remain as filtered views of the same data.
  • Added
    Event webhooks: POST /v2/events/subscribe (or POST /v2/webhooks with trigger: {type: "event"}) fires when NEW events land — with an optional row-state filter q (the ticker's state) and event_q, a filter on the event's own payload (e.g. only insider buys over $1M). Deliveries carry event: "events.fired". Latency is ingest cadence: analyst ≤1h, corporate kinds daily.
  • Added
    POST /v2/webhooks is now the canonical create: a webhook is a trigger (scan / ticker / signal / event) plus delivery fields. The per-resource /subscribe endpoints remain as permanent shorthand — every door creates the identical object.
  • Added
    GET /v2/tickers/{ticker}/history/{interval} — true series history: up to 25 columns for one ticker, one flat row per step (1m/1h/1d), chronological, cursor-paged. The old /v2/tickers/{ticker}/history?asof= form (a point snapshot despite its name) keeps working forever and stays fully documented; GET /v2/tickers/{ticker}?asof= returns the identical response — existing integrations are unaffected.
  • Changed
    asof is now one uniform capability: the same staleness rule on every endpoint — a row must be within the serving tier's window (14 days for daily) or the response is empty/404 with last_available. Unlimited depth on every plan; history-series endpoints are unaffected and stay all-time.
  • Added
    Idempotency keys on every create endpoint: send Idempotency-Key: <unique string> and a retry within 24h replays the original response (Idempotency-Replayed: true) instead of creating a duplicate; concurrent duplicates get 409 idempotency_in_flight.
  • Added
    POST /v2/scan/explain — dry-run a scan without executing: validation, the compiled predicate after custom-signal expansion, resolved scope and asof tier, and the planner's cost/row estimate. Always responds 200; failures return { valid: false, stage, error, message }.
  • Added
    Previously-undocumented surfaces are now in the reference: PATCH /v2/webhooks/{id}, the /v2/devices family (mobile push registration), GET /v2/stream/usage, and scan's full=true.
v2.14.02026-07-20
  • Changed
    The Free plan now includes a monthly call quota of 10,000 calls per calendar month (UTC), resetting on the 1st. Every paid plan is unmetered — no monthly cap. Calls past the quota return 402 monthly_quota_exceeded with a resets_at timestamp; rejected requests (429s and quota 402s) never consume quota. Free-plan responses carry X-Quota-Limit, X-Quota-Remaining, and X-Quota-Reset headers.
v2.13.02026-07-18
  • Changed
    Custom signals are no longer a paid feature and are no longer capped. Authoring and consuming them both work on every plan, including Free, with no count limit. The custom_signals_tier_required (403) and custom_signal_limit_reached (403) errors are retired; they can no longer occur. Accounts that were locked out of their own custom signals after a downgrade can use them again.
  • Changed
    Scale is now capped at 1,000 webhooks, where it was previously unlimited. Webhooks and websocket streaming now ladder identically: 0 / 10 / 100 / 1,000 across Free / Hobby / Pro / Scale. Unlimited webhooks are available on Enterprise.
  • Added
    GET /v2/stream/usage returns your current websocket consumption — tickers, max_tickers, connections, max_connections. Streaming caps are pooled per ACCOUNT, not per API key: issuing additional keys does not grant additional capacity.
  • Added
    Two account-level ceilings are now documented: too_many_universes and too_many_custom_signals (both 400). These are anti-abuse guards, not plan limits — they are identical on every plan and upgrading does not raise them.
v2.12.02026-07-10
  • Changed
    Webhook cadence is no longer plan-gated — any webhook can use any cadence, regardless of plan. The cadence_above_plan_max (403) error is retired; it can no longer occur.
  • Changed
    The real-time cadence is now realtime (the default). It is evaluated on every data refresh (~1×/min), so a match is delivered within seconds of the snapshot that first contains it — no per-minute batching. 1m is a deprecated alias for realtime: it is still accepted on create/update and is normalized to realtime, which is what responses now return.
v2.11.02026-07-08
  • Changed
    Plans restructured around a new $0 Free tier, now the default on signup. All data is available on every plan, including Free: full universe, every signal, real-time data, history, asof, news, and analyst archives. Paid plans differ by rate limit, webhook count, and custom signal count. The 14-day trial is retired; cancelling returns an account to Free rather than revoking access.
v2.10.02026-06-30
  • Added
    Rules are now validated at creation. Every subscribe endpoint dry-runs your query and rejects an unrunnable rule (unknown column, bad syntax) with 400 invalid_query and the underlying message.
  • Added
    Optional fields on /v2/tickers/{t}/subscribe, /v2/signals/{s}/subscribe, and /v2/scan/subscribe — a comma-separated list of extra columns to include in each fired payload's match rows, beyond the standard set (ticker, name, asset_type, price, day_change_pct, market_cap). Mirrors fields on /v2/scan; each must be a real column or the subscription is rejected at creation.
v2.9.02026-06-29
  • Added
    GET /v2/analyst/events — per-event analyst rating history from a ~14-year archive: upgrades, downgrades, initiations, and price-target changes, each with the firm, analyst, new and previous rating, and new and previous price target. Filter by ticker/tickers (≤50), since/until, firm (case-insensitive), and action; results are newest-first and page with cursor. At least one filter is required. Scale and above — the live last_rating_* columns on /v2/tickers and the recent_* analyst flags on /v2/scan remain available on every plan. See /docs/endpoints/events/query#analyst.
  • Added
    tickerbot_list_analyst_events MCP tool wraps the endpoint above, so agents can pull analyst rating history in chat.
v2.8.02026-06-28
  • Added
    Webhook delivery channels. Every subscribe endpoint (/v2/tickers/{t}/subscribe, /v2/signals/{s}/subscribe, /v2/scan/subscribe) now takes a channel discriminator — webhook (signed POST to target_url), discord (an embed posted to a Discord channel), or in_app (dashboard-only). Omit it and we infer: webhook when target_url is set, discord when discord_url is set, otherwise in_app. See the Delivery channels guide at /docs/endpoints/webhooks/channels.
  • Added
    Discord delivery. Pass channel: "discord" plus a discord_url (a Discord incoming-webhook URL) and each fire posts a formatted embed — subscription name, composed query, and the first dozen matching tickers with price and day change. No HMAC: the URL is the credential, so it is stored masked and stripped from list/get responses, which expose channel_config_present: true instead. 429s honor Discord's Retry-After; other 4xxs are permanent failures; 5xx/network errors ride the standard retry ladder.
  • Changed
    POST /v2/webhooks/{id}/test is channel-aware — for a Discord subscription it posts a real-shape test embed (titled with a [TEST] prefix) and returns the inline outcome, same as the HTTPS test fire.
  • Changed
    The delivery channel is fixed at create time. PATCH /v2/webhooks/{id} still toggles a webhook subscription between POST-to-URL and in-app, but cannot switch to or from Discord — delete and re-subscribe to change channel.
v2.7.02026-06-27
  • Changed
    Subscribing no longer auto-fires a webhook.ping at your endpoint. One delivery shape — webhook.fired — so handler code only needs to handle one event, and the first payload your endpoint ever receives is identical to every future one. New webhooks ship in status: "active" immediately.
  • Added
    POST /v2/webhooks/{id}/test fires a real-shape POST to your target_url synchronously and returns the inline HTTP outcome (delivered, http_status, elapsed_ms, error). For URL targets the body has the same field set and HMAC signature as a real fire — webhook.fired for condition triggers, events.fired for event triggers — with an X-Tickerbot-Test: true header as the only marker. Test fires are one-shot: failures are recorded as permanent_failure and never enter the retry queue or trigger auto-disable on the parent webhook.
  • Added
    test_url field on subscribe responses points at the test endpoint above. The dashboard also surfaces a "Send test fire" button on the post-create modal and on the webhook detail page.
  • Removed
    webhook.ping event type. The pending_verification status is no longer emitted on new webhooks.
v2.6.02026-06-19
  • Added
    GET /v2/tickers/{ticker}/bars/{interval} — OHLCV bars at 1s, 1m, 5m, 15m, 30m, 1h, 1d. Single symbol or comma-separated bulk (response keyed by symbol). Paging via before + limit (with cursor/next_cursor as sugar); asof returns a single point-in-time bar. 1d/1h cover the full universe with full history; sub-hour covers the active universe and back-fills from the provider on first request. Available on every plan, all intervals.
  • Added
    1s (1-second) interval on the bars endpoint, served on demand: from our store when present, otherwise passed through from the provider in the same call. Second data is not bulk-backfilled — it accumulates as requested. Best paired with a tight before+limit window.
v2.5.02026-06-04
  • Added
    POST /v2/tickers/{ticker}/subscribe, POST /v2/signals/{signal}/subscribe, and POST /v2/scan/subscribe — subscribe to a webhook directly from the resource you want to watch. The new endpoints all return the same webhook record shape; /v2/webhooks becomes a pure registry for listing, inspecting, deleting, and re-enabling subscriptions.
  • Removed
    POST /v2/webhooks — replaced by the resource-level subscribe endpoints above. Existing webhooks created via the old path keep firing unchanged.
  • Removed
    /v2/rules — saved-bundle layer retired. Inline the q directly on /v2/scan or on a subscribe endpoint; reference a universe via ?universe=<slug> instead of bundling it.
  • Added
    ?asof= is now uniform across every read: /v2/tickers/{ticker}?asof=, /v2/signals/{signal}?asof=, /v2/scan?asof=. Returns the universe as it stood at the close of the requested day, sourced from signal_daily_state. _meta.frozen_fields lists columns that aren't historized (sector, industry, exchange, asset_type).
  • Changed
    Every paid plan now ships replayable history on every read, unlimited universes, and webhooks scaling by tier (Hobby 10 · Pro 100 · Scale unlimited). The Pro → Scale upgrade is content (news archive, custom signals).
  • Changed
    News archive (/v2/news/scan) moved to Scale and above (previously Pro). The live news_volume and news_volume_weighted_sentiment columns on /v2/tickers and /v2/scan remain available on every paid plan.
  • Changed
    Custom signals (POST/PATCH/DELETE /v2/signals/{name}) moved to Scale and above. The unified /v2/signals catalog remains readable on every plan.
  • Changed
    Webhook visibility is account-scoped: every API key on the same account sees the same webhook registry. Rotating a key no longer strands subscriptions.
v2.4.02026-06-02
  • Changed
    Free trial no longer requires a credit card. New signups are placed on Hobby for 14 days; an API key is minted from the dashboard checklist with no Stripe interaction. Add a payment method anytime to keep going past the trial.
  • Changed
    /onboarding retired. The dashboard is now the unified post-signup landing — trial countdown, account-status banner, and onboarding checklist all live there. Stripe Checkout success and cancel URLs now point back to /dashboard and /dashboard/billing.
  • Added
    402 trial_ended error code (was subscription_required) returned by /v2/* when a no-card trial has expired. Body message links to /dashboard/billing to add a payment method.
v2.3.02026-06-01
  • Added
    Custom (expression) signals — name a SQL WHERE-clause expression once, then reference it as a bare identifier in any predicate context (scan q, another custom signal's expr, webhook subscribe body). Compiles + inlines at create time; recursion is detected and capped at depth 5. CRUD: POST /v2/signals, GET /v2/signals (unified catalog of built-ins + your customs), PATCH/DELETE /v2/signals/{name}. Cascade-safe delete refuses with 409 signal_referenced (carries referencing_signals array) — pass ?force=true to override.
  • Added
    GET /v2/signals/{name}/{ticker}/events — occurrence records (start/end timestamps + start/end prices) for a single signal on a single ticker. State-style signals return windowed regions; event-style signals return point events. Drives the dashboard chart's flag-overlay rail.
  • Changed
    Hobby now includes full per-ticker history and historical scans (previously live-data only). Rate limit on Hobby raised from 60 to 600 req/min.
  • Changed
    The demo ticker (AAPL) now bypasses the plan top-N scope filter on every plan, so the public docs and the per-signal reference page render without auth on every tier.
v2.2.12026-05-26
  • Changed
    GET/POST /v2/news/scan replaces the original /v2/news + /v2/news/{id} pair. One SQL-style endpoint, two shapes — article rows by default, aggregate rollups when group_by is supplied. Auto-joins UNNEST(tickers) AS tk whenever any clause references the tk alias. "As-of" is just a WHERE filter on time_published; no separate parameter.
  • Changed
    News archive access now requires Pro or above (was Hobby). The two live news columns on the ticker table (news_volume, news_volume_weighted_sentiment) remain available on every paid plan via /v2/scan and /v2/tickers.
  • Added
    /v2/sandbox/news/scan — unauthenticated, IP-rate-limited mirror of the scan endpoint, capped at 50 rows.
v2.2.02026-05-25
  • Added
    GET /v2/news — paginated, filterable news feed. Articles indexed back to 2015, refreshed every 15 minutes. Filterable by tickers, topics, time range, min_relevance, min_sentiment/max_sentiment. Hobby and above; per-call cap 50/200/1000 by plan. (Superseded the next day by /v2/news/scan.)
  • Added
    GET /v2/news/{id} — fetch a single article by id. (Superseded the next day by /v2/news/scan.)
  • Added
    Two new fields on the ticker schema: news_volume (24-hour rolling count of mentions at relevance ≥ 0.6) and news_volume_weighted_sentiment (relevance-weighted average sentiment, attenuated by tanh(volume/15) so quiet tickers read near zero). Both refresh every 15 minutes. Queryable through /v2/scan and /v2/tickers.
  • Removed
    The four previously-stale news columns on ticker (latest_news_at, recent_news_count, highly_relevant_news_count, news_sentiment_volatility) have been removed. They were never reliably populated; the new two-field design above supersedes them.
v2.1.12026-05-18
  • Removed
    Free tier removed. Every plan (Hobby, Pro, Scale) now starts with a 14-day free trial; cancel anytime.
v2.1.02026-05-14
  • Added
    /v2/universes — create and manage named ticker lists. System universes top_10 and top_100 (rebalanced monthly by dollar volume) are available to every account.
  • Added
    /v2/rules — save a {q, universe_id?, order, dir, fields} bundle and reference it from /v2/scan?rule= or /v2/webhooks.
  • Added
    ?universe= parameter on /v2/scan, /v2/signals/{signal}, and /v2/tickers — scope queries to a system or owned universe.
  • Added
    ?asof= on /v2/scan — folds the historical scan into the main scan endpoint. /v2/scan/history remains as a backwards-compatible alias.
  • Added
    Webhook cadence field — pick 1m (real-time, the default), hourly, or nyse_open.
  • Added
    Webhook rule_id body field — subscribe to a saved rule instead of inlining q.
  • Changed
    Free and Hobby plans now auto-scope ticker queries to the plan top-N (10 / 100). Response carries _meta.scope describing what got applied.
  • Changed
    New pricing matrix: ticker scope, webhook cadence, max universes/rules/webhooks. See /pricing for the full grid.
v2.0.02026-05-13
  • Changed
    API base path moves from /v1 to /v2. v1 keeps working at its existing path for now; new integrations should use v2.
  • Added
    /v2/signals/{signal} lists tickers where a signal matches. Numeric signals take a ?condition= (e.g. >70); boolean flags are auto-detected.
  • Added
    /v2/signals/{signal}/{ticker}/history/{interval} returns per-signal time-series at the requested resolution (1d / 1h / 1m). Daily history covers all-time; minute history is two years for top-200 tickers.
  • Added
    /v2/scan/history?asof= snapshots the universe scan at any past date, as-of-that-day. Falls under the same SQL grammar as live /v2/scan.
  • Added
    /v2/tickers/{ticker}/history?asof= returns the wide ticker row as it stood on a past date, with quarterly fundamentals (assets, equity, EPS…) joined in by filing date.
  • Added
    /v2/tickers/{ticker}/events returns a unified event log: splits, dividends, analyst rating changes, all sorted newest-first with cursor pagination.
  • Changed
    v2 uses scanner-native column names everywhere — the legacy v1 docs vocabulary (day_change_pct, asset_type) is gone in favor of day_change_pc, type. The full set is documented on the schema page.
  • Changed
    Webhooks now live under /v2/webhooks with the same shape as /v1/webhooks. Existing v1 webhooks keep firing unchanged.
v1.1.02026-05-11
  • Added
    Free tier: live API key with no card on file. 10 req/min, 7 days of signal history, all query endpoints; no webhooks.
  • Added
    Scale tier ($199/mo): 1,000 req/min, 1-year history, up to 100 webhook subscriptions, Slack Connect support.
  • Changed
    Pricing: Pro replaces Core at $79/mo (down from $99), 500 req/min, 6-month history. Hobby now includes up to 3 webhook subscriptions.
  • Added
    /v1/signals/{ticker}/{signal} enforces per-plan history depth. Requests with from older than the plan ceiling return 400 history_window_exceeded with max_history_days + earliest_allowed_from in the response body.
  • Changed
    Subscription cancellation falls back to Free instead of revoking API keys — your integration keeps working at Free-tier limits. Webhooks over the new tier limit are auto-disabled (config preserved); resubscribe to re-enable.
  • Fixed
    GET /v1/signals/{ticker}/{signal} route now registered (previously returned 404 despite being documented).
v1.0.02026-05-01
  • Added
    Initial public release of the Tickerbot API. Four endpoints under /v1: tickers, signals, scan, webhooks.
  • Added
    GET /v1/tickers/{ticker} and bulk GET /v1/tickers?tickers=... return the full curated ticker object.
  • Added
    GET /v1/signals/{ticker}/{signal} returns time-series history: numeric bars, continuous-flag windows, or edge-flag triggers depending on the signal type.
  • Added
    GET/POST /v1/scan accepts a SQL WHERE clause and returns matching tickers.
  • Added
    POST /v1/webhooks creates a SQL-driven webhook that POSTs to your URL once per minute when new tickers enter the match set. State-change deduplication, HMAC-SHA256 signed deliveries, 5-attempt retry.
  • Added
    50+ boolean flags + ~50 numeric/string columns documented on the schema page.
  • Added
    Coverage: ~12,000 US-listed equities and the top 100 cryptocurrencies by market cap.