Fixtures
The match schedule: tournament, round, scheduled time, players and current status. This is the foundation almost every integration starts with - see it in action in the quickstart guide.
Livescore
Real-time score data for matches in progress: current set and game score, server, and match status. Available both via REST polling and the WebSocket feed for point-by-point push updates - see REST vs WebSocket for live tennis data for how to choose between them.
Head to head (H2H)
Historical results between two specific players, including surface breakdowns - commonly used to power the "H2H record" panel shown before a match on score widgets and betting products.
Standings
Tournament and ranking standings, useful for leaderboards, qualification tracking, and season-long dashboards.
Players
Player profile data - name, nationality, ranking and career information - used to enrich fixtures and build player-centric pages or fantasy rosters.
Pre-Match Odds
Odds set ahead of a match, via the get_odds endpoint - the data type behind pre-tournament pricing pages and outright markets. This is stable, non-live data, so it fits naturally into the REST request-response model. See the Odds reference in the documentation.
Live Odds
Odds for matches currently in progress, via the get_live_odds endpoint. Unlike pre-match odds, this data moves with the score, which is why it's typically paired with the WebSocket feed so your pricing stays in sync with what's happening on court - see Live Odds reference in the documentation.
Statistics
In-match and historical statistics - the detail layer behind coaching and performance-analytics tools, as discussed in What Can You Build With a Tennis API?.
Full reference
Every field, parameter and response example for each of these data types is documented in full in the API documentation. If your product needs real-time updates on any of this data, also read the WebSocket documentation.