From 3d52656411286045f8d11505002508d0a2b83db0 Mon Sep 17 00:00:00 2001 From: bensynapse <118375461+bensynapse@users.noreply.github.com> Date: Wed, 11 Nov 2026 17:04:29 +0200 Subject: [PATCH 1/2] Add an export formats page (1.13.81) export-formats.html explains how to export matches, fixtures, players, rankings and tournaments to CSV, JSON Lines or Parquet with livetennisapi-export 0.1.0. It is a guide in the GUIDES list. The page says when each format fits. It lists the six datasets with the endpoint and the plan each needs, as the package states them. It also covers paging, how nested fields become dotted columns and when the file is written. The pandas, DuckDB and R examples were run against files the package's own writers produced from its test fixtures. Versions were pandas 3.1.1 with pyarrow 26.0.1, DuckDB 2.0.0, and R 4.6.2 with arrow 26.0.1. _export_drift fails the build when the page names an endpoint the spec does not define. It also fails when the page size differs from the spec's limit maximum. The docs menu, the docs home, the sitemap, llms.txt and the README link the page. Nothing on the wire changed. --- CHANGELOG.md | 5 + README.md | 1 + docs/ai-sdk.html | 3 +- docs/auth-quota-and-health.html | 5 +- docs/broadcast-graphics.html | 5 +- docs/changelog.html | 13 +- docs/errors-and-rate-limits.html | 3 +- docs/export-formats.html | 438 +++++++++++++++++++++++++++ docs/historical-results-archive.html | 5 +- docs/index.html | 3 +- docs/live-scores.html | 5 +- docs/llms.txt | 4 + docs/openapi.json | 2 +- docs/players-and-tournaments.html | 5 +- docs/point-by-point-history.html | 5 +- docs/push-feed-and-webhooks.html | 5 +- docs/reference.html | 5 +- docs/shot-level-rally-data.html | 5 +- docs/sitemap.xml | 3 +- docs/tennis-odds.html | 5 +- openapi.yaml | 2 +- scripts/build_reference.py | 338 +++++++++++++++++++++ 22 files changed, 835 insertions(+), 30 deletions(-) create mode 100644 docs/export-formats.html diff --git a/CHANGELOG.md b/CHANGELOG.md index 8f7cbbd..7ee49f3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,6 +5,11 @@ All notable changes to the specification are recorded here. The API surface is versioned as `v1`. Changes within `v1` are **additive only**; removing a field or changing its type would require `v2`. +## [1.13.81] - 2026-11-11 + +### Added +- **An export formats page.** `export-formats.html` explains how to export matches, fixtures, players, rankings and tournaments to CSV, JSON Lines or Parquet with `livetennisapi-export` 0.1.0. It says when each format fits and lists the six datasets with the endpoint and the plan each needs. It also covers paging, how nested fields become dotted columns and when the file is written. The read-back examples for pandas, DuckDB and R were run against files the package wrote. The build fails when the page names an endpoint or a page size the spec no longer has. The docs menu, the docs home, the sitemap and llms.txt link the page. Nothing on the wire changed. + ## [1.13.80] - 2026-11-09 ### Added diff --git a/README.md b/README.md index 2a095cd..84e3218 100644 --- a/README.md +++ b/README.md @@ -134,6 +134,7 @@ Everything in the Live Tennis API developer surface: | JavaScript / TypeScript client | `npm install livetennisapi` | [repo](https://github.com/livetennisapi/livetennisapi-js) | [package](https://www.npmjs.com/package/livetennisapi) | | MCP server for LLM agents | hosted at `https://mcp.livetennisapi.com/mcp`, or `npx livetennisapi-mcp` | [repo](https://github.com/livetennisapi/livetennisapi-mcp) | [package](https://www.npmjs.com/package/livetennisapi-mcp) | | Vercel AI SDK tools | `npm install livetennisapi-ai` ([guide](https://docs.livetennisapi.com/ai-sdk.html)) | [repo](https://github.com/livetennisapi/livetennisapi-ai) | [package](https://www.npmjs.com/package/livetennisapi-ai) | +| CSV, JSON Lines and Parquet export | `pip install livetennisapi-export` ([guide](https://docs.livetennisapi.com/export-formats.html)) | [repo](https://github.com/livetennisapi/livetennisapi-export) | [package](https://pypi.org/project/livetennisapi-export/) | - **API reference** — ([plain-HTML version](https://docs.livetennisapi.com/reference.html), no JavaScript required) - **Website and plans** — diff --git a/docs/ai-sdk.html b/docs/ai-sdk.html index 525b9a2..013965e 100644 --- a/docs/ai-sdk.html +++ b/docs/ai-sdk.html @@ -200,7 +200,7 @@ -
Live Tennis API DocsGet a free key
Explore the documentation
+
Live Tennis API DocsGet a free key
Explore the documentation

