The standings endpoint returns the full league table organised by group, together with a cross-group ranking of fourth-placed teams used to determine playoff qualification. Results are served from a Redis cache that is valid for one hour and is invalidated automatically whenever a match is marked as finished.Documentation 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.
Endpoint
Method:GETPath:
/standingsAuth: None
Query parameters
Season to fetch standings for. When omitted, the currently active season is used.
Caching
Responses are cached in Redis for 3,600 seconds (1 hour). The cache key isstandings for the active season or standings:<season_id> when a season ID is specified. The cache is invalidated automatically after any match in that season is finalised.
Response
A map where each key is a group name (e.g.
"Grupo A") and the value is an ordered array of team objects sorted by the competition tiebreaker rules.ID of the best-ranked fourth-placed team across all groups, used to fill a knockout playoff slot.
null if no fourth places exist.Ordered array of all fourth-placed teams ranked against each other by the competition tiebreaker criteria. Each entry has the same fields as the team objects inside
groups, adjusted to exclude matches against teams that did not exist in groups with fewer sides.Tiebreaker rules
When teams are level on points the server applies the following criteria in order:- Head-to-head points in matches between the tied teams.
- Overall goal difference.
- Goals scored.
- Goals conceded (fewer is better).
- Fair-play score (
yellow_cards + red_cards × 3, lower is better). - Database ID (descending) as the final deterministic tiebreaker.
Example
Response