Fixtures
The fixture endpoint provides information about games in particular leagues. For many customers, the endpoint 'fixtures' is the primary endpoint for their app or website. Because 'fixtures' is one of our API’s most critical endpoints, we’re going to walk you through all six different ways of using the endpoint.
The endpoint is subdivided over six categories where you can request the endpoint:
All these endpoints, except get last updated, share the same possible includes and parameters. Please refer to our includes and filter tutorials on how to use them. Some of the most used filters are:
Leagues: filter on league ids.
Bookmakers*: filter on bookmaker ids.
Markets*: filter on market ids.
Status: filter on status.
A total overview of the includes and parameters is available at our API reference guide. For this example, we’re going to show you how to use our different fixture endpoints. You’ll learn how to request fixtures using an id and using a specified date (range).
The end goal of this tutorial is to successfully request (multiple) fixture IDs, as well as request all fixtures between two dates for Celtic. Let’s get started then, shall we?
What is fixture data?
Well, I lied. Before we get started, we’ll first show you what kind of data the fixture endpoints get you.
See below for a response with all the data from one fixture.
It might seem overwhelming, but don’t worry! As you might have noticed in all of our previous tutorials, we've included a tab with the field descriptions.
A small recap: We can see the id of the fixture, which is 16475287. Every fixture has his own unique id. Next, we can see various other ids, such as league, season, local and visitor teams, and the winner’s id. Scroll down a bit more, and you’ll see the final score, total playing time and date of when the match was played, and both teams’ standings.
Request fixtures by date
We’re going to start by using the endpoint called fixtures by date.
We’ve used this endpoint multiple times in our previous tutorials. This is the best option if you want to request all the fixtures of a specific date. You will need to fill in the date in a YYYY-MM-DD format. The API will return all the fixtures of the specified date you requested.
So, let’s say we use the following default date, that is also used in Postman: 2020-08-02:
Notice how it’s the same response as our fixture example above? Next up, we’ll show you how to get all the fixtures between two specified dates.
Request fixture by date range
Sometimes, you want to get all the fixtures for a certain date range, such as all the fixtures in a week. Our fixture by date range endpoint will do this for you. You can request fixtures between days, weeks, months, and even years. Once again, the date should be filled in in the YYYY-MM-DD format.
Now, let’s say we want to have all the fixtures that are being played in the week of 2020-08-02 until 2020-08-10:
The API will give you all the fixtures between the requested dates. We'll happily show you the API response, but it's not any different from the response of our previous request.
Request fixture by id
The fixture by id endpoint is perfect when you want to request information about a single fixture. This endpoint is often used for specific match pages. To make use of this endpoint, simply use the following URL:
Now, we simply add the fixture id from step 1:
Well, will you look at that? It’s the exact same response!
You can also request fixture by multiple ids, in case you want to request more than one. This is a different endpoint An actual request will look like this:
And that’s done too.
Note that you can request a maximum of 25 fixtures with this endpoint.
Request all fixtures of your favorite team!
As a football fan, you might be more interested in all the matches of your favorite team. We understand and got you covered with our endpoint: get fixtures by date range for team. This endpoint is basically a minor extension from fixtures by date range:
So, let’s say we’re major Celtic fan (team id: 53):
Just like that, we requested all the Celtic fixtures between the 2nd of August 2020 and the 10th of August of 2020. This endpoint is excellent for when you are building an application for your favorite team. Because you get to see how your team performed between two dates. If you know the dates for when the season began and when it ended, you can also request all the particular season’s fixtures.
Keep it, synced!
To help you keep your data in sync, we have implemented an endpoint that returns you all the games that have received an update within two hours. Fixtures that have updated lineups, events, or statistics are included. You will only receive updates for fixtures that have ended or haven’t started yet.
Something that’s closely linked to fixtures is our livescores endpoint. We will discuss this in the next chapter.
Last updated
Was this helpful?