canonical: https://jentic.com/apis/livetennisapi.com/livetennisapi

# Live Tennis API

The Live Tennis API serves real-time tennis scores, player and tournament data, match-winner market prices, and model-driven match analysis across the ATP, WTA, Challenger, ITF, and junior tours. It is read-only, exposes live per-point events and statistics, a results archive back to 1968, head-to-head records, shot-by-shot charting, and outbound webhooks for match updates.

## For AI agents

Read live tennis scores, player and tournament data, market prices, and match analysis, and register webhooks for match updates.

## Scope

Does not cover other sports, sell betting slips, or settle wagers. Use for tennis scores, data, market prices, and match analysis only.

## Capabilities

- Read live match scores and per-point events as they happen
- Look up player bios, rankings, and tournament catalogues
- Retrieve match-winner market prices and recent price ticks
- Query head-to-head records and a results archive back to 1968
- Register outbound webhooks for live match updates

## Use cases

### Agent-driven live score updates through Jentic

An AI agent running a sports assistant can read the live score of a match and stream per-point events as they happen. Through Jentic the agent discovers the score and events operations by intent and loads their schemas, so it reports updates without wiring the Live Tennis endpoints.

Example prompt: Search Jentic for 'get a match score', find a match in progress, and read its current score and latest per-point events.

### Head-to-head and historical lookups

Build previews by pulling head-to-head records and past results from an archive reaching back to 1968. The API joins matches to players and tournaments by stable ids, so an agent can assemble a matchup summary from consistent references.

Example prompt: Look up the head-to-head record between two players and pull their recent completed matches.

### Market price monitoring

Track match-winner market prices and recent price ticks per side for matches in progress. The API returns the mapped market and its price history so an agent can monitor movement without maintaining its own feed.

Example prompt: Retrieve the match-winner market prices for a match and read the recent price ticks per side.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/matches` | List matches by lifecycle status |
| GET | `/matches/{matchId}/score` | Get current match score |
| GET | `/players` | Search players by name |
| GET | `/tournaments` | List tournaments |
| GET | `/rankings` | List rankings |
| GET | `/h2h` | Get head-to-head records |
| GET | `/markets/{matchId}/prices` | Get market prices per side |

## Key resources

- **Matches** — Live and completed matches with scores and events
- **Players and tournaments** — Player bios, rankings, and tournament catalogues
- **Markets** — Match-winner market prices and price ticks

## Why Jentic

- **Setup:** Wiring the Live Tennis API by hand means sending its bearer key or X-API-Key header, resolving its versioned host, and handling live and archive read patterns yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Live Tennis API is read-only for its data surface, so a rule can allow only the read operations your agent needs. You choose the operations it may call, such as scores and rankings, so registering or deleting webhooks is not included unless you add it.
- **Credential handling:** Your Live Tennis key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a match score' or 'get head-to-head records', and Jentic returns the matching Live Tennis operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **TheSportsDB** — Free sports data across many sports
- **Sportmonks** — Sports data feeds with detailed statistics
- **The Odds API** — Betting odds across sports and bookmakers

## FAQ

### What authentication does the Live Tennis API use?

The Live Tennis API accepts either a bearer token or an X-API-Key header per its OpenAPI spec. Through Jentic your key is stored encrypted by your own Jentic One instance and injected at request time, so your agent never sees it.

### Is there a Live Tennis API MCP server?

You don't need an MCP server to give your agent the Live Tennis API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it on demand without loading another server's tool definitions into its context.

### Can I get live scores with the Live Tennis API?

Yes. The score operation returns the current score for a match with the lowest latency, and the events operation returns per-point events newest first for matches in progress.

### What are the rate limits for the Live Tennis API?

Access is tiered as FREE, BASIC, PRO, and ULTRA, and the OpenAPI spec does not state numeric per-tier request limits. Check the Live Tennis documentation at https://livetennisapi.com for current tier limits.

### Can I limit what my agent is allowed to do with the Live Tennis API?

Yes. The Live Tennis API is read-only for data, so allow only the read operations your agent needs, such as scores, rankings, and head-to-head records, while withholding the webhook-management operations unless you add them. Every call it makes is logged.

### How do I get a match score with the Live Tennis API through Jentic?

Search Jentic for 'get a match score', load the score operation, and pass the match id. Jentic injects your key and returns the current score. To run it on your own infrastructure, install Jentic One from its GitHub repo.