> ## Documentation Index > Fetch the complete documentation index at: https://padelapi.org/docs/llms.txt > Use this file to discover all available pages before exploring further. # Show Match Point By Point > Retrieve the full point-by-point reconstruction of a padel match: every set, every game and every point as it was played. It works for **live matches** (updated within seconds of each point) and for **finished matches** (the complete historical record), making it the building block for live score widgets, win-probability models, momentum charts and match replays. > 🔒 This endpoint [requires a **Pro** subscription](https://padelapi.org/billing). ### Response shape The match breaks down into nested `sets → games → points`: - Each **set** has a `set_number` and a `set_score` (e.g. `"6-3"`, or `null` while the set is still in progress). - Each **game** has a `game_number`, the cumulative `game_score` at the start of the game (e.g. `"3-2"`), the `serving` team (`"team_1"`, `"team_2"` or `null` when unknown) and the ordered list of `points` (`["0:0", "15:0", "15:15", …]`). ### Status and coverage - `status` — `live`, `finished`, `retired`, `walkover`, `bye` or `scheduled`. - `coverage` — how complete the tracking is: `full` (every game captured), `partial` (the source feed had gaps), `tracking` (still live, resolved once finished) or `null` (no point-by-point data available). ### Live updates: poll or subscribe You can poll this endpoint, but for real-time apps subscribe to push updates instead. Every response includes a `channel` (e.g. `matches.123`) and a `connections.match` link; broadcast events arrive over Pusher. See the [WebSockets guide](https://padelapi.org/docs/websockets) for the subscription flow. ### Related endpoints - [Show Match](https://padelapi.org/docs/api-reference/match/show-match) — teams, score, round and tournament. - [Show Match Stats](https://padelapi.org/docs/api-reference/match/show-match-stats) — aggregated match statistics. - [List Live Matches](https://padelapi.org/docs/api-reference/live/list-live-matches) — every match currently in progress. ## OpenAPI ````yaml https://padelapi.org/docs/api.json get /matches/{match}/live openapi: 3.1.0 info: title: Padel API – API Reference version: '1.0' description: padelapi.org servers: - url: https://padelapi.org/api security: - http: [] paths: /matches/{match}/live: get: tags: - Match summary: Show Match Point By Point description: >- Retrieve the full point-by-point reconstruction of a padel match: every set, every game and every point as it was played. It works for **live matches** (updated within seconds of each point) and for **finished matches** (the complete historical record), making it the building block for live score widgets, win-probability models, momentum charts and match replays. > 🔒 This endpoint [requires a **Pro** subscription](https://padelapi.org/billing). ### Response shape The match breaks down into nested `sets → games → points`: - Each **set** has a `set_number` and a `set_score` (e.g. `"6-3"`, or `null` while the set is still in progress). - Each **game** has a `game_number`, the cumulative `game_score` at the start of the game (e.g. `"3-2"`), the `serving` team (`"team_1"`, `"team_2"` or `null` when unknown) and the ordered list of `points` (`["0:0", "15:0", "15:15", …]`). ### Status and coverage - `status` — `live`, `finished`, `retired`, `walkover`, `bye` or `scheduled`. - `coverage` — how complete the tracking is: `full` (every game captured), `partial` (the source feed had gaps), `tracking` (still live, resolved once finished) or `null` (no point-by-point data available). ### Live updates: poll or subscribe You can poll this endpoint, but for real-time apps subscribe to push updates instead. Every response includes a `channel` (e.g. `matches.123`) and a `connections.match` link; broadcast events arrive over Pusher. See the [WebSockets guide](https://padelapi.org/docs/websockets) for the subscription flow. ### Related endpoints - [Show Match](https://padelapi.org/docs/api-reference/match/show-match) — teams, score, round and tournament. - [Show Match Stats](https://padelapi.org/docs/api-reference/match/show-match-stats) — aggregated match statistics. - [List Live Matches](https://padelapi.org/docs/api-reference/live/list-live-matches) — every match currently in progress. operationId: getMatchPointByPoint parameters: - name: match in: path required: true description: The match ID schema: type: integer responses: '200': description: '' content: application/json: schema: type: object properties: id: type: integer self: type: string status: type: string coverage: type: string channel: type: string sets: type: array items: type: object properties: set_number: type: integer set_score: type: string games: type: array items: type: object properties: game_number: type: integer game_score: type: string serving: type: string points: type: array items: type: string required: - game_number - game_score - serving - points required: - set_number - set_score - games connections: type: object properties: match: type: string required: - match required: - id - self - status - coverage - channel - sets - connections '401': $ref: '#/components/responses/AuthenticationException' '404': $ref: '#/components/responses/ModelNotFoundException' '422': $ref: '#/components/responses/ValidationException' components: responses: AuthenticationException: description: Unauthenticated content: application/json: schema: type: object properties: message: type: string description: Error overview. required: - message ModelNotFoundException: description: Not found content: application/json: schema: type: object properties: message: type: string description: Error overview. required: - message ValidationException: description: Validation error content: application/json: schema: type: object properties: message: type: string description: Errors overview. errors: type: object description: A detailed description of each field that failed validation. additionalProperties: type: array items: type: string required: - message - errors securitySchemes: http: type: http scheme: bearer ````