How we built Live Tennis API

Live Tennis API sells professional tennis data to developers. It covers ATP, WTA, Challenger and ITF, singles and doubles, over REST and WebSocket. The free plan has live scores, players and fixtures. Paid plans add completed results, the point-by-point record, market prices, rankings and a win-probability model, up to $99.99 a month.

Synapse built it. The company that sells it is JSB Holdings LLC, a Delaware company, and the product’s about page names it as the operator. It is the one case on this site with a name on it. We can name it because every part of it is public, so you can check each claim below yourself.

What we built

The API and the data behind it

One base URL and one version, v1. Changes inside v1 are additive, and the changelog dates every one of them. On 23 September 2026 it stood at version 1.13.44.

Behind it sit two archives. The results archive holds 1,485,752 ATP and WTA results from 1968 to 2022. On 14 September 2026 the point-by-point tape held 27,381,531 rows. That covers 179,578 of the 187,832 matches completed since January 2023. Both figures come from the product’s own facts file, which prints the day each one was counted.

The documentation

A full reference in plain HTML that reads without JavaScript, and an interactive one beside it. The OpenAPI 3.1 specification is on GitHub. Topic pages each answer one question, such as how to read a live score or how far back the history goes.

Client libraries and integrations

Official clients for Python, JavaScript and TypeScript, Go, Swift, .NET, Dart, PHP and Laravel. The Python one installs with pip install livetennisapi and the JavaScript one with npm install livetennisapi. The GitHub organisation had 58 public repositories on the day we checked. They include plugins for n8n, Home Assistant, VS Code and Obsidian.

The MCP server

npx livetennisapi-mcp gives Claude, Cursor, Zed or any other MCP client 24 read-only tools over the API. It is listed in the official MCP Registry as io.github.livetennisapi/livetennisapi-mcp. The tools only read, and the API behind them never touches orders or wallets.

Search and answer engines

This is the work our answer-engine page sells, run on our own product first. The robots.txt names GPTBot, ClaudeBot, PerplexityBot and the other AI crawlers one by one. The site’s llms.txt file sums up the product for answer engines, and the docs have their own. The about page prints every figure with the date it was counted, because an answer engine hedges on a number it can’t date. A second site, besttennisapi.com, publishes its measurement method and an open benchmark tool before any result.

What you can check

All of it. The site, the docs, the GitHub organisation, the npm and PyPI packages and the MCP Registry entry are public. The organisation’s GitHub profile links back to us under “Build with Synapse”. We checked every fact on this page against those sources on 24 September 2026.

What this page leaves out is revenue, customer numbers and traffic. They are private, and a figure you can’t check has no place in a case study.

Which of our services this is

The API and the pipeline are custom software. The SDKs, the MCP server and the GitHub work are developer marketing and GitHub marketing. The crawler rules, the llms.txt files and the dated facts are our answer-engine work.