Pinnacle WebSocket API
real-time odds in milliseconds.

Why WebSocket beats REST polling

Polling a REST endpoint means you only see a price after your next request — and you burn rate limit doing it. A WebSocket keeps one connection open and pushes every change the moment Pinnacle's broker emits it, so fast-moving lines and drops reach you first.

How it works

Connect to wss://pinnodds.com/ws/feed with your API key, subscribe to the sports you care about, and receive a snapshot of current state followed by a live stream of price deltas. A heartbeat keeps the socket alive; reconnect and you get a fresh snapshot.

// Node.js — connect, subscribe, receive live Pinnacle odds
import WebSocket from "ws";

// perMessageDeflate: true compresses live frames ~5x — strongly recommended
const ws = new WebSocket("wss://pinnodds.com/ws/feed?key=YOUR_KEY", { perMessageDeflate: true });

ws.on("open", () => {
  // subscribe to soccer (1) and basketball (4), live stream
  ws.send(JSON.stringify({ type: "subscribe", streams: ["live"], sport_ids: [1, 4] }));
});

ws.on("message", (buf) => {
  const msg = JSON.parse(buf);
  if (msg.type === "snapshot") console.log("state:", msg.events.length, "events");
  if (msg.type === "live")     console.log(msg.rec.id, msg.rec.markets); // price update
});

Enable compression. Turn on permessage-deflate on your client — live frames are compressed roughly 5×. This is essential for high-volume or geographically distant clients: without it, a burst of updates can exceed a single connection's throughput and queue up, so frames arrive with a delayed timestamp. Browsers negotiate it automatically; in Node's ws pass { perMessageDeflate: true }; Python's websockets and Go's gorilla/websocket support it too. Same URL, same JSON — your client decompresses transparently.

Full, copy-paste clients in Node, Python, Go and PHP — plus the exact frame schema and auth — are in the WebSocket documentation.

What you get

Frequently asked questions