In this part of the tutorial series, we’re going to discuss standings. We’ll explain what standings are, how they can be displayed and most importantly, which endpoints and includes you can use to request various standings.
Standings, also known as rankings, show the positions of the teams competing in a season. Standings show the total number of games played, won, lost, the number of goals for and against and the number of points they have accumulated.
So, how do you request all of this data yourself? We’re going to show you how! In this tutorial, we will first show you how to request standings for the English Premier League season 20/21 (season id: 17420 ).
Afterward, we’ll go more in-depth with an example about the Champions League’s standings. We’ll then show you how to request standings for groups and stages. And finally, how to request live standings!
Let’s get started.
The English Premier League is an example of a domestic league, similar to the Italian Serie A, German Bundesliga, etc.
Standings can easily be requested with the standings by season id endpoint.
In order to request the standings of the English Premier League, we need the following things:
A valid API token
Access to the English Premier League (league id: 8) in your paid plan
The season id of the English Premier League season 20/21 (season id: 17420 ).
This will result in the following request and response.
Season Field Description
Field
Description
id
The unique id of the current stage
name
The name of the stage
league_id
The unique league id the stage belongs to
season_id
The unique id of the current season
round_id
The unique id of the current round
round_name
The name of the round
type
Indicates what kind of type this stage is
stage_id
The unique id of the current stage
stage_name
The name of the stage
Standings Field Description
Field
Description
position
The actual position in the rankings in the stage
team_id
The unique team id of the team in that position in the stage
team_name
The team name in that position in the stage
round_id
The unique id of the current round
round_name
The name of the round
group_id
The unique id of the group, in which the team participates in
group_name
The name of the group, in which the team participates in
overall
The overall results of the team, i.e., the number of games, points and goals
home
The home results of the team, i.e., the number of games, points and goals
away
The away results of the team, i.e., the number of games, points and goals
total
The total points of the team and their goal difference
results
The standing rules of the place the team is in
points
The accumulated number of points the team has
recent_form
The recent form of the team
status
Will be available in API 3.0: Indicates if the team moves up on down based on the last standings.
Most of the data speaks for itself. Just like in our other tutorials, we've added a field description overview in the third tab.
However, a field that needs some further explanation is result
.
This field will contain the standing rules of a season. Each season has its own standing rules. The number one at the end of the season will be crowned champions and “earns” something.
For example, the winner of the English Premier League will earn the right to compete in a different competition, such as the Champions League or Europa League.
Or, in case of finishing last, the team will relegate to a lower division. You can find the possible outcomes in our API references.
You can enrich your request with includes. But beware, the includes on our standings by season id endpoint requires additional action. Namely, you will need to prefix the include.
What is prefixing exactly? With nested includes, you add the additional information at the end of the include. i.e., lineup.player
With prefixing, it’s the other way around. You will need to prefix every available include with standings.
So, for example, if you want to have additional team information, you will need to prefix teams with standings like this: standings.team