Skip to main content

Odds360 Cricket

Odds360 cricket is designed to sit on top of the normal SportMicro cricket match feed:

  1. find the match in cricket.sportmicro.com
  2. request bookmaker-specific Odds360 prices for that match_id
  3. keep the match refreshed with live streams

Service URLs​

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

Two access patterns​

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

Supported cricket odd groups​

  • player
  • team
  • full-time

Odd group mapping​

  • player -> odds.player
  • team -> odds.team
  • full-time -> odds.fullTime

1. Discover the match in SportMicro​

Use the cricket data endpoints to obtain the match_id and basic metadata:

  • https://cricket.sportmicro.com/matches-live
  • https://cricket.sportmicro.com/matches-by-date
  • https://cricket.sportmicro.com/matches
  • https://cricket.sportmicro.com/leagues
  • https://cricket.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 cricket​

GET /bookmaker/{bookmakerId}

The response contains the bookmaker sports list.

3. Load the cricket match list with prices​

GET /bookmaker/{bookmakerId}/cricket/matches?page=0
GET /bookmaker/{bookmakerId}/cricket/matches?page=0&status=live
GET /bookmaker/{bookmakerId}/cricket/matches?page=0&league=IPL

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 cricket odds payload​

GET /bookmaker/{bookmakerId}/cricket/{matchId}

Important response shape:

{
  "matchId": 2450840,
  "sport": "cricket",
  "odds": {
    "player": {},
    "team": {},
    "fullTime": {}
  },
  "override": []
}

The frontend also loads:

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

5. Use the raw Odds360 REST service​

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

6. Subscribe to live updates​

Updates

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

Overrides

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

Dashboard subscriptions:

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

7. Optional manual overrides​

PATCH /bookmaker/{bookmakerId}/cricket/{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>/cricket/<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>/cricket/<match_id>/updates"
);
es.addEventListener("message", (ev) => console.log(JSON.parse(ev.data)));

Notes​

  • match_id should come from the cricket 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.