Live Tennis API · docs · guide

@@ -316,6 +316,7 @@ Tennis WebSocket feed and webhooks Tennis API authentication, quota and status Errors and rate limits +Export tennis data to CSV, JSON Lines or Parquet

Written for livetennisapi-ai 1.3.0. Package source in livetennisapi/livetennisapi-ai, page source in livetennisapi/openapi.

Built by Synapse Research Ltd.

diff --git a/docs/auth-quota-and-health.html b/docs/auth-quota-and-health.html index 359b1bc..389fb18 100644 --- a/docs/auth-quota-and-health.html +++ b/docs/auth-quota-and-health.html @@ -199,10 +199,10 @@ -
Live Tennis API DocsGet a free key
Explore the documentation
+
Live Tennis API DocsGet a free key
Explore the documentation
-

Live Tennis API · docs · version 1.13.80

+

Live Tennis API · docs · version 1.13.81

Tennis API authentication, quota and status

How do you authenticate, and how do you see what quota is left? Send your key as X-API-Key on every request. GET /usage returns your own consumption against your plan's quota and works on every tier including FREE, so a client can check its own headroom before a burst. GET /health is the unauthenticated liveness probe.

2 endpoints on this page. Base URL @@ -253,6 +253,7 @@

Example

curl https://api.livetennisapi.com/api/public/v1/usag
 Tennis WebSocket feed and webhooks
 Live Tennis API tools for the Vercel AI SDK
 Errors and rate limits
+Export tennis data to CSV, JSON Lines or Parquet
 
 

Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/broadcast-graphics.html b/docs/broadcast-graphics.html index dfcc1c4..15ec314 100644 --- a/docs/broadcast-graphics.html +++ b/docs/broadcast-graphics.html @@ -199,10 +199,10 @@ -

Live Tennis API DocsGet a free key
Explore the documentation
+
Live Tennis API DocsGet a free key
Explore the documentation
-

Live Tennis API · docs · version 1.13.80

+

Live Tennis API · docs · version 1.13.81

Tennis scores for on-air graphics

How do you put live tennis scores into a broadcast graphics template? GET /broadcast/match/{matchId} returns ONE flat object for one match and GET /broadcast/live the same object for every live match in a single call. Both are ULTRA. A graphics template binds each field to a fixed path, so three things are contractual: the object is flat, every key is present on every read (null, never missing), and the score is already in display form — p1_points reads "40" or "AD" and set_line is one string. Built for 1 Hz: every response carries a strong ETag, so If-None-Match makes an unchanged state a 304 with no body. Detect a new state on sequence, never on served_at, which changes on every read.

2 endpoints on this page. Base URL @@ -273,6 +273,7 @@

Example

curl https://api.livetennisapi.com/api/public/v1/broa
 Tennis API authentication, quota and status
 Live Tennis API tools for the Vercel AI SDK
 Errors and rate limits
+Export tennis data to CSV, JSON Lines or Parquet
 
 

Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/changelog.html b/docs/changelog.html index 612afff..8ca6e55 100644 --- a/docs/changelog.html +++ b/docs/changelog.html @@ -4,7 +4,7 @@ Live Tennis API — Changelog - + @@ -14,7 +14,7 @@ @@ -199,13 +199,18 @@ -

Live Tennis API DocsGet a free key
Explore the documentation
+
Live Tennis API DocsGet a free key
Explore the documentation

Live Tennis API · docs

Changelog

-

Every change to the specification, dated and versioned. The API surface is v1; changes within it are additive only. Current version 1.13.80, last change . Also as the full reference, OpenAPI YAML / JSON, and the dated facts file.

