API Endpoints

These are the REST endpoints your platform must expose to receive live data. Each path corresponds to a specific message type we will POST to your platform. Use the tables below for URL structure, headers, and match ID resolution.

Base URL

bash

https://api.partner.integration.odds-prod.{host}

URL Pattern

bash

{baseUrl}/v1/{product}/{partnerId}/match:{matchId}/{messageType}

Component	Value	Description
baseUrl	https://api.partner.integration.odds-prod.{host}	Partner platform API base
product	liveodds	Product identifier
partnerId	{partnerId}	Your assigned partner identifier
matchId	e.g. 65865058	Match ID (numeric)

Endpoints

POST

/v1/liveodds/{partnerId}/match:{matchId}/oddsLive

Receives odds changes, full snapshots, or market deactivation messages from our engine

Operation: Odds Delta / Snapshot / DeactivationResponse: 202 Accepted

POST

/v1/liveodds/{partnerId}/match:{matchId}/market_settlementLive

Receives market settlement results after round or fight conclusion

Operation: Market SettlementResponse: 202 Accepted

POST

/v1/liveodds/{partnerId}/match:{matchId}/rollback_settlementLive

Receives rollback requests to reverse previous market settlements for correction

Operation: Rollback SettlementResponse: 202 Accepted

POST

/v1/liveodds/{partnerId}/match:{matchId}/heartbeatLive

Receives keep-alive signals sent every 5 seconds during idle periods

Operation: Session HeartbeatResponse: 202 Accepted

Required Headers

Header	Value
Authorization	Bearer {access_token}
Content-Type	application/json

Match ID Resolution

Priority	Source	Field	Description
1	External Fight ID	fight_metadata.fight_id_sr	Preferred — e.g. match:65865058
2	Fight Mapping	In-memory mapping	Maps internal fight IDs to external IDs
3	Fallback	match:{cardId}	Built from {card}{fightId}{correctionNumber}