Betfair integration
Match tennis data to Betfair runners.
Connect DFT tennis identities to a Betfair market and its selections, keeping player meaning intact even when runner order changes.
Runner identity should survive a reordered list.
Alcaraz appears first in the runner list. The mapping still connects each selection to the right player.
betfair context
Keep your platform identifiers alongside the DFT match.
- marketId
<market_id>
The two runners are intentionally in reverse order. Selection identity must follow the player, not row position.
- Both player identitiesMatched
- Tournament edition and dateMatched
- Named outcome / runnerMatched
A confirmed mapping can carry DFT scores, history and probabilities into your application.
{
"platform": "betfair",
"status": "matched",
"dft_match_id": "cfaabd98-37a1-4652-b1a3-8b26b5840b7e",
"dft_edition_id": "f431d1e9-bd98-4d7c-ace9-d34a795f7175",
"platform_ids": {
"marketId": "<market_id>"
},
"outcomes": [
{
"ref": "<alcaraz_selection_id>",
"playerId": "22c4fbb8-caae-4bfd-b732-aef9b8a5f986",
"side": "b"
},
{
"ref": "<sinner_selection_id>",
"playerId": "bfec67b0-65b9-4f6a-bce2-5c6d8dd001b6",
"side": "a"
}
]
}marketId identifies the market; each selectionId is connected to its own DFT player.
Keep runner identity when the order changes.
The example maps supplied selection references to players, with explicit unresolved states.
status- matched, ambiguous or unmatched. An unresolved case keeps the mapping empty.
dft_match_id- The DFT match identity used to join points, players and the tournament edition.
platform_ids- The supplied platform references, kept distinct from DFT match and player identifiers.
outcomes- Each named reference keeps its playerId and side. Reordering a list does not change player identity.
Questions
Connect the runners before the data.
Explore the mapping behavior and prepare the data access your application needs.