+

Every change to the specification, dated and versioned. The API surface is v1; changes within it are additive only. Current version 1.13.81, last change . Also as the full reference, OpenAPI YAML / JSON, and the dated facts file.

+

1.13.81

+

Added

+
    +
  • An export formats page. export-formats.html explains how to export matches, fixtures, players, rankings and tournaments to CSV, JSON Lines or Parquet with livetennisapi-export 0.1.0. It says when each format fits and lists the six datasets with the endpoint and the plan each needs. It also covers paging, how nested fields become dotted columns and when the file is written. The read-back examples for pandas, DuckDB and R were run against files the package wrote. The build fails when the page names an endpoint or a page size the spec no longer has. The docs menu, the docs home, the sitemap and llms.txt link the page. Nothing on the wire changed.
  • +

1.13.80

Added

    diff --git a/docs/errors-and-rate-limits.html b/docs/errors-and-rate-limits.html index 26212b9..6fc0c34 100644 --- a/docs/errors-and-rate-limits.html +++ b/docs/errors-and-rate-limits.html @@ -200,7 +200,7 @@ -
    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation

    Live Tennis API · docs · guide

    @@ -420,6 +420,7 @@ Tennis WebSocket feed and webhooks Tennis API authentication, quota and status Live Tennis API tools for the Vercel AI SDK +Export tennis data to CSV, JSON Lines or Parquet

    Built from openapi.yaml. Page source in livetennisapi/openapi.

    Built by Synapse Research Ltd.

    diff --git a/docs/export-formats.html b/docs/export-formats.html new file mode 100644 index 0000000..fa4a9be --- /dev/null +++ b/docs/export-formats.html @@ -0,0 +1,438 @@ + + + + + +Export tennis data: CSV, JSONL or Parquet | Live Tennis API + + + + + + + + + + + + + + + + + + + + + +
    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    +
    +

    Live Tennis API · docs · guide

    +

    Export tennis data to CSV, JSON Lines or Parquet

    +

    How do you export tennis data to CSV, JSON Lines or Parquet? Install livetennisapi-export, set LIVETENNISAPI_KEY and name an output file. The file extension picks the format. The command pages through every result and writes matches, fixtures, players, rankings or tournaments.

    +

    Package livetennisapi-export 0.1.0, for Python 3.9 or later. Read-back examples run on with pandas 3.1.1, DuckDB 2.0.0 and R 4.6.2.

    + +
    +
    +

    Install livetennisapi-export

    +

    The package is livetennisapi-export on PyPI. It needs Python 3.9 or later +and installs the official Python client with it.

    +
    pip install livetennisapi-export
    +pip install "livetennisapi-export[parquet]"
    +

    The second line adds Parquet support. The parquet extra brings in pandas and pyarrow.

    + +

    Set the API key

    +

    The command reads your key from the LIVETENNISAPI_KEY environment variable. +Get a free key.

    +
    export LIVETENNISAPI_KEY=twjp_...
    +

    There is no flag for the key, so the key is never part of the export command. Without the variable the +command prints where to get a key and exits with status 2. It sends no request.

    + +

    Which format should I pick?

    +

    The file name picks the format. All three hold the same rows.

    +
    + + +
    The three export formats and when each fits
    FormatFile nameWhat a row isPick it when
    CSV.csvFlat columns, one header line, every value as textYou want to open the file in a spreadsheet or load it into a tool that reads nothing else.
    JSON Lines.jsonl or .ndjsonOne JSON object per line, exactly as the API returned it, nested objects includedYou want the record unchanged, for a pipeline, a document store or a later reshape.
    Parquet.parquet or .pqFlat columns with a type per columnYou analyse the data in pandas, DuckDB or R and want numbers and booleans to stay typed.
    +

    CSV is the one every tool opens. A reader has to work out the types again, because a CSV cell is text. +JSON Lines is the only format that keeps nested objects as objects. Parquet keeps a type for +each column, so a rank stays a number and a flag stays a boolean.

    +

    Use -o - with -f csv or -f jsonl to write to stdout. +Parquet is binary and needs a file name.

    + +

    Which datasets can I export, and which plan does each need?

    +

    There are six datasets. Each one reads a single endpoint through the official Python client. +The plans are the ones the package states.

    +
    + + + + + +
    The six datasets, the endpoint each reads and the plan it needs
    DatasetEndpointPlanRequests
    matchesGET /matchesFREE for live and upcoming. completed and cancelled are part of History and need BASIC or a History planOne per page
    fixturesGET /fixturesFREEOne per page
    playersGET /players?search=FREEOne per page
    playerGET /players/{playerId}FREEOne per player id
    rankingsGET /rankingsPRO. --system elo needs ULTRAOne per page
    tournamentsGET /tournamentsFREEOne per page
    +

    If your plan does not cover a request, the API answers 403. The command then prints the refusal +and exits with status 1. Plans and prices are on the pricing page. +The errors page explains each status.

    +

    The spec also gives a FREE key 20 history calls each calendar month, which completed +matches can use.

    +

    rankings exports one ranking table in rank order, so it needs --system. +The choices are atp, wta, itf_jt, itf_mt, +itf_wt, elo, atp_doubles and wta_doubles. +elo also needs --tour atp or --tour wta. +matches takes --status, and it defaults to upcoming.

    +
    # Upcoming fixtures on the ATP tour
    +livetennisapi-export fixtures --tour atp -o fixtures.csv
    +
    +# Every match completed on one day, as Parquet
    +livetennisapi-export matches --status completed --date 2026-11-08 -o results.parquet
    +
    +# The same day as JSON Lines, rows unchanged
    +livetennisapi-export matches --status completed --date 2026-11-08 -o results.jsonl
    +
    +# Full profiles for a list of player ids
    +livetennisapi-export player 101 202 303 -o players.csv
    +
    +# The current ATP ranking table
    +livetennisapi-export rankings --system atp -o atp.csv
    +
    +# Player search, written to stdout
    +livetennisapi-export players alcaraz -o - -f jsonl
    +

    livetennisapi-export DATASET --help lists every option for a dataset.

    + +

    How does paging work?

    +

    The command asks for pages of 200 rows, the largest page the API allows. It moves +the offset forward by the rows it received and stops when meta.has_more is false. +You never page by hand.

    +
      +
    • Each page is one request against your quota. --max-rows N stops after N rows and +sends no further request.
    • +
    • --page-size takes 1 to 200. Smaller pages mean more requests for the same rows.
    • +
    • player is not paged. It sends one request for each player id you list.
    • +
    +

    Quotas for each plan are on the +authentication, quota and status page.

    + +

    How do nested fields become columns?

    +

    JSON Lines needs no change, so each line is the object the API returned. CSV and Parquet need flat +columns. The writer applies the same rules to both.

    +
      +
    • A nested object becomes one column for each field, named with dots.
    • +
    • A list becomes JSON text in one column.
    • +
    • An empty value is an empty cell in CSV and a null in Parquet.
    • +
    • A boolean is true or false in CSV.
    • +
    +

    Here is a match row cut down to a few fields. The values are made up.

    +
    {"id": 5001, "tournament": "Example Open",
    + "players": {"p1": {"name": "Test Player A", "ranking": 12}},
    + "score": {"sets": [2, 0], "games": [[6, 6], [3, 4]]}}
    +

    It becomes six columns.

    +
    + + + + + +
    The columns the example row becomes
    ColumnValue in the CSV
    id5001
    tournamentExample Open
    players.p1.nameTest Player A
    players.p1.ranking12
    score.sets[2, 0]
    score.games[[6, 6], [3, 4]]
    +

    The columns follow the fields the API sent, in the order they first appear. A field added to the +API shows up as a new column with no upgrade. These names come from files the command wrote on +.

    +
    + + +
    Column names seen in exported files
    ExportSome of its columns
    fixtures, as CSVcreated_at, event_date, gender, id, is_qualifying, match_id, player1_id, player1_name
    matches, completed, as Parquetplayers.p1.itf_ranking.rank_date, score.timestamp
    rankings, --system atpeffective_date, observed_at, player_id, player_name, points, previous_rank, rank, rank_movement
    +

    A match file is wide, because each player object and the score object spread into their own +columns. In Parquet a whole-number column that has an empty value is stored as a decimal number.

    + +

    When is the file written?

    +

    Nothing is written until every page has arrived. A request that fails halfway leaves no +half-written file. A file of the same name from an earlier run stays as it was.

    +
      +
    • A refused API key writes no file. The command prints the refusal and exits with status 1.
    • +
    • A missing key, an unknown file extension with no -f and Parquet to stdout are caught before any +request is sent. +The command exits with status 2.
    • +
    • On success the command exits with status 0. When it writes a file, it prints the row count and the +file name to stderr.
    • +
    • A request that matches no rows still writes the file. The CSV is then empty, with no header line.
    • +
    + +

    How do I read an export in pandas?

    +

    A dotted name is an ordinary column label in pandas.

    +
    import json
    +import pandas as pd
    +
    +results = pd.read_parquet("results.parquet")
    +print(results[["tournament", "round", "players.p1.name", "players.p2.name", "winner"]])
    +
    +# Lists are stored as JSON text. Decode a column when you need the values.
    +results["sets"] = results["score.sets"].map(json.loads, na_action="ignore")
    +
    +fixtures = pd.read_csv("fixtures.csv", parse_dates=["event_date"])
    +print(fixtures.groupby("tournament")["id"].count())
    + +

    How do I query an export in DuckDB?

    +

    DuckDB reads all three formats from the file name.

    +
    -- A dotted column needs double quotes in CSV and Parquet files.
    +SELECT tournament, "players.p1.name", "players.p2.name", winner
    +FROM 'results.parquet'
    +WHERE surface = 'hard';
    +
    +-- Lists are JSON text. Cast one to read it as a list.
    +SELECT id, CAST("score.sets" AS INTEGER[]) AS sets
    +FROM 'results.parquet';
    +
    +-- JSON Lines keeps the nesting, so the same field is a struct path.
    +SELECT tournament, players.p1.name, score.sets
    +FROM read_json_auto('results.jsonl');
    +
    +SELECT rank, player_name, points
    +FROM 'atp.csv'
    +ORDER BY rank;
    + +

    How do I read an export in R?

    +

    Base R reads the CSV. The arrow package reads the Parquet file.

    +
    fixtures <- read.csv("fixtures.csv")
    +table(fixtures$tournament)
    +
    +library(arrow)
    +results <- read_parquet("results.parquet")
    +results[, c("tournament", "players.p1.name", "players.p2.name", "winner")]
    +
    +# Lists are stored as JSON text.
    +library(jsonlite)
    +sets <- lapply(results$score.sets, function(x) if (is.na(x)) NULL else fromJSON(x))
    + +

    Can I export from Python code?

    +

    The same package is a small Python API. fetch returns the rows, write +writes them and export does both.

    +
    from livetennisapi_export import export, fetch, to_dataframe, write
    +
    +rows = fetch("fixtures", tour="atp")               # a list of dicts
    +write(rows, "fixtures.jsonl")
    +
    +export("matches", "results.csv", status="completed", from_="2026-11-01", to="2026-11-07")
    +
    +df = to_dataframe(fetch("rankings", system="atp"))  # the same flat columns as the CSV
    +

    from_ is the from parameter, renamed because from is a Python keyword. +fetch and export take api_key= or read LIVETENNISAPI_KEY. +to_dataframe needs the parquet extra.

    + + + +
    + +
    + + + + diff --git a/docs/historical-results-archive.html b/docs/historical-results-archive.html index dacb278..8fbefe7 100644 --- a/docs/historical-results-archive.html +++ b/docs/historical-results-archive.html @@ -199,10 +199,10 @@ -
    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation
    -

    Live Tennis API · docs · version 1.13.80

    +

    Live Tennis API · docs · version 1.13.81

    Historical tennis results API — 1968 onward

    How far back does the historical tennis data go, and what is in it? The results archive covers 1968 to 2022: GET /history/archive/matches for results, /archive/players for bios, /archive/career for career aggregates and GET /h2h for head-to-head across both the archive and our own completed matches. All BASIC. Matches from 2013 onward additionally carry a reconstructed point-by-point tape at /archive/matches/{archiveId}/tape (ULTRA).

    6 endpoints on this page. Base URL @@ -313,6 +313,7 @@

    Example

    curl https://api.livetennisapi.com/api/public/v1/h2h
     Tennis API authentication, quota and status
     Live Tennis API tools for the Vercel AI SDK
     Errors and rate limits
    +Export tennis data to CSV, JSON Lines or Parquet
     
     

    Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/index.html b/docs/index.html index ca419b6..9c0c2f0 100644 --- a/docs/index.html +++ b/docs/index.html @@ -345,7 +345,7 @@ -

    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation
    @@ -388,6 +388,7 @@

    Tennis data.
    Start building.

    09 / ESSENTIALSAuth, quota & statusAuthenticate, understand limits and check health. 10 / AI SDKVercel AI SDK toolsGive a model live scores and history with livetennisapi-ai. 11 / ERRORSErrors & rate limitsEvery error code, what causes it and when to retry. + 12 / EXPORTCSV, JSON Lines & ParquetExport matches, fixtures, players and rankings to a file.
    Official clientspip install livetennisapinpm install livetennisapinpx livetennisapi-mcpnpm install livetennisapi-ai
    diff --git a/docs/live-scores.html b/docs/live-scores.html index 4c49c6c..03b0e2a 100644 --- a/docs/live-scores.html +++ b/docs/live-scores.html @@ -199,10 +199,10 @@ -
    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation
    -

    Live Tennis API · docs · version 1.13.80

    +

    Live Tennis API · docs · version 1.13.81

    Live tennis scores API

    How do you read live tennis scores from the API? Poll GET /matches?status=live for the slate, then GET /matches/{matchId}/score for the lowest-latency read of one match. Both are on the FREE plan. Scores carry sets, games, points and the server; /events and /points give the same match as a stream of changes rather than a snapshot, so a client can catch up without re-reading state.

    11 endpoints on this page. Base URL @@ -437,6 +437,7 @@

    Example

    curl https://api.livetennisapi.com/api/public/v1/fixt
     Tennis API authentication, quota and status
     Live Tennis API tools for the Vercel AI SDK
     Errors and rate limits
    +Export tennis data to CSV, JSON Lines or Parquet
     
     

    Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/llms.txt b/docs/llms.txt index 4000642..bbc7054 100644 --- a/docs/llms.txt +++ b/docs/llms.txt @@ -30,6 +30,7 @@ endpoints, generated from the same spec as the reference: ## Guides - How do you give a Vercel AI SDK model live tennis data? https://docs.livetennisapi.com/ai-sdk.html - What does each Live Tennis API error mean, and when should a client retry? https://docs.livetennisapi.com/errors-and-rate-limits.html +- How do you export tennis data to CSV, JSON Lines or Parquet? https://docs.livetennisapi.com/export-formats.html ## Quickstart (no code required) Open this in a browser — no install, no headers: https://api.livetennisapi.com/api/public/v1/matches?status=live&token=YOUR_KEY @@ -223,6 +224,9 @@ backtest. - Vercel AI SDK tools: `npm install livetennisapi-ai`, package https://www.npmjs.com/package/livetennisapi-ai, source https://github.com/livetennisapi/livetennisapi-ai (guide: https://docs.livetennisapi.com/ai-sdk.html). The same 25 tools as the MCP server, as AI SDK tools. Reads the key from LIVETENNISAPI_KEY. Needs `ai` v7, which needs Node 22 or later. +- CSV, JSON Lines and Parquet export: `pip install livetennisapi-export`, package https://pypi.org/project/livetennisapi-export/, + source https://github.com/livetennisapi/livetennisapi-export (guide: https://docs.livetennisapi.com/export-formats.html). Six datasets: matches, + fixtures, players, player, rankings and tournaments. Reads the key from LIVETENNISAPI_KEY. ## Affiliate programme - https://affiliates.livetennisapi.com/program — 51% recurring commission for the lifetime diff --git a/docs/openapi.json b/docs/openapi.json index fb9c2ad..b81bfe6 100644 --- a/docs/openapi.json +++ b/docs/openapi.json @@ -2,7 +2,7 @@ "openapi": "3.1.0", "info": { "title": "Live Tennis API", - "version": "1.13.80", + "version": "1.13.81", "contact": { "name": "Live Tennis API", "url": "https://livetennisapi.com" diff --git a/docs/players-and-tournaments.html b/docs/players-and-tournaments.html index 56d36eb..6cca478 100644 --- a/docs/players-and-tournaments.html +++ b/docs/players-and-tournaments.html @@ -199,10 +199,10 @@ -

    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation
    -

    Live Tennis API · docs · version 1.13.80

    +

    Live Tennis API · docs · version 1.13.81

    Tennis players, tournaments and rankings API

    How do you look up a player, a tournament or a ranking? GET /players searches by name and GET /players/{playerId} returns one player's bio, current ranking and cached statistics — both FREE. GET /players/{playerId}/stats (PRO) is the player's win/loss record over our completed matches, split by surface, level and season, with ULTRA adding summed serve and return statistics. GET /tournaments is the catalogue that Match.tournament_id joins against, so a match can be resolved to its event without a second lookup. GET /rankings serves rank-ordered listings on PRO. The per-player as-of records, including the Elo tape, are ULTRA.

    8 endpoints on this page. Base URL @@ -330,6 +330,7 @@

    Example

    curl https://api.livetennisapi.com/api/public/v1/rank
     Tennis API authentication, quota and status
     Live Tennis API tools for the Vercel AI SDK
     Errors and rate limits
    +Export tennis data to CSV, JSON Lines or Parquet
     
     

    Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/point-by-point-history.html b/docs/point-by-point-history.html index c3f149c..5ed51d3 100644 --- a/docs/point-by-point-history.html +++ b/docs/point-by-point-history.html @@ -199,10 +199,10 @@ -

    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation
    -

    Live Tennis API · docs · version 1.13.80

    +

    Live Tennis API · docs · version 1.13.81

    Point-by-point tennis data API

    Which endpoints return point-by-point tennis data, and how complete is it? GET /history/matches/{matchId} returns the tape for one completed match: the ordered score states we hold for it. The model's win probability sits on the rows that were observed live, and coverage is declared per match. GET /history/matches lists completed matches with their tape coverage, and GET /history/coverage is the measured completeness rollup per tour and draw bucket — a number we publish rather than estimate, with its own as_of. GET /history/packages serves the same data as pre-built monthly bulk files.

    8 endpoints on this page. Base URL @@ -333,6 +333,7 @@

    Example

    curl https://api.livetennisapi.com/api/public/v1/hist
     Tennis API authentication, quota and status
     Live Tennis API tools for the Vercel AI SDK
     Errors and rate limits
    +Export tennis data to CSV, JSON Lines or Parquet
     
     

    Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/push-feed-and-webhooks.html b/docs/push-feed-and-webhooks.html index 1cc94f5..dcefdb2 100644 --- a/docs/push-feed-and-webhooks.html +++ b/docs/push-feed-and-webhooks.html @@ -199,10 +199,10 @@ -

    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation
    -

    Live Tennis API · docs · version 1.13.80

    +

    Live Tennis API · docs · version 1.13.81

    Tennis WebSocket feed and webhooks

    How do you receive tennis data as it happens instead of polling? Two ways, both ULTRA. GET /ws-token mints a short-lived token for the high-fan-out push feed, which streams score and point changes as they are written. POST /webhooks registers an outbound HTTP callback for the same events; GET /webhooks lists your registrations and never returns the signing secret. Webhooks require a direct key, not a marketplace one.

    4 endpoints on this page. Base URL @@ -293,6 +293,7 @@

    Example

    curl https://api.livetennisapi.com/api/public/v1/ws-t
     Tennis API authentication, quota and status
     Live Tennis API tools for the Vercel AI SDK
     Errors and rate limits
    +Export tennis data to CSV, JSON Lines or Parquet
     
     

    Generated from openapi.yaml by livetennisapi/openapi. Every endpoint on diff --git a/docs/reference.html b/docs/reference.html index d86368e..b661e15 100644 --- a/docs/reference.html +++ b/docs/reference.html @@ -202,12 +202,12 @@ -

    Live Tennis API DocsGet a free key
    Explore the documentation
    +
    Live Tennis API DocsGet a free key
    Explore the documentation

    Live Tennis API — Full Reference

    -

    Version 1.13.80 · OpenAPI 3.1.0

    +

    Version 1.13.81 · OpenAPI 3.1.0