GET Fixtures by Date Range for Team
Returns the fixtures from your requested date range for your team
Name | Required? | Description |
---|---|---|
| YES Another option is to provide the API token in the header. | Your unique API token. Ex. ?api_token=YOUR_TOKEN |
| NO | Enrich the API response with more data by using includes. Ex. &include=participants;events |
| NO | Select specific fields on the base entity. Read how to select fields in our tutorial. |
| NO | Order by specific fields on the base entity. For more information check out this page. |
| NO | Filter the API response on multiple related entities. There are static filters and dynamic filters. Please find the possibilities in the Static and Dynamic Filter tab. |
| NO | Translate name fields of the API Response in your selected language. Find more information and which languages are available on our translations page. |
Filters
More information on how to use filters can be found on our tutorials on how to filter. If you want more information on which filters to use you can check out the following endpoint:
Pagination
YES
Parameters
Parameter | Required | Description | Example |
---|---|---|---|
| No | Returns fixtures ordered by starting_at ( | &order=desc |
| No | The amount of results to return per page (max 50.). Defaults to 25. | &per_page=30 |
| No | You can paginate using the | &page=2 |
Include depth
You can use a total of 3
nested includes on this endpoint
Include options
sport
round
stage
group
aggregate
league
season
coaches
tvStations
venue
state
weatherReport
lineups
events
timeline
comments
trends
statistics
periods
participants
odds
premiumOdds
inplayOdds
prematchNews
postmatchNews
metadata
sidelined
predictions
referees
formations
ballCoordinates
scores
xGFixture
pressure
Related Entities:
Get an overview and explanation of all the fields returned in the API response. The related entities for the fixtures endpoints are:
Code Example
Last updated