Tickers

Turn user input and market filters into normalized security records. Ticker resources connect exchange-qualified symbols, company identity, market classification, cross-reference identifiers, and stable public IDs.

Choose a ticker endpoint

Select discovery or direct retrieval based on what you already know.

Move from discovery to retrieval

Use search for names, ticker codes, and exchange-qualified symbols when the user's input can produce several candidates. After a user selects a result, store its id and use that stable tkr_ identifier for direct retrieval.

Use list when you need an exact exchange, security type, primary-listing status, listing status, or two-letter listing-country filter. Follow returned cursor URLs unchanged and keep sending the Bearer header on every request.

The retrieve route accepts a stable public ID, exchange-qualified symbol such as NASDAQ:AAPL, or FIGI. It does not accept a bare ticker, CIK, CUSIP, or ISIN because those values can map to several listings.

Understand ticker identity

symbol is exchange-qualified, while ticker is the local code. A secondary listing remains its own resource and points to the canonical listing through primary_symbol. Filter with is_primary=true when your application needs one primary listing per company.

Ticker resources can include CIK, CUSIP, ISIN, FIGI, currencies, listing status, market classification, and primary-symbol context. Fields use null when the value is unavailable.

Common use cases

Use ticker resources as the discovery layer for other v3 APIs.

• Ticker autocomplete. Power a search control that tolerates misspelled company names and returns ranked listing candidates for user selection.
• Security-universe construction. Build an exchange-specific or country-specific universe with exact list filters and cursor pagination.
• Stable identifier resolution. Resolve a selected listing to a stable tkr_ ID before retrieving company, price, or fundamental resources.
• Primary-listing selection. Distinguish primary listings from secondary exchange listings when an application needs one canonical security per company.
• Identifier mapping. Map FIGIs and exchange-qualified symbols to normalized ticker records with company identity and market classification context.
• Historical security research. Preserve delisted securities in research datasets instead of limiting every ticker universe to active listings.

Next steps

Discover or resolve a ticker, then use its stable identity with related APIs.

• Search tickers from user-entered text.
• List and filter the ticker catalog.
• Retrieve one exact ticker.
• Retrieve the canonical company profile.
• Load canonical exchange values.