Polymarket integration
Connect tennis data to Polymarket.
Connect a DFT match and named player to Polymarket event, market and outcome context for a clearer application data flow.
The token must keep the outcome’s meaning.
Explore the mapping from a platform reference to a DFT match and player, including unresolved cases.
polymarket context
Keep your platform identifiers alongside the DFT match.
- event_id
<event_id>- conditionId
<condition_id>
An event contains market questions and named outcomes. Each token must keep the right player meaning.
- Both player identitiesMatched
- Tournament edition and dateMatched
- Named outcome / runnerMatched
A confirmed mapping can carry DFT scores, history and probabilities into your application.
{
"platform": "polymarket",
"status": "matched",
"dft_match_id": "cfaabd98-37a1-4652-b1a3-8b26b5840b7e",
"dft_edition_id": "f431d1e9-bd98-4d7c-ace9-d34a795f7175",
"platform_ids": {
"event_id": "<event_id>",
"conditionId": "<condition_id>"
},
"outcomes": [
{
"ref": "<alcaraz_token_id>",
"playerId": "22c4fbb8-caae-4bfd-b732-aef9b8a5f986",
"side": "b"
},
{
"ref": "<sinner_token_id>",
"playerId": "bfec67b0-65b9-4f6a-bce2-5c6d8dd001b6",
"side": "a"
}
]
}The token references remain attached to named outcomes. Array order alone does not determine player identity.
Keep the outcome attached to its player.
The example preserves supplied event, condition and outcome references alongside DFT identities.
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
Give platform references tennis meaning.
Inspect the reconciliation path and prepare a data workflow you can understand.