TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/danielsl4/TFG_DAM_2526/llms.txt
Use this file to discover all available pages before exploring further.
/matches/:id endpoint returns all data for a single match, extending the fields available from the list endpoint with a full chronological events array. This is the primary source of truth for match scorecards and live event feeds.
Authentication is optional. When a valid JWT is provided, the userVote field reflects the authenticated user’s vote for that match.
Response is cached in Redis per match and per user. The cache is invalidated whenever the match is modified.
Request
Method:GETPath:
/matches/:id
Path parameters
Unique identifier of the match to retrieve.
Headers
Optional.
Bearer <token> — include to receive the userVote field populated for the authenticated user.Response
200 OK
A single match object. All fields from the list endpoint are present, plus theevents array below.
Unique match identifier.
Match date and time in ISO 8601 format.
Label for an unresolved home team slot.
Label for an unresolved away team slot.
Goals scored by the home team.
Goals scored by the away team.
Home team penalty shootout goals.
Away team penalty shootout goals.
"pendiente", "en_curso", or "finalizado".Competition phase.
Group name, or null for knockout stages.
Referee notes.
Authenticated user’s vote, or null.
Ordered list of in-match events, from first to last recorded.
Errors
| Status | Condition |
|---|---|
404 Not Found | No match exists for the given id. |
500 Internal Server Error | Database or cache error. |
Example
200 response