Real-time crypto data

Crypto

Spot-style crypto pairs with the full REST surface, quotes, trades, snapshots, aggregates, and real-time WebSocket channels when streaming is available.

  • Live prices & trades
  • 24/7 streaming feed
  • Snapshots & OHLCV history

Feed capabilities

Endpoint and channel coverage for the crypto feed. Field availability depends on your account package and enabled symbols.

Quote & trade endpointsBid and ask via /crypto/quote, last execution via /crypto/trade/last.
OHLCV aggregatesBucketed bars via /crypto/agg, configurable time ranges.
WebSocket channelscrypto.quotes and crypto.trades, full real-time push.
Snapshot endpointComposed multi-field view per symbol for initial loads.

Inside the crypto 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 crypto symbol.

  • Top-of-book bid and ask with sizes
  • Millisecond timestamps on every response
  • Plain pair symbols: BTCUSD, ETHUSD
  • Identical shape across every asset class
GET/crypto/quote/:symbol
{
  "symbol": "BTCUSD",
  "bid": 84210.12,
  "ask": 84210.45,
  "bid_size": 1.2,
  "ask_size": 0.8,
  "timestamp": 1743512400000
}
GET/crypto/quote/:symbolLatest consolidated bid and askDocs
GET/crypto/trade/last/:symbolLast trade price and sizeDocs
GET/crypto/snapshot/:symbolQuote, last trade, prev close, and change in one responseDocs
GET/crypto/agg/:symbol/prevMost recent settled daily barDocs
GET/crypto/agg/:symbol/:multiplier/:timespan/:from/:toHistorical OHLCV range with paginationDocs
GET/crypto/symbolsSymbol discovery for the feedDocs
WScrypto.quotes · crypto.tradesStreaming quotes and trades by subscriptionDocs

Data quality

Benchmarked against a selected market reference.

Median of up to three regulated fiat-USD venues outside the aggregation.

Measured Sep 10, 2026, 08:45 to 09:10 UTC, one sample per second.

See the full Crypto benchmark

3.15 bp

Price fidelity

0.76 bp

Tracking after basis

4.91 bp

Tail deviation p95

Typical use cases

Crypto is often the first stream teams integrate before expanding to stocks or forex.

Power charting

OHLCV aggregates for candlestick rendering and volatility views; quote snapshots for tight bid/ask displays.

Charts

Real-time alerts

Subscribe to trade prints and quote updates for threshold alerting without polling REST continuously.

Alerts

Live dashboards

Combine crypto live tiles with stocks or forex using the same WebSocket subscribe protocol.

Dashboards

Backtest & research

Portable symbol format fits configs and cross-asset correlation studies. Pull history with the same key.

Research

Access model

Same API key and limit philosophy across every TickerLayer data feed.

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 /crypto/quote/BTCUSD
WSWebSocket
{
  "action": "subscribe",
  "channels": ["crypto.quotes"],
  "symbols": ["BTCUSD"]
}
AuthAuthentication
REST:      x-api-key: YOUR_API_KEY
WebSocket: ?apiKey=YOUR_API_KEY  (upgrade URL)

Frequently asked questions

What is the TickerLayer Crypto Data Feed?

The Crypto Data Feed offers REST and WebSocket access to supported digital asset pairs. It fits crypto dashboards, portfolio tools, trading analytics, alerting systems, and internal monitoring, anywhere you want fast crypto market context without running your own streaming infrastructure.

Which crypto pairs can I access?

The feed covers the major pairs and expands based on demand. Use the crypto symbols endpoint to pull the current list of supported pairs, display names, and integration-ready symbols, so your app stays in step with real coverage instead of a static list that goes stale.

Can I stream crypto market data?

Yes. WebSocket channels carry quote and trade-style updates where available, and REST sits alongside them for snapshots, initial page loads, fallbacks, and request-based work. That combination covers everything from live price cards and watchlists to backend monitoring services.

Is the Crypto API easy to integrate?

Yes. Simple routes, clear JSON, and copy-pasteable examples mean you can test in minutes. It works equally well for a quick prototype and a production dashboard, with the common integration path kept obvious so you are not reverse-engineering the API to get started.

How should developers handle crypto data freshness?

Crypto moves fast, so always read response timestamps, handle stale values safely, and plan for network or market interruptions. The structured responses make those checks easy, and in production you should pair them with sensible loading and error states, retries, and monitoring so users always see trustworthy prices.

What can I build with the Crypto Data Feed?

Common builds include price trackers, live dashboards, portfolio views, alerting tools, market overview pages, and multi-asset fintech products. Reach for WebSocket when the experience is live and REST for controlled backend requests and initial loads. The same feed scales from a weekend prototype to a full product.

Ready to integrate?

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