GET All Fixtures
GET
All Fixtures
GET
All FixturesEndpoint details
Authorization
API Key
Pagination
YES
Allowed nested includes
10
Parameters
Available parameters
include
Enrich the API with more data and/or nested includes. Can be used by adding &include=
etc. to your request url.
filter
Array of fields to filter on. Can be used by adding &filter[{field you want to filter}].
For example: &filter[league_id]=4.
fields[object]
Only return fields you are interested in. Every type of data in the response has a resource type, like fixtures or battings. Simply add &fields[object]=id,name,code
to your request URL. For example: &fields[fixtures]=id&fields[battings]=active.
sort
One or comma separated list of fields to sort on. Can be used by adding &sort=
to your request url.
page
The number of the page you want to browse. Can be used by adding &page=
etc to your request url.
Filters
season_id
league_id
localteam_id
visitorteam_id
status
referee_id
round
stage_id
starts_between
Custom Filters
On this endpoint we offer the option to use a custom date filter to get all fixtures played between 2 dates. Add &filter[starts_between]=2019-03-03,2019-03-15
to the query string to get all games played between these 2 dates.
Sort
You can sort on all fields.
Include options
balls
runs
bowling
batting
venue
stage
season
league
visitorteam
localteam
scoreboards
firstumpire
secondumpire
referee
manofseries
manofmatch
tosswon
lineup
Includes are the cornerstone of our API and allow you to enrich and customize your requests. This flexibility is what distinguishes us from our competitors.
To gain more information on the relations available for the include you can use nested includes. For example you can use batting.batsman
or batting.bowler
or batting.runoutby
. more option are available.
You can learn more about what includes are and how they work here:
Enriching your responseExample response
Last updated