Tennis API documentation
Tennis data, one call awayEvery professional singles match, men from 1877 and women from 1968: Grand Slams and tour events down to challengers and ITF, with scores, rounds, surfaces and seeds. Where it is known, each match carries its closing prices, every bookmaker's price and how it moved, games and sets lines, correct score prices, full match statistics and every point.
Results are added about every ten minutes as matches finish. People build betting models and backtests, results widgets, player and tournament pages, fantasy and scouting tools, and assistants that answer tennis questions from facts rather than memory. JSON over HTTPS, GET only, UTC times, and ids that never change.
1Start here
2Every subject
Results on a day, yesterday's results, one match in full, the week's events and doubles.
Read the guideFind a player by name: their profile and record, matches, seasons, titles, rankings over time, Elo and head to heads.
- Find players
- Player profile
- Player matches
- Player seasons
- Player titles
- Ranking history
- Elo history
- Head to head
Find an event, see every season it has been held, every match and the draw of a season, and its champions.
Read the guideClosing prices on every match list; on one match each bookmaker, the opening prices, the lines and every move; and how the market has done.
Read the guideServe, return and point statistics by set, point by point, and a player's figures over many matches.
Read the guide3Every endpoint
GETMatches on a day/v1/matches | Matches on a day, with scores and closing prices |
GETYesterday's results/v1/results/yesterday | Yesterday's results |
GETFixtures/v1/fixtures | The matches set to be played, from those under way to two days ahead: start time, round, both players with ranking and Elo, the chance Elo gives each, and the price before play where the market has one |
GETLive scores/v1/live | The singles matches in play now, read every 15 seconds: sets, games, the game in progress with who serves and its points, how long ago each was read, and those finished in the last 15 minutes |
GETLive match/v1/live/{id} | One match in play: the live score and every game so far, point by point, with who served, breaks, break points and set points. After it leaves Live, its last score stays here 7 days (meta.in_live false) |
GETMatch/v1/matches/{id} | One match: score, every bookmaker's price with its opening price, the games and sets lines, correct score prices, price movement and the full statistics |
GETMatch statistics/v1/matches/{id}/statistics | Serve and return figures for each player, for the match and each set, with the service games held and broken |
GETPoint by point/v1/matches/{id}/points | Every game and point of a match: who served, who won it, breaks, break points and set points |
GETMatch prices/v1/matches/{id}/odds | Every bookmaker's closing and opening price for a match, and every market: games, sets, handicaps and correct score |
GETPrice moves/v1/matches/{id}/moves | Each change of each bookmaker's match price before the start, timed |
GETFind players/v1/players | Find players by name |
GETPlayer profile/v1/players/{id} | A player, with their win and loss record by surface |
GETPlayer matches/v1/players/{id}/matches | A player's matches, newest first |
GETPlayer seasons/v1/players/{id}/seasons | A player's won and lost by season, and by surface within each season |
GETPlayer statistics/v1/players/{id}/statistics | A player's serve and return figures over every match held with statistics, and their opponents' against them |
GETPlayer titles/v1/players/{id}/titles | Every final a player won and lost, by level |
GETRanking history/v1/players/{id}/rankings | A player's singles ranking and points, week by week, newest first |
GETElo history/v1/players/{id}/elo | A player's Elo rating now, and before every match, overall and on the match's surface, with the chance it gave them |
GETHead to head/v1/h2h/{a}/{b} | Head to head between two players |
GETRankings/v1/rankings | The current singles rankings, with each player's highest ranking and Elo |
GETRankings on a date/v1/rankings/{date} | The ranking list of the week of a date: singles, men from 1973 and women from 2003; women's doubles with list=doubles |
GETElo ratings/v1/elo | The players our Elo rates highest, overall or on one surface, among those with a match in the last year |
GETFind tournaments/v1/tournaments | Tournaments, by name, tour or tier |
GETTournament/v1/tournaments/{id} | A tournament and every season held |
GETTournament season/v1/tournaments/{id}/{season} | Every match of one season of a tournament |
GETSeason draw/v1/tournaments/{id}/{season}/draw | One season of a tournament round by round, from qualifying to the final, with seeds and entry |
GETChampions/v1/tournaments/{id}/champions | The champion and runner-up of every season of a tournament, and who has won it most |
GETThis week/v1/calendar | The events being played in the week of a date, every level, with surface, city and matches held so far |
GETDoubles on a day/v1/doubles | Every doubles match of one day, with both pairs, seeds, the score and closing prices |
GETDoubles pair/v1/doubles/pairs/{id} | A doubles pair, their record together and every match they played, newest first |
GETMarket accuracy/v1/markets/accuracy | How often the closing favourite won: by price, level, surface and season, and over the last 30 days |
GETBiggest upsets/v1/markets/upsets | The longest closing prices that won at Grand Slam and tour level |
GETBookmaker margins/v1/markets/margins | Each bookmaker's average margin on its closing prices since the start of last year |
GETAll-time leaders/v1/records | The most matches won and the most titles, all time |
GETSeason leaders/v1/records/{season} | The most matches won and the most titles in one season |
GETSearch/v1/search | Players and tournaments together, by name |
GETCoverage/v1/meta/coverage | What the database holds, season by season, counted from the data |
GETBulk files/v1/exports | Every season as compressed CSV files: matches, prices, price moves, statistics and point by point, with rows, size and checksum, rebuilt nightly |
GETBulk file/v1/exports/{season}/{dataset} | One season's file of one dataset (matches, prices, moves, statistics or points), gzip-compressed CSV |
GETUsage/v1/usage | Your plan, calls used and limits (does not count) |
paid plans; the rest are on every plan, the free key included
4Popular calls
| Match prices |
| Player profile |
| Ranking history |
| Elo history |
| Tournament |
5For assistants and agents
https://api.tennisdatabaseapi.com/mcphttps://tennisdatabaseapi.com/documentation/mcp-toolshttps://tennisdatabaseapi.com/documentation/manual.md6Plans in short
7What is new
| 2026-11-05 | Tie-breaks in the point by point: each tie-break is now one game with tiebreak set to true, its points the running tie-break score in the same order as every other game (winner first in a match's points, player_1 first live), its server the player who served the first point. Until now each tie-break point was held as a game of its own. Every match was read again and rebuilt, and the service-game summaries follow. |
| 2026-10-31 | Live scores: /v1/live lists the singles matches in play now, read every 15 seconds, with sets, games, the game in progress, who is serving and its points, and /v1/live/{id} adds every game so far, point by point. On the Live and Complete plans. |
| 2026-10-29 | Every knockout match carries draw: the match its winner went on to and the matches that led into it, and each match in a tournament draw carries next_match, so a bracket can be built from the answers. |
8Everything else
9Questions people ask
Men's matches from 1877 and women's from 1968. Prices and statistics start later and are fullest from the 2000s; Coverage counts them decade by decade. More
Finished matches are added about every ten minutes. The free key reads yesterday to two days ahead; Live reads the last 45 days. More
Both where known: the market's closing price, each bookmaker's closing price with its opening price, and every recorded move in between. More
Not yet: singles only, and point by point arrives once a match is finished. More
Yes: connect the MCP server, or give your agent the skill file. Both use your normal key and plan. More
Nothing in your code changes: fields that were null fill in, and the dates your plan reads widen at once. More