Rally construction by OUR match id (ULTRA)

Rally construction addressed by OUR match id, resolved through the optional link. Answers 404 {"error":"not_charted"} when we hold the match but nobody charted it — deliberately distinct from "no such match", because most of our matches are not charted and a consumer walking the archive must tell them apart.

get/history/matches/{matchId}/rally

Request

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

Path parameters

matchIdinteger required

The match id. Every match route shares ONE id space, so the same value works everywhere matchId appears.

Get it from any match list, where it is the id field of each match object: GET /matches?status=live (in progress), GET /matches?status=upcoming or GET /fixtures (scheduled), GET /matches?status=completed or GET /history/matches (finished).

Ids are stable for the life of a match, so one captured before it starts still resolves after it finishes.

Query parameters

limitinteger
offsetinteger

Response

The charted match with its rally points

rally_match_idinteger

The id this product is keyed on.

source_idstring
match_idinteger nullable

OUR match id, when the charted match is also one we hold. Null otherwise — most charted matches predate our own collection.

datestring date nullable
tournamentstring nullable
roundstring nullable
surfacestring nullable
gender'M' | 'W' | 'null' nullable
best_ofinteger nullable
pointsinteger

Charted points in this match.

points_parsedinteger

How many of them our parser read cleanly — the per-match quality number.

Changes

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