Skip to main content

Odds360 Esports

Odds360 esports is handled in the same way as the esports bookmaker flow in sportmicro-frontend:

  1. identify the match from the SportMicro esports feed
  2. request bookmaker-scoped Odds360 prices for that match_id
  3. subscribe to live refreshes for updates and overrides

Service URLs​

SportMicro esports data: https://esports.sportmicro.com/
Odds360 esports feed:   https://odds360.sportmicro.com/

Two access patterns​

  • Public Odds360 API: https://odds360.sportmicro.com/esports
  • Dashboard and bookmaker flow used by sportmicro-frontend: /bookmaker/{bookmakerId}/esports/...

Supported esports odd groups​

  • map
  • full-time

Odd group mapping​

  • map -> odds.map
  • full-time -> odds.fullTime

1. Discover the match in SportMicro​

Use the esports data endpoints to obtain the match_id and metadata:

  • https://esports.sportmicro.com/matches-live
  • https://esports.sportmicro.com/matches-by-date
  • https://esports.sportmicro.com/matches
  • https://esports.sportmicro.com/leagues
  • https://esports.sportmicro.com/classes

Important fields:

  • id or match_id
  • league_id
  • league_name
  • home_team_name
  • away_team_name
  • start_time
  • status_type

2. Confirm that the bookmaker can access esports​

GET /bookmaker/{bookmakerId}

The response contains the bookmaker sports list.

3. Load the esports match list with prices​

GET /bookmaker/{bookmakerId}/esports/matches?page=0
GET /bookmaker/{bookmakerId}/esports/matches?page=0&status=live
GET /bookmaker/{bookmakerId}/esports/matches?page=0&league=CS2

Available query parameters:

  • page
  • league
  • homeTeam
  • awayTeam
  • status with live or upcoming

Backend behavior:

  • page size is 100
  • postponed and finished matches are excluded
  • only matches with totalOdds > 0 are returned

4. Load the full esports odds payload​

GET /bookmaker/{bookmakerId}/esports/{matchId}

Important response shape:

{
  "matchId": 2450840,
  "sport": "esports",
  "odds": {
    "map": {},
    "fullTime": {}
  },
  "override": []
}

The frontend also loads:

GET /bookmaker/{bookmakerId}/esports/{matchId}/verify

5. Use the raw Odds360 REST service​

GET https://odds360.sportmicro.com/esports
GET https://odds360.sportmicro.com/esports-history
GET https://odds360.sportmicro.com/esports-classes
GET https://odds360.sportmicro.com/esports-leagues

6. Subscribe to live updates​

Updates

wss://odds360.sportmicro.com/live/{bookmaker_id}/esports/{match_id}/updates
https://odds360.sportmicro.com/live/{bookmaker_id}/esports/{match_id}/updates

Overrides

wss://odds360.sportmicro.com/live/{bookmaker_id}/esports/{match_id}/overrides
https://odds360.sportmicro.com/live/{bookmaker_id}/esports/{match_id}/overrides

Dashboard subscriptions:

GET /bookmaker/{bookmakerId}/esports/{matchId}/updates
GET /bookmaker/{bookmakerId}/esports/{matchId}/overrides

7. Optional manual overrides​

PATCH /bookmaker/{bookmakerId}/esports/{matchId}/{oddType}

Typical body:

{
  "oddKey": "market_name#outcome_key",
  "oddValue": 1.85,
  "durationSeconds": 3600,
  "suspended": false
}

WebSocket example​

const ws = new WebSocket(
  "wss://odds360.sportmicro.com/live/<bookmaker_id>/esports/<match_id>/updates"
);
ws.addEventListener("message", (ev) => console.log(JSON.parse(ev.data)));

SSE example​

const es = new EventSource(
  "https://odds360.sportmicro.com/live/<bookmaker_id>/esports/<match_id>/updates"
);
es.addEventListener("message", (ev) => console.log(JSON.parse(ev.data)));

Notes​

  • match_id should come from the esports SportMicro match feed.
  • bookmaker_id is the UUID assigned to your Odds360 bookmaker.
  • /bookmaker/... routes are the authenticated dashboard routes used by sportmicro-frontend.
  • https://odds360.sportmicro.com/... routes are the public Odds360 API routes.
  • The frontend only shows odd groups that are present and non-empty for the match.