Skip to main content

Odds360 Volleyball

Odds360 volleyball is consumed in the same way as the volleyball bookmaker pages in sportmicro-frontend:

  1. find the match in the SportMicro volleyball feed
  2. request bookmaker-specific Odds360 prices for that match_id
  3. keep the match updated through live subscriptions

Service URLs

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

Two access patterns

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

Supported volleyball odd groups

  • set-time
  • half-time
  • full-time

Odd group mapping

  • set-time -> odds.setTime
  • half-time -> odds.halfTime
  • full-time -> odds.fullTime

1. Discover the match in SportMicro

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

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

GET /bookmaker/{bookmakerId}

The response contains the bookmaker sports list.

3. Load the volleyball match list with prices

GET /bookmaker/{bookmakerId}/volleyball/matches?page=0
GET /bookmaker/{bookmakerId}/volleyball/matches?page=0&status=live
GET /bookmaker/{bookmakerId}/volleyball/matches?page=0&league=Champions

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 volleyball odds payload

GET /bookmaker/{bookmakerId}/volleyball/{matchId}

Important response shape:

{
"matchId": 2450840,
"sport": "volleyball",
"odds": {
"setTime": {},
"halfTime": {},
"fullTime": {}
},
"override": []
}

The frontend also loads:

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

5. Use the raw Odds360 REST service

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

6. Subscribe to live updates

Updates

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

Overrides

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

Dashboard subscriptions:

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

7. Optional manual overrides

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

Notes

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