Overview - AnySport

1. Overview

Item	Details
Protocol	WebSocket (JSON text frames)
Sport	Football (soccer) only, for now
Path	`/v1/ws/live`
Production endpoint	`wss://data.anysport.io/v1/ws/live`

Plan required:

Plan	Fee
Pro Max	$399 / mo

Available data products:

Product	Subscribe code	Subscribe ack code	Unsubscribe code	Unsubscribe ack code	Push `type`
Live Match Stats	`20000`	`20001`	`21000`	`21010`	`situation_update`
Score	`20200`	`20201`	`21200`	`21210`	`score_update`
In-Play Odds	`20100`	`20101`	`21100`	`21110`	`odds_live_update`
Pre-match Odds	`20300`	`20301`	`21300`	`21310`	`odds_prematch_update`

No data is pushed automatically after a successful handshake — you need to send a subscribe message and get an ack before you’ll start receiving pushes. A single connection can subscribe to multiple products at once.

Field requirement conventions used throughout these docs:

Marker	Meaning
Required	Request fails if this field is missing
Conditionally required	Required only when a certain condition is met (see field notes)
Optional	Can be omitted; omitting it usually means “no filter” or the field may come back empty

2. Establishing the Connection

2.1 Handshake URL

Handshake URL

wss://data.anysport.io/v1/ws/live?api_key={YOUR_API_KEY}&business=soccer

Param	Required	Type	Notes
`api_key`	Conditionally required	string	Your API key. Can be passed in the URL, or in the subscribe message’s `data.api_key` field. At least one of the two is required.
`business`	Required	string	Sport type. Currently only `soccer` is supported.

Filter conditions (league_id / country_id / match_id) belong in the subscribe message’s data object, don’t put them in the URL.

2.2 Handshake Success Response

Field	Required	Type	Notes
`type`	Yes	string	Always `connected`
`message`	Yes	string	Human-readable message
`timestamp`	Yes	string	ISO-8601 timestamp

Handshake success response example

{
  "type": "connected",
  "message": "WebSocket connected. Send subscribe message to receive data.",
  "timestamp": "2026-07-13T08:00:00.000Z"
}

At this point the connection is live, but no business data is flowing yet. The handshake itself can also be rejected at the HTTP layer, for example:

401 / 403: invalid API key
429: too many concurrent connections, or your account is temporarily throttled

3. Full Sequence Diagram

The diagram below shows a full connection lifecycle: handshake → subscribe to two products → receive pushes → heartbeat → unsubscribe. Next: see Heartbeat & Keep-Alive for how to keep this connection open, and Message Format & Codes for the full request/response schema.

​1. Overview

​2. Establishing the Connection

​2.1 Handshake URL

​2.2 Handshake Success Response

​3. Full Sequence Diagram

1. Overview

2. Establishing the Connection

2.1 Handshake URL

2.2 Handshake Success Response

3. Full Sequence Diagram