Live Trades WebSocket

For API integrations with Console usage and credit tracking, connect to wss://partner-api.bravadotrade.com/stream/polymarket/partner/trades using a Market Data key with stream.read and HMAC authentication. The server sends recent history, then every new trade across Polymarket markets. No subscription message is needed. The legacy Terminal /trade-feed/ws route has a separate access contract. New Console integrations must use the authenticated route above; adding an API key header to a different route does not select this usage-accounted feed.

Coverage today is Polymarket. The feed carries every trade on every market, not a selection of the active ones, and the rate varies with market activity — on the order of tens of trades per second (samples measured 20–50/s). Size your buffers and your UI for the whole hose, and filter client-side for the markets you care about. To follow a specific market’s book instead, use the Order Books feed.

Connect with usage tracking

Your organisation needs an eligible paid plan with WebSockets access. Keep the secret on your server; browser-native WebSocket clients cannot set HMAC headers. Create a Market Data credential in Console. Save its key and secret locally as BRAVADO_API_KEY and BRAVADO_API_SECRET.

Node.js

import WebSocket from "ws";
import { createHash, createHmac } from "node:crypto";

const path = "/stream/polymarket/partner/trades";
const timestamp = String(Date.now());
const payload = [timestamp, "GET", path, createHash("sha256").update("").digest("hex")].join("\n");
const signature = createHmac("sha256", process.env.BRAVADO_API_SECRET).update(payload).digest("hex");
const ws = new WebSocket(`wss://partner-api.bravadotrade.com${path}`, {
  headers: {
    "X-BRAVADO-API-KEY": process.env.BRAVADO_API_KEY,
    "X-BRAVADO-TIMESTAMP": timestamp,
    "X-BRAVADO-SIGNATURE": signature,
  },
});
ws.on("message", data => console.log(JSON.parse(data.toString())));
ws.on("error", error => console.error(error.message));
// Generate a fresh timestamp and signature for every reconnect.

Snapshot and trade payloads use WebSocket credits for enrolled organisations: 1 credit per 100,000 uncompressed UTF-8 bytes. Heartbeats and errors are not charged. Usage updates during an open connection; allow about a minute for batching, then refresh Console. The authenticated route sends heartbeat pings; Node’s ws client responds automatically.

Frames

Every message is a JSON object with a type field.

`snapshot`

Sent once, immediately on connect, so the feed does not start empty. It carries the last 200 trades as an array, newest first. The buffer is a fixed-count ring, not a time window. At the rates we have measured (20–50 trades per second) 200 trades is roughly four to ten seconds of history, and less than that when the market is busier — nowhere near thirty seconds, and not a fixed span you can rely on.

{
  "type": "snapshot",
  "trades": [ /* array of trade objects, see below */ ]
}

`trade`

Sent for every new fill after the snapshot.

{
  "type": "trade",
  "trade": {
    "id": "33339798372916037220786136133406478491116150628220441951753426683441228279665-1788624812-223432",
    "eventTitle": "Counter-Strike: Spirit vs Team Falcons - Map 2 Winner",
    "marketQuestion": "Counter-Strike: Spirit vs Team Falcons - Map 2 Winner",
    "outcome": "Spirit",
    "side": "SELL",
    "price": 0.999,
    "priceCents": 100,
    "size": 5.37,
    "amount": 5.36463,
    "timestamp": 1788624830000,
    "assetId": "61368774849738226433217302604163725833749767729515136801666479828182608187817",
    "conditionId": "0xf86b33b82a0e0b44d2c30c3264e2ed9f95ebfc4d98275d124f69c77d3fa68bb7",
    "eventSlug": "cs2-ts7-fal2-2026-09-05",
    "eventImage": "https://polymarket-upload.s3.us-east-2.amazonaws.com/counter-strike-image.png",
    "trader": "0xd93461E85B794F0a2fA3a1E9390681db1dF8ab75",
    "traderName": "Goodluck88888888",
    "traderImage": "https://polymarket-upload.s3.us-east-2.amazonaws.com/profile-image.png",
    "transactionHash": "0xdfdd21ca739637b2135de5914e72ee93e9b5ef2b2f443e978b96df75839f0ea2"
  }
}

The trade object in a trade frame and every element of the snapshot array share the same shape:

Field	Type	Description
`id`	string	Per-process identifier for the fill: two clients on the same instance see the same `id`, two instances do not. Not stable across restarts or instances — do not dedupe on it, see below.
`eventTitle`	string	Human-readable event title. May be empty if not yet resolved server-side.
`marketQuestion`	string	The market question. May be empty, on the same rows where `eventTitle` is.
`outcome`	string	The outcome traded, for example `"Yes"`, `"No"`, or a named outcome.
`side`	string	`"BUY"` or `"SELL"`.
`price`	number	Fill price as a decimal probability between 0 and 1.
`priceCents`	number	`price` rounded to whole cents, convenience field.
`size`	number	Number of outcome tokens filled.
`amount`	number	Notional value of the fill, `price × size`.
`timestamp`	number	Fill time in Unix milliseconds.
`assetId`	string	Outcome token ID. Use this to subscribe on the Order Books feed.
`conditionId`	string	Market condition ID. May be empty.
`eventSlug`	string	URL slug for the event. Optional.
`eventImage`	string	Event image URL. Optional.
`trader`	string	The trader’s wallet address.
`traderName`	string	Display name or pseudonym for the wallet. May be empty when the trader has no profile name.
`traderImage`	string	Profile image URL. Optional.
`transactionHash`	string	Polygon transaction hash for the fill. The semantic key: dedupe on this. Optional in the schema, but present on every trade we have observed.

assetId links the two feeds. Watch the trade stream to discover which outcome tokens are active right now, then pass those IDs to the Order Books feed to see depth for them. And trader links Market Data to Data API: take a wallet you see filling and pull its PnL, positions, and history.

Keep-alive and reconnect

The authenticated route sends heartbeat pings; clients must respond with protocol pongs (most libraries do this automatically). This trade route does not accept subscription commands. If the socket drops, reconnect to receive a fresh snapshot; authenticated reconnects require a fresh timestamp and signature. Dedupe against trades already on screen using transactionHash, not id. id is built from a counter that lives in the serving process: it restarts from zero when the process does, and two instances give the same fill different ids. transactionHash identifies the fill itself.

Health

curl https://partner-api.bravadotrade.com/trade-feed/status

Returns whether the upstream source is connected, total trades emitted, recent-buffer size, and connected-client count.

Order Books WebSocket, live depth for a specific asset.
Market Data overview.
Data API, enrich the wallets you see trading.

Market Data

Feeds

UMA resolution

Mempool Fills

Live Trades WebSocket

Connect with usage tracking

Frames

`snapshot`

`trade`

Keep-alive and reconnect

Health

​Connect with usage tracking

​Frames

​snapshot

​trade

​Keep-alive and reconnect

​Health

​Related

Connect with usage tracking

Frames

`snapshot`

`trade`

Keep-alive and reconnect

Health

Related