Ticker reference endpoints help discover stock tickers, ticker types, company details, and related tickers.
Read this page with Ticker Search, Stocks Data API, Stock Snapshots, Stock Trades and Quotes, and Stock Data Provider Evaluation.
List tickers
GET /v1/stocks/tickers/
curl "https://api.cutemarkets.com/v1/stocks/tickers/?market=stocks&active=true&limit=100" \
-H "Authorization: Bearer YOUR_API_KEY"
The ticker list is paginated. If next_url is present, request it as-is.
Ticker types
GET /v1/stocks/tickers/types/
curl "https://api.cutemarkets.com/v1/stocks/tickers/types/" \
-H "Authorization: Bearer YOUR_API_KEY"
Ticker detail
GET /v1/stocks/tickers/{ticker}/
curl "https://api.cutemarkets.com/v1/stocks/tickers/AAPL/?date=2026-05-06" \
-H "Authorization: Bearer YOUR_API_KEY"
Related tickers
GET /v1/stocks/tickers/{ticker}/related/
curl "https://api.cutemarkets.com/v1/stocks/tickers/AAPL/related/" \
-H "Authorization: Bearer YOUR_API_KEY"
Limits
Ticker reference endpoints default to limit=100 and clamp to limit=1000.
Reference workflow
Reference data answers identity questions before market data is requested. Use it to normalize symbols, validate that a ticker is active, inspect the market/category metadata, and discover related tickers. Do not use reference responses as a substitute for live snapshots, trades, quotes, or bars.
When a stock signal later becomes an options workflow, route from reference data into Options Expirations, Options Chain API, Stock and Options Data Join Workflow, and Market Hours, Timestamps, and Timezones. That preserves the distinction between symbol identity, market state, and option contract identity.
| Task | Endpoint | Product decision |
|---|---|---|
| Build a ticker picker | /v1/stocks/tickers/ | Filter by market, active, and pagination. |
| Confirm one ticker | /v1/stocks/tickers/{ticker}/ | Store name, market, locale, and primary exchange metadata. |
| Explain relationships | /v1/stocks/tickers/{ticker}/related/ | Use for related-company or paired-watchlist UI. |
| Discover valid types | /v1/stocks/tickers/types/ | Populate filters without hard-coding type labels. |
Pagination pattern
Ticker reference can produce large result sets. Start with a narrow filter when possible, use limit deliberately, and follow next_url as an opaque continuation URL. Avoid constructing page cursors yourself; they are signed so the server can preserve the exact query state.
curl "https://api.cutemarkets.com/v1/stocks/tickers/?active=true&market=stocks&limit=250" \
-H "Authorization: Bearer YOUR_API_KEY"
After a user selects a ticker, move to the endpoint that matches the workflow: snapshots for current state, trades or quotes for tick data, aggregates for bars, or options expirations when the next screen is an options chain.
Symbol lifecycle considerations
Reference data is where symbol lifecycle issues should be handled. A ticker can become inactive, change names, move exchanges, or become related to another symbol through corporate actions. If an application stores only the display name a user saw at selection time, it becomes difficult to explain later why a downstream market-data request changed or failed. Store the selected symbol, the reference response timestamp, and the metadata fields your application depends on.
The active filter is especially important for search and security-master workflows. Active symbols are usually what a user expects in a current trading interface. Historical research can still need inactive or renamed securities, but that should be an explicit mode so the UI does not mix current tradable symbols with old records.
Caching reference data
Ticker reference responses are slower-moving than trades or quotes, so they can usually be cached more aggressively. The cache should still have an expiration policy. A daily refresh is often enough for watchlist metadata, while onboarding flows and administrative symbol pickers can refresh on demand when a user searches.
Do not use stale reference data to decide whether a market-data endpoint is entitled or available. Reference data can tell you what the symbol is; plan access, quote availability, and historical lookback are still enforced by the endpoint that returns the market data.
Application patterns
- Security master: page through
/v1/stocks/tickers/with narrow filters and store normalized symbols. - Detail page: call
/v1/stocks/tickers/{ticker}/before rendering company metadata. - Related list: use related tickers to populate comparison cards or paired-watchlist suggestions.
- Options entry point: after selecting a stock ticker, call
/v1/tickers/expirations/{ticker}/before loading option contracts.
Keeping reference data separate from market data makes the system easier to debug. A symbol lookup problem should be fixed in the reference layer; a quote, trade, or aggregate problem should be investigated in the market-data layer with the relevant request id.
Reference-data implementation notes
Stock reference data protects the rest of the workflow from bad identifiers. Validate active status, ticker type, primary exchange, name, market, related tickers, and corporate-action context before requesting quotes, trades, bars, or option chains. Store the reference timestamp or cache version when research depends on historical symbol state.
Reference data also helps route errors cleanly inside applications. A missing ticker, inactive symbol, changed ticker, unsupported asset type, or index-versus-ETF confusion should produce a different message. Pair this page with Ticker Search, Corporate Actions and Adjusted Options, and Stocks REST Overview before building broad watchlists.