API Enterprise

See every ticker a listing has traded under and every venue it has traded on, with the dates each combination held. Tickers get reused and listings move between exchanges, so the same symbol can name different companies in different years; this endpoint tells you which one you are looking at and what it was called before.

One row is returned per period over which both the ticker and the venue were unchanged, so a rename or an exchange move starts a new row and nothing else does. Rows carry their real dates: from_date is the day the ticker was adopted on that venue even when that is before your requested window, and to_date is null while the row still applies. Your window selects which rows are returned (any row that overlaps it), it does not re-date them.

The from_date you pass also decides which listing you get, because a ticker can have belonged to different companies over time: US/FB with a 2019 from_date is Meta's listing, and the history returned is Meta's. To ask for a specific listing regardless of what it is called today, identify it by ORTEX id instead, for example stock/tid/6696628/ticker_history. On this endpoint from_date and to_date are required on every path, including tid: state a wide window to read the listing's whole history.

This is the history of one listing. A company with several listings has a history per listing; when you identify the stock by security id, company id or ISIN you get its primary listing as at from_date. ISIN changes are not part of this history because an ISIN belongs to the security rather than to the listing; use the isin_history endpoint.

Available Data Points:

• From Date: The first date this ticker and venue combination applied (YYYY-MM-DD).
• To Date: The last date it applied, or null while it still does.
• Ticker: The ticker the listing traded under.
• Exchange Symbol: The ORTEX exchange symbol of the venue it traded on.
• MIC: The venue's segment MIC.
• Operating MIC: The venue's operating MIC.
• Exchange Country: The ISO-2 country code of the venue.

Try it out! You can test the API with the trial key TEST. Simply include it in your request headers; either here, or add the header "Ortex-Api-Key": "TEST" to your http request.

Trial key restrictions: Trial keys may be limited to a specific date range and set of regions. Requests outside the allowed regions or entirely outside the allowed date range are rejected; a date window that partially overlaps the allowed range is trimmed to it, reported in meta.restriction.

Get full access! Contact [email protected]