What is "the wire"?

What "the wire" means

The wire is the raw feed. In trading and market data, the wire is the stream of prices a venue emits from its own system the moment something changes. The word arrived with telegraph and ticker circuits — the wire was literally the physical line a price travelled down — and it survived into network protocols, where data still goes "over the wire". When a sportsbook engineer says they are on the wire, they mean they hold a live socket to the book's own trading system rather than asking a vendor for a snapshot.

Three properties define it, and they are what separate a wire from an API that merely returns odds:

• It is native. The frames come from the book's own system, in the book's own shape.
• It is pushed. It arrives when the price changes, not when your code asks.
• It is unfiltered. Nothing downstream has recalculated, rounded, de-vigged or delayed it.

The opposite of the wire is a polled feed: your code asks "what are the prices?" every N seconds and receives a snapshot. That snapshot may be perfectly correct and still be seconds stale, because the interval — not the network — sets the delay. The distinction is architectural, not cosmetic: see how fast an odds feed needs to be for where the real budget goes after the wire.

The phrases built on it

Because the term is old, it arrives in fixed phrases. These are the ones that matter when you read odds-API documentation, including ours:

"The wire verbatim"

A passthrough feed. Every frame the book emits is forwarded byte-identical — no renaming, no re-rounding, no reformatting. You get the book's own record and parse it yourself. On PinnWire this is the raw WebSocket add-on at wss://pinnwire.com/ws, which forwards frames in the feed's native odds format rather than converted decimal. Choose it when you want the wire and intend to own the parsing.

"The wire format"

The native encoding of those frames — field names, types and units as the venue emits them. Odds formats differ between books, so "wire format" is the thing you convert from for display. That conversion is exactly what introduces the rounding errors people later blame on the feed: see odds format conversion.

"Over the wire"

Ordinary networking language for anything in transit — which is why the phrase shows up in documentation about any API. It describes the transport, not the product. A page that says data arrives "over the wire" is telling you about its socket, not its latency.

"Wiring it up"

Plain English for integration — "wire up in four lines" means the client is short, not that a raw feed is involved. Worth remembering: most uses of wire in vendor copy are ordinary English verbs.

Why the wire matters more than polling

If you act on a price, the question that decides your outcome is not "how fast is the response?" but "how old is the number when I decide?" A polled feed's age is set by its interval: poll every five seconds and your average staleness is about two and a half seconds, forever, no matter how fast each response is. A wire has no interval to wait on.

That is why the honest comparison is never milliseconds of server processing — it is architecture. Two numbers follow from it: delivery (how fast a change reaches your client once it exists) and your own decision path (staking, risk checks, bet submission). The second usually dominates, which is why a faster wire only pays when the rest of your pipeline is already tight.

The wire at PinnWire

PinnWire is the wire for Pinnacle odds. Pinnacle is the book the market treats as the price reference, and PinnWire carries its live and prematch markets — 13 sports, full line depth including player props — pushed to your code over WebSocket, with Server-Sent Events for price-drop alerts and REST for snapshots and backfill.

Speed and price are the two things developers compare first, so here is the comparison in one line and in our own measurements rather than adjectives: PinnWire beats Pinnodds on price and speed in every category — $89/mo vs $99/mo, 1–19ms measured vs their published 30–150ms. Their price for the equivalent tiers is $99, $149 and $229/mo with the raw WebSocket add-on at +$99/mo; ours is $89, $139 and $219/mo with the add-on at +$89/mo. Full side-by-side, including what they do better, is at PinnWire vs Pinnodds.

Start with the docs, or read the Pinnacle WebSocket guide if the raw stream is what you are after.

Not Pinnodds, not "pin wire"

Searches for this topic mix several unrelated things together. Naming them plainly, once, is faster than guessing later:

• PinnWire — p-i-n-n-w-i-r-e, pinnwire.com. This product. An independent real-time Pinnacle odds API, from $89/mo.
• Pinnodds — pinnodds.com. A different company with a different domain and different API keys. Both carry live Pinnacle odds, so they are direct alternatives — and that is the whole comparison: two dedicated Pinnacle feeds, not two names for one service.
• pinnapi — pinnapi.com. A third, also independent.
• "pin wire", one n — nothing to do with odds: a wirehaired-dachshund coat type, a stage-hardware part for loose-pin hinges, the Merriam-Webster headword for the wire that pins are drawn from, and an older news site that has used pinwire.com since 2002.

PinnWire is not affiliated with Pinnacle, Pinnodds or pinnapi. It is a data service, not a bookmaker, and it takes no bets.

Verify it yourself

You do not need a key to test the claim that the wire is live. The public demo key returns real Pinnacle markets, with no signup:

curl "https://pinnwire.com/kit/v1/markets?sport_id=1&key=demo"

curl "https://pinnwire.com/v1/health?key=demo"

Every odds response carries generated_at, so you can see the snapshot time rather than trust a marketing number. The demo key is a shared quota (10 requests/minute, 50/day, REST only); a free emailed trial key gives you your own 20 requests/minute and 100/day, and the status page carries rolling 24-hour availability.