Global equity coverage

Stocks

US & international equities via derived, non-exchange-sourced feeds. Quotes, trades, snapshots, and aggregates over REST and real-time WebSocket channels.

  • Live quotes & trades
  • Snapshots & OHLCV history
  • US & international markets
View API docsStart buildingDashboard

Feed capabilities

REST endpoints and WebSocket channels available in the stocks feed. Response shape is normalized across US and international symbols.

Quote & trade endpointsBid, ask and last via /stocks/quote and /stocks/trade/last/:symbol across US and international symbols.
OHLCV aggregatesDaily, hourly, minute-level bars via /stocks/agg where supported.
WebSocket channelsstocks.quotes and stocks.trades, same subscribe pattern as other asset classes.
Snapshot endpointComposed per-symbol response via /stocks/snapshot for initial data loads.

Inside the stocks feed

Field for field, the exact responses the API returns. What you see here is what production sends.

Latest quote

Best bid and ask with sizes from the aggregation layer, one call per equity symbol.

  • Top-of-book bid and ask with sizes
  • Millisecond timestamps on every response
  • Market-qualified symbols: US:AAPL, DE:BMW, JP:7203
  • Identical shape across every asset class
GET/stocks/quote/:symbol
{
  "symbol": "US:AAPL",
  "bid": 214.22,
  "ask": 214.25,
  "bid_size": 1200,
  "ask_size": 800,
  "timestamp": 1743512400000
}
GET/stocks/quote/:symbolLatest consolidated bid and askDocs
GET/stocks/trade/last/:symbolLast trade price and sizeDocs
GET/stocks/snapshot/:symbolQuote, last trade, prev close, and change in one responseDocs
GET/stocks/agg/:symbol/prevMost recent settled daily barDocs
GET/stocks/agg/:symbol/:multiplier/:timespan/:from/:toHistorical OHLCV range with paginationDocs
GET/stocks/symbolsSymbol discovery for the feedDocs
WSstocks.quotes · stocks.tradesStreaming quotes and trades by subscriptionDocs

Data quality

Benchmarked against a selected market reference.

US names against the NBBO, international names against a selected dealer.

Measured Sep 10, 2026, 14:24 to 14:49 UTC, one sample per second.

See the full Stocks benchmark

92.7%

US names within 1 bp of the NBBO midpoint

98.8%

Quote ranges overlap

230 ms

Source to platform p95

Typical use cases

Common ways teams put equity data to work.

Power charting

OHLCV aggregates for candlestick rendering; snapshot endpoints for quick intraday context displays.

Charts

Price alerts

Stream trades or quotes and evaluate threshold conditions in your own alert engine without constant polling.

Alerts

Live dashboards

Combine REST portfolio summaries with WebSocket live tiles, same client pattern as forex or crypto.

Dashboards

Backtest & research

Query symbols, pull historical bars, and cross-reference with forex or crypto from the same integration.

Research

Access model

Consistent account-level controls across all TickerLayer data feeds.

One integration model across every feed

Use the same API key, REST conventions, and WebSocket subscription flow across all TickerLayer data feeds.

  • Header-based REST authentication
  • Symbol-based WebSocket subscriptions
  • Account-level limits and package access
GETREST
GET /stocks/quote/US:AAPL
WSWebSocket, where available
{
  "action": "subscribe",
  "channels": ["stocks.quotes"],
  "symbols": ["US:AAPL"]
}
AuthAuthentication
REST:      x-api-key: YOUR_API_KEY
WebSocket: ?apiKey=YOUR_API_KEY  (upgrade URL)

Live pages

See the feed on a live page

Delayed price, chart and key figures for popular symbols, with the exact API calls that return them live.

View all symbols

Frequently asked questions

What is the TickerLayer Stocks Data Feed?

The Stocks Data Feed gives you API access to stock quotes, trades, snapshots, and symbol discovery through a consistent REST structure. It is a practical fit for dashboards, fintech apps, trading analytics, portfolio tools, and internal monitoring, anywhere you need stock data without building and maintaining your own ingestion pipeline.

Can I access US and international stock data?

Yes, depending on your plan and the available symbol list. Coverage spans US and international equities, and the stocks symbols endpoint shows exactly which instruments and market-qualified identifiers are supported. That matters when a similar-looking ticker exists in more than one region; the symbol endpoint removes the guesswork.

How are stock symbols handled?

Stocks use a market-qualified symbol format so the same code in different regions stays unambiguous. Rather than hardcoding naming rules, treat the symbol discovery endpoint as your source of truth for what is supported. This keeps search results, watchlists, portfolio holdings, and quote pages accurate as coverage changes.

Can I use REST and WebSocket for stocks?

Yes. REST handles quote lookups, snapshots, trades, and backend requests where you pull data on demand. WebSocket carries streaming quote and trade updates where available. You can lean on REST for request-based flows and add WebSocket for live market screens, all from the same platform.

What can I build with the Stocks API?

Common builds include watchlists, portfolio dashboards, research tools, pricing widgets, market overview pages, and internal analytics. Because responses share a consistent shape, wiring stock data into frontend components, backend services, or reporting jobs is straightforward, which is usually where most of the integration time goes.

Is the Stocks Data Feed suitable for production apps?

It is built for production use once you have validated coverage, freshness, limits, and plan access for your workflow. The data is intended for informational and analytical use, so regulated or order-routing systems should add their own validation, monitoring, and controls. As a rule, read response timestamps and handle stale or missing data gracefully.

Ready to integrate?

Start with the free tier, explore the docs, and connect via REST or WebSocket in minutes.

Start buildingDashboardStocks API reference