Skip to main content
Bravado’s Market Data layer streams realtime prediction-market data over WebSockets, so you consume live trades and order books through Bravado infrastructure instead of connecting to each venue’s socket yourself. Two feeds are available today, both served from wss://partner-api.bravadotrade.com:

Live Trades

A realtime stream of fills across every market — no filter and no allowlist — each already enriched server-side with the trader’s name and wallet address.

Order Books

Live order-book snapshots and incremental updates for any outcome token, plus last-trade price and best bid/ask, multiplexed over one socket.
Coverage today is Polymarket. Both feeds currently source from Polymarket, the largest prediction market by volume. The wire format is designed to extend to additional venues as coverage grows, see Supported Prediction Markets.

​
Why stream through Bravado

The venue’s own socket is public, so this is not about access. It is about not rebuilding the same plumbing every prediction-market application needs.

​
What you can build

  • Live tickers and tapes. Render a running feed of fills across the market, no polling.
  • Depth and price displays. Drive an order-book widget or a best bid/ask readout straight from the socket.
  • Signal and discovery. Watch flow across every market and react to it in realtime.
  • Enriched activity. Every trade arrives with the trader’s wallet, so you can cross-reference Trader Data (PnL, positions, history) for the wallets you see trading.

​
Feeds

The market-data streams are public today, no API key or signature is required to connect. This matches the access tier of the underlying venue’s public market feed. Authentication and per-partner metering may be introduced later, so build your client to read a token from configuration even if it does not send one yet.

​
Health and diagnostics

Each feed exposes a plain HTTP status endpoint you can poll from a health check or dashboard:
The trade-feed status reports whether the upstream source is connected, how many trades it has emitted, the size of the recent buffer, and the current connected-client count.