#General
The Tennis Live Data API is designed to be as simple as possible to use (just like all the sportcontentapi API’s!). Below is a standard workflow to get you started using the API.
#Sample Workflows
GET /tours
Note: This endpoint will show you the most recent seasons first. You can assume these are the currently active seasons. The tour_code
and tour_season_id
attributes for each object are what you’ll want to use to query the /tournaments endpoint.
GET /tours -> GET /tournaments/tour_code
/tour_season_id
Note: The /tournaments endpoint is a calendar of tournaments across the entire tour season. You’ll want to note the id
of each tournament object in order to query matches relating to that tournament.
GET /tours -> GET /tournaments/tour_code
/tour_season_id
-> GET /matches/tournament_id
Note: The matches endpoint will list all published matches for a given tournament with basic details such as match status
round_name
and date
. In some tournaments this file can get quite big, so consider using the /matches/tournament_id
/YYYY-MM-DD
endpoint to limit results to a single day of a tournament. The valid days for a tournament can be determined by the start_date
and end_date
of each tournament in the /tournaments/tour_code
/tour_season_id
endpoint. Names are shortened in this endpoint for easier small screen display.
GET /tours -> GET /tournaments/tour_code
/tour_season_id
-> GET /matches-results/tournament_id
Note: This endpoint will work the same as the standard matches endpoint, but will retrieve a results
object, as well as a home
and away
player object for each match. Study the meta
object to understand how results are published. Again, this endpoint can result in a very large file as tournaments progress. It is advisable to narrow down calls to a particular date by passing a date parameter the endpoint like so /matches-results/tournament_id
/YYYY-MM-DD
to ensure the best possible page load speeds.
GET/tours-> GET /tournaments/tour_code
/tour_season_id
-> GET /matches/tournament_id
-> GET /match/match_id
**Note: ** This will pull up a single match with all possible details for the given match_id
GET/matches-by-date- defaults to today’s date
GET/matches-by-date/YYYY-MM-DD - specific date
**Note: ** This will pull up all matches, across all tournaments, and present the results in an array containing a tournament
object, as well as a matches
array for easy listing on your application.
tour_code
:GET /rankings/tour_code
- retrieves overall rankings
GET /rankings/race/tour_code
- retrieves race (season) rankings
**GET /player/player_id
Note: This endpoint will retrieve player first_name
, last_name
, full_name
, and country
as well as ranking info for both the overall and season rankings.
Don’t see what you’re looking for? Send us a mail and we’ll be happy to help. If you feel we could do more or do it differently, also let us know!