Fixtures by Multiple IDs

The IDs you want to retrieve.

Enrich the API response with more data by using includes. Ex. &include=participants;events

Allowed values: sport, round, stage, group, aggregate, league, season, coaches, tvStations, venue, state, weatherReport, lineups, events, timeline, comments, trends, statistics, periods, participants, odds, premiumOdds, inplayOdds, prematchNews, metadata, sidelined, predictions, referees, formations, ballCoordinates, scores, xGFixture, pressure, expectedLineups, matchfacts. Pass as a semicolon-separated list (the API rejects comma here), e.g. include=sport;round.

Select specific fields on the base entity . Read how to select fields in our tutorial .

Selectable fields: id, sport_id, league_id, season_id, stage_id, group_id, aggregate_id, state_id, round_id, venue_id, name, starting_at, result_info, leg, details, length. Pass as a comma-separated list, e.g. select=id,sport_id.

Order by specific fields on the base entity . For more information check out this page.

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.

Composable filter expression in the form name1:value1,value2;name2:value3. Available filter names: participantSearch, todayDate, venues, Deleted, markets, bookmakers, WinningOdds, fixturestatisticTypes, eventTypes, lineupdetailTypes, fixtureStates, fixtureLeagues, fixtureGroups, coachCountries, seasonStatisticTypes. Pass as a single string — the API rejects the bare comma-joined value codegen tools emit when this is modeled as an array.

Translate name fields of the API Response in your selected language. Find more information and which languages are available on our translations page .