Ticker Changes

Complete symbol-change history for any current or former ticker, plus the latest ticker established by that history.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Overview

Given any current or former ticker, returns the complete known symbol-change history for that security and the latest ticker established by that history. Every ticker in a chain resolves to the same history and the same current_ticker, so you can search with a symbol from years ago or with today's symbol. Search is case-insensitive and whitespace is trimmed.

When to use

  • Mapping an old ticker in a backtest, watchlist or filing archive to the symbol it trades under today.
  • Showing a dated "formerly known as" trail on a company profile.
  • Detecting whether a ticker you hold has ever been reassigned or renamed.

Key parameters

  • ticker (required) — current or former symbol.

Response highlights

  • query_ticker — the normalized symbol you searched.
  • has_changes — false when no eligible change event involves the symbol. This only means no change is on record; it does not say whether the ticker is valid or active.
  • current_ticker — the latest ticker established by the change history. It does not assert that the security is currently listed or trading. null when has_changes is false.
  • history — ordered array of { old_ticker, new_ticker, effective_date } events, earliest first.

Notes

  • Only effective, confirmed events are included. Future-dated events do not change current_ticker until their effective date.
  • Ticker symbols are recycled between unrelated companies. When the ledger cannot safely tell which company a symbol refers to (for example the same symbol was used by two issuers, or two changes compete for the same symbol), the endpoint returns 409 Conflict with error.code = "ambiguous_ticker_lineage" rather than guessing. error.details.reason says why and error.details.tickers lists the symbols involved.
  • Supersedes the deprecated Historical Tickers endpoint.
Query Params
string
required
length between 1 and 6
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json