Participants

What does the include do?

The participants include provides comprehensive information about the teams (participants) involved in a specific fixture. This include gives you detailed data about each team including their name, logo, founding year, venue, and match-specific metadata such as home/away status and winner information.

Why use participants?

The participants include is essential for:

  • Team identification: Get team names, logos, and short codes for display

  • Match context: Understand home/away dynamics and venue information

  • Result tracking: Immediately identify which team won the match

  • Team profiles: Access founding year, country, and team type information

  • UI/UX development: Get all necessary team data for building match interfaces

In API 3.0, participants replaced the older localTeam and visitorTeam includes to support multi-sport data models.

Requesting participants

To retrieve participant information for a fixture, use the following include:

https://api.sportmonks.com/v3/football/fixtures/{fixture_id}
?api_token=YOUR_TOKEN&include=participants

Example: Get participants for Manchester United vs Everton (fixture ID: example)

https://api.sportmonks.com/v3/football/fixtures/{fixture_ID}
?api_token=YOUR_TOKEN&include=participants

Response structure

When you include participants in your request, you'll receive an array of two participant objects (home and away teams):

Field descriptions

Main participant fields

Field
Type
Description

id

integer

Unique identifier for this team

sport_id

integer

ID of the sport (1 = football/soccer)

country_id

integer

ID of the team's country

venue_id

integer

ID of the team's home stadium/venue

gender

string

Gender of the team: "male", "female", or "mixed"

name

string

Full name of the team

short_code

string

3-letter abbreviation for the team (e.g., "MUN", "EVE")

image_path

string

URL to the team's logo/crest image

founded

integer

Year the team was founded

type

string

Team type: "domestic" or "national"

placeholder

boolean

Indicates if this is a placeholder team (TBD teams in cup draws)

last_played_at

string

DateTime of the team's most recent match

Meta object fields

The meta object contains fixture-specific information about the participant:

Field
Type
Description

meta.location

string

Team's location in this fixture: "home" or "away"

meta.winner

boolean

Whether this team won the match (true/false)

meta.position

integer

Team's league table position at the time of the match

Understanding home vs away

In API 3.0, the distinction between home and away teams is provided in the meta.location field:

  • "home": The team playing at their home venue

  • "away": The visiting team

This is different from API 2.0 which used localTeam and visitorTeam includes.

Identifying the winner

The meta.winner field immediately tells you which team won the match:

Nested includes

The participants include does not have specific nested includes documented, but you can use the participant_id to fetch more detailed team information using the Teams endpoints if needed.

Code examples

Python example

JavaScript example

Common use cases

1. Match header display

Create a visual match header for your application:

2. Historical performance tracking

Track how teams perform home vs away:

3. Cup draw management

Handle TBD teams in cup competitions:

Build a logo display for multiple fixtures:

Best practices

  1. Always check meta.location: Don't assume array order for home/away teams. Always use meta.location to identify teams correctly.

  2. Handle placeholder teams: In cup competitions, check the placeholder field to handle TBD teams appropriately.

  3. Cache team logos: Team logos rarely change. Cache them locally to reduce bandwidth and improve performance.

  4. Use short_code for displays: The 3-letter short code is perfect for space-constrained displays (mobile, scoreboards).

  5. Combine with other includes: Use &include=participants,scores,events to get complete match data in one request.

  6. Check for national teams: Use the type field to distinguish between club teams ("domestic") and national teams ("national").

Differences from API 2.0

In API 2.0, teams were accessed via:

  • localTeam (home team)

  • visitorTeam (away team)

In API 3.0, this changed to:

  • participants (array containing both teams)

  • Use meta.location to identify home/away

Migration example:

  • Scores - Combine with scores to show team names and final results

  • Lineups - Get player lineups for each participant

  • Events - See which team scored goals and received cards

  • Venue - Get detailed venue information for the home team

Summary

The participants include provides essential team information for fixtures including names, logos, home/away status, and winner information. The meta object contains fixture-specific data like location and winner status, making it easy to build match displays and track team performance. Always use meta.location to correctly identify home and away teams in API 3.0.

Last updated

Was this helpful?