League 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.

Domestic league standings

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.


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.

Using includes

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


Cup standings

For ‘normal’ domestic Leagues, the response format is different compared to Cups.

If you have Cups and ‘normal’ leagues in your plan, make sure to check out the response correctly. Let’s look at one of the most requested leagues: the Champions League 2020/2021 season (league id: 2 and season id: 17299).

You can use the same endpoint as with a standard league. However, the response will be very different.


As you can see, the standings are grouped by ... groups!

We can’t stress this enough. It’s paramount that you read the response correctly.

Due to our unique group ids, you can also request the specific groups you’re interested in with the group_ids parameter.

Let’s say you only want the standings of Group C. You can add the group_idsparameter with the group id of Group C (244367) to the request. You can also request multiple groups by separating them with a comma.