Live Tennis API · Schema

Event

CompanySportsDataReal-TimeTennis

Properties

Name Type Description
type string The stoppage family (added 2026-09-12). `medical_timeout_start/end`, `trainer_called/_end` and `toilet_break_start/end` are stated by the match scorer or chair umpire, with `player` = the player conce
player integernull
timestamp stringnull
at stringnull Stoppage family — the UTC instant the stoppage happened (for a pause, its last score change).
detected_at stringnull Stoppage family — when we recorded it.
basis stringnull Stoppage family — observed (a source stated it) or inferred (measured from our clocks).
reason stringnull Stoppage family — medical_timeout | unspecified | no_treatment | taping | changeover_treatment | evaluating | failed | toilet_break | weather | other | resumed | unknown.
position stringnull pause rows only — where the last point left the match, which sets the silence threshold.
score objectnull Stoppage family — sets, games, points, server at the moment of the stoppage.
duration_seconds integernull end rows only.
View JSON Schema on GitHub

JSON Schema

livetennisapi-com-event-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/livetennisapi-com/json-schema/livetennisapi-com-event-schema.json",
  "title": "Event",
  "x-generated": "2026-11-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/livetennisapi-com-matches-api-openapi.yml#/components/schemas/Event",
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "enum": [
        "break",
        "set_won",
        "game_won",
        "momentum_run",
        "stoppage_start",
        "stoppage_end",
        "pause_start",
        "pause_end",
        "medical_timeout_start",
        "medical_timeout_end",
        "trainer_called",
        "trainer_called_end",
        "toilet_break_start",
        "toilet_break_end"
      ],
      "description": "The stoppage family (added 2026-09-12). `medical_timeout_start/end`, `trainer_called/_end` and `toilet_break_start/end` are stated by the match scorer or chair umpire, with `player` = the player concerned. Coverage (2026-09-13): WTA, WTA 125, Challenger and UTR singles — WTA and WTA 125 in two layers: the match state within ~20 s (`trainer_called`, `toilet_break_*`, `stoppage_*`, player null) and a later event layer with a variable delay (measured 2026-09-13: about one minute to an hour behind play), which adds `medical_timeout_start/end` with the player and exact instants; Challenger and UTR from the scorer timeline (22 of 70 finished Challenger matches, median 8 s). ITF World Tennis Tour singles from the court's live-scoring state (the state, not the player: `player` is null on ITF rows; first medical timeout observed and published 2026-09-13). ATP main tour: the live match stage is watched for its medical-timeout and interruption stages — present in the vocabulary, not yet observed on a tennis match, so ATP rows are mapped, not yet proven (`player` null, `at` = our observation instant). Not doubles. `stoppage_start/end` is a whole-match stop (`reason` weather | other when stated, unknown when only a bare suspension flag reached us). `pause_start/end` is an interruption of play measured from our own point clocks (`basis: inferred`), never labelled medical."
    },
    "player": {
      "type": [
        "integer",
        "null"
      ],
      "enum": [
        1,
        2,
        null
      ]
    },
    "timestamp": {
      "type": [
        "string",
        "null"
      ],
      "format": "date-time"
    },
    "at": {
      "type": [
        "string",
        "null"
      ],
      "format": "date-time",
      "description": "Stoppage family — the UTC instant the stoppage happened (for a pause, its last score change)."
    },
    "detected_at": {
      "type": [
        "string",
        "null"
      ],
      "format": "date-time",
      "description": "Stoppage family — when we recorded it."
    },
    "basis": {
      "type": [
        "string",
        "null"
      ],
      "enum": [
        "observed",
        "inferred",
        null
      ],
      "description": "Stoppage family — observed (a source stated it) or inferred (measured from our clocks)."
    },
    "reason": {
      "type": [
        "string",
        "null"
      ],
      "description": "Stoppage family — medical_timeout | unspecified | no_treatment | taping | changeover_treatment | evaluating | failed | toilet_break | weather | other | resumed | unknown."
    },
    "position": {
      "type": [
        "string",
        "null"
      ],
      "enum": [
        "point",
        "changeover",
        "setbreak",
        null
      ],
      "description": "pause rows only — where the last point left the match, which sets the silence threshold."
    },
    "score": {
      "type": [
        "object",
        "null"
      ],
      "description": "Stoppage family — sets, games, points, server at the moment of the stoppage."
    },
    "duration_seconds": {
      "type": [
        "integer",
        "null"
      ],
      "description": "end rows only."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/livetennisapi-com-event"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.