Kalshi integration
Tennis data for Kalshi.
Connect tennis match and player context to Kalshi event and market identifiers before adding data to your application.
A ticker is only the start.
Explore a clear match, an ambiguous case and an unmatched event. Inspect the mapping each case produces.
kalshi context
Keep your platform identifiers alongside the DFT match.
- event_ticker
<event_ticker>- ticker
<market_ticker>
A yes/no market refers to a named player and a particular match. Keep that meaning alongside the ticker.
- Both player identitiesMatched
- Tournament edition and dateMatched
- Named outcome / runnerMatched
A confirmed mapping can carry DFT scores, history and probabilities into your application.
{
"platform": "kalshi",
"status": "matched",
"dft_match_id": "cfaabd98-37a1-4652-b1a3-8b26b5840b7e",
"dft_edition_id": "f431d1e9-bd98-4d7c-ace9-d34a795f7175",
"platform_ids": {
"event_ticker": "<event_ticker>",
"ticker": "<market_ticker>"
},
"outcomes": [
{
"ref": "yes",
"playerId": "bfec67b0-65b9-4f6a-bce2-5c6d8dd001b6",
"side": "a"
},
{
"ref": "no",
"playerId": "22c4fbb8-caae-4bfd-b732-aef9b8a5f986",
"side": "b"
}
]
}The mapping preserves event_ticker, market ticker and the player behind yes/no. Read the platform rules for the specific market.
Keep the ticker and player identity distinct.
This local reconciliation example preserves supplied Kalshi references beside the selected DFT match.
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
Start from a match you can identify.
Inspect how reconciliation behaves, then prepare your DFT data workflow.