API Enterprise
Every listing in a region on a single date, with the full instrument-identity block.
Built for enterprise consumers: one call gives the universe a region request covers, the response is uncharged (no credits), and every row can be joined straight onto your own security master.
Available Data Points:
- Date: The specific date for which the data is retrieved (
YYYY-MM-DDformat). - Company: The name of the company issuing the security.
- Ticker: The ticker symbol associated with the security.
- Operating MIC: The operating Market Identifier Code of the security.
- MIC: The Market Identifier Code (MIC) for the traded security.
- ISIN: The International Securities Identification Number for the security.
- FIGI: The Financial Instrument Global Identifier.
- Share Class FIGI: The Financial Instrument Global Identifier for the share class.
- Ortex Company ID: Unique id for a company.
- Ortex Security ID: Unique id for a security issued by a company.
- Ortex Tradable item ID: Unique id for a listing of a security.
- Ortex Tradable item main indicator: Indicates if the trading item is the main trading item for the security.
- Tradable Item Currency: The currency of the tradable item.
- Exchange Country: The country location of the exchange.
Region and date
Use region to select the listings (a region name, an ISO-2 country code, or "ALL"; defaults to US) and date to select the day (defaults to today).
Which listings are returned
A listing is returned when it was listed on the date (today, when date is omitted) and has both a ticker and an exchange symbol, so every row can be named on the stock endpoints as /stock/{exchangeSymbol}/{ticker}/ or /stock/tid/{ortexTid}/. On a past date a listing delisted since is still returned, so a historical list is not survivorship-biased. The identifiers are each listing's current ones; ortexTid is the stable key across dates.
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]
