Charted matches with shot-by-shot data (ULTRA)

Charted matches, newest first. RALLY CONSTRUCTION IS THE LAYER BELOW THE TAPE: the tape says what the score became after each point, this says how the point was played.

It has its OWN id space. The charted corpus and our own match table are different populations — the corpus reaches back decades and concentrates on the biggest events, while our matches begin when our own collection did. Keying this on our match ids would hide most of it. Ask this endpoint for the authoritative coverage list rather than assuming a match is charted: charting is human work, so coverage is deep, not universal.

get/rally/matches

Request

  • Base URL: https://api.livetennisapi.com/api/public/v1
  • URL: https://api.livetennisapi.com/api/public/v1/rally/matches
  • Auth: one of:
    • HTTP bearer
    • API key in header X-API-Key

Query parameters

playerstring

Substring match on either player name.

fromstring date

YYYY-MM-DD.

tostring date

YYYY-MM-DD.

surfacestring
gender'M' | 'W'
limitinteger
offsetinteger

Response

Charted matches, with per-match parse-quality counts

Changes

No recorded changes to this operation across all 1 revision of this API.