Crypto market data API. Put the market in view.

Read public prices, pairs, order books and recent trades, with supported streaming interfaces for live market updates.

Open public data reference ↗

Public market data

  1. 1. Currencies & pairs

    Find supported currency codes and the spot pairs represented by the reference.

  2. 2. Prices & order books

    Read available pair statistics and published bid and ask information.

  3. 3. Recent trades

    Retrieve the recent trade records exposed by the public routes.

  4. 4. Supported streams

    Use the Trading Gateway public ticker channel or the relevant authenticated and futures streams.

A market view With a defined scope.

Use public REST for spot market data and the supported Client API stream for futures. Trading Gateway feeds serve XBO’s interface and use separate access rules. A native spot WebSocket API remains in development.

  1. Spot prices, pairs, books and trades: public REST
  2. Futures market data: Client API streaming
  3. XBO interface feeds: separate Trading Gateway
  4. Authenticated UI streams: bearer/session credentials

Know what the feed provides.

Details for your next decision.

  • Do public REST requests need an API key?

    No. The documented public market-data routes are unauthenticated routes on the Client API. Private account functions on that API require authentication.

  • Which public data is available?

    Currencies, pairs, statistics, order books and recent trades are covered by the public REST reference. Select the fields and refresh behaviour your application needs.

  • What streaming is available?

    Client API streaming covers futures market data. XBO’s interface also uses Trading Gateway feeds, including an anonymous public ticker and authenticated streams. Those UI feeds are distinct from external Client API access; confirm the supported interface for your integration.

  • Is there a public historical candle or OHLCV endpoint?

    No public candle or OHLCV endpoint is offered in the current Client API catalogue. A wider native spot streaming service is still in development and should not be treated as a live historical-data source.

  • Are latency and availability guaranteed?

    No fixed latency, uptime or depth guarantee is made on this page. Agree any access, retention or redistribution requirements for your use case.

  • Can Client API keys authenticate Trading Gateway streams?

    No. Authenticated Trading Gateway streams require bearer/session credentials, rather than a Client API key and secret. The public ticker can be anonymous. Follow the access requirements for each interface.

Explore what else your business can do with crypto.

Explore the services that work alongside this one.