In-Play Odds - AnySport

Direction	code	Notes
Client subscribes	`20100`	`data` is required
Server subscribe ack	`20101`
Client unsubscribes	`21100`
Server unsubscribe ack	`21110`

Subscribes example

{
  "code": 20100,
  "trace": "live-odds-sub-001",
  "data": {
    "match_id": "1234567"
  }
}

For the shared data fields available on every subscribe request (api_key, match_id, league_id, country_id), see Message Format & Codes.

Push Envelope Fields (`odds_live_update`)

Field	Required	Type	Notes
`type`	Yes	string	Always `odds_live_update`
`data`	Yes	object	Single-match live odds payload
`timestamp`	Yes	string	Server push time

`data` Field Notes

Field	Always present?	Type	Notes
`type`	Usually	string	Generally `odds`
`match_id`	Usually	string	Match ID
`home_team`	Usually	string	Home team name
`away_team`	Usually	string	Away team name
`league`	May be empty	string	League name
`match_time`	May be empty	string	Kickoff time
`bookmaker`	May be empty	string	Bookmaker / odds source
`phase`	Usually	string	Always `live` for in-play odds
`main_market`	May be empty	string	Primary market type, e.g. `1X2`
`home_odd`	May be empty	string	Home win odds
`draw_odd`	May be empty	string	Draw odds
`away_odd`	May be empty	string	Away win odds
`markets_json`	May be empty	object/array	Additional market details
`source_updated_at`	May be empty	string	Upstream data source’s update time
`push_ts`	May be empty	string	Upstream push timestamp
`received_at`	May be empty	string	Time the server received the data

In-play odds response example

{
  "type": "odds_live_update",
  "data": {
    "type": "odds",
    "match_id": "1234567",
    "home_team": "Manchester United",
    "away_team": "Arsenal",
    "league": "Premier League",
    "match_time": "2026-07-13T15:00:00Z",
    "bookmaker": "bet365",
    "phase": "live",
    "main_market": "1X2",
    "home_odd": "2.10",
    "draw_odd": "3.40",
    "away_odd": "3.20",
    "markets_json": {},
    "source_updated_at": "2026-07-13T15:67:01Z",
    "push_ts": "2026-07-13T15:67:01.123Z",
    "received_at": "2026-07-13T15:67:01.200Z"
  },
  "timestamp": "2026-07-13T15:67:01.250Z"
}