← Streaming data

Data API

Polymarket Sports WebSocket: game state alongside the market

Polymarket Sports WebSocket provides public game-state updates rather than order-book prices. Join its sporting context to Gamma game and market metadata.

Available on
API
Pricing
The sports feed is public and needs no API credentials. The reference lists no subscription charge.

Screenshots and interface

What is Polymarket Sports WebSocket?

The stream covers scores, current periods and live/ended states. A game may connect to several companion markets and props, so retain the game-to-contract mapping instead of treating a token price as the score.

Period and status formats depend on the sport, and status values are case-sensitive. The client must also maintain the heartbeat and reconcile state after a disconnect. Connection freshness and game completion need separate handling.

Who it is for

  • Building live sports market pages.
  • Watching game state alongside positions.
  • Adding updates to a dashboard using Gamma metadata.

Data and API methods

  • Public socket

    Connect to wss://sports-api.polymarket.com/ws without authentication.

  • Status changes

    Receive live and ended game states.

  • Scores and periods

    Update scores and sport-specific period displays.

  • Possession

    NFL and college-football updates include possession changes.

  • Game mapping

    Connect feed identity with game-linked discovery and companion markets.

  • Heartbeat

    Respond to server Ping messages to maintain the connection.

Integration tasks

Build a game panel

Resolve the game through Gamma, join stream updates and display score, period and status beside related contracts.

Recover a connection

Reconnect, reconcile current game state and resume updates. Distinguish a stale socket from a game that has ended.

Pricing and total cost

The sports feed is public and needs no API credentials. The reference lists no subscription charge.

API access and setup

  1. Find game and market identifiers through Gamma.
  2. Open the public sports WebSocket.
  3. Parse score, period and status for the specific sport.
  4. Reply Pong within 10 seconds; the server sends Ping every 5 seconds.
  5. Reconnect and reconcile state when the connection closes.

Useful links

What to check

  • Normalize periods separately for each sport.
  • Status values are case-sensitive.
  • Game-state data is separate from CLOB books and prices.
  • One game can have several markets and props.

A closer look

Ratings & reviews

Editorial rating
4.0/ 5
0 user reviews

Our take on Polymarket Sports WebSocket

A focused public stream provides useful game context. Clients must handle sport-specific states and keep game information distinct from market prices.

Assessment criteria
Task usefulness, documented scope, setup clarity, and access and cost transparency.
Assessment date
Documentation reviewed

Documentation-based assessment. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Related tools

Browse category

Frequently asked questions about Polymarket Sports WebSocket

Does it need a wallet or key?

No. The documented feed is public.

Where do I get order-book prices?

Use the CLOB market-data channel for outcome-token books and prices.

Can all sports share one period parser?

Use sport-specific normalization: quarters, innings and maps represent different states.