// Matches
Get match referee
Get the referee for a match along with their career totals for games, yellow cards and red cards. Use it to judge how strict a referee tends to be, for example for card markets or match previews.
GET
https://api.soccer-data.co/v1/matches/{match_id}/referee
- referee is null when no referee has been assigned yet, so handle that case.
- If you only need the referee's name, Get a match already includes it, so you can skip this call.
Path parameters
match_idstringrequired
The match's id, like match_…. Find one with the ID guide.
Response fields
data.match_idstring
The match's id.
data.refereeobject|null
The referee for this match. Null when none is assigned.
data.referee.idstring
Referee's id.
data.referee.namestring
Referee's name.
data.referee.slugstring|null
URL-friendly name, handy for building links.
data.referee.countrystring
Country the referee comes from.
data.referee.country_codestring|null
Two-letter ISO country code, when we have it.
data.referee.country_slugstring|null
URL-friendly country name.
data.referee.careerobject
Totals across the referee's career.
data.referee.career.gamesinteger
Matches refereed.
data.referee.career.yellow_cardsinteger
Yellow cards shown.
data.referee.career.red_cardsinteger
Red cards shown.
data.referee.career.yellow_red_cardsinteger
Red cards that came from a second yellow.
curl "https://api.soccer-data.co/v1/matches/match_9pd0ck6g2m9i/referee" \ -H "X-Api-Key: $SOCCER_DATA_KEY"
const res = await fetch("https://api.soccer-data.co/v1/matches/match_9pd0ck6g2m9i/referee", {
headers: { "X-Api-Key": process.env.SOCCER_DATA_KEY },
});
const { data } = await res.json();
import os, requests
res = requests.get(
"https://api.soccer-data.co/v1/matches/match_9pd0ck6g2m9i/referee",
headers={"X-Api-Key": os.environ["SOCCER_DATA_KEY"]},
)
data = res.json()["data"]
$data = Http::withHeaders(['X-Api-Key' => env('SOCCER_DATA_KEY')])
->get('https://api.soccer-data.co/v1/matches/match_9pd0ck6g2m9i/referee')
->json('data');
200 · Example response
{
"data": {
"match_id": "match_9pd0ck6g2m9i",
"referee": {
"id": "referee_o1sm9am51qq5",
"name": "Chris Kavanagh",
"slug": "chris-kavanagh-referee_o1sm9am51qq5",
"country": "England",
"country_code": null,
"country_slug": "england",
"career": {
"games": 322,
"yellow_cards": 1176,
"red_cards": 28,
"yellow_red_cards": 12
}
}
}
}
### GET /matches/{match_id}/referee
Get match referee
Get the referee for a match along with their career totals for games, yellow cards and red cards. Use it to judge how strict a referee tends to be, for example for card markets or match previews.
- referee is null when no referee has been assigned yet, so handle that case.
- If you only need the referee's name, Get a match already includes it, so you can skip this call.
Response fields:
- `data.match_id` (string): The match's id.
- `data.referee` (object|null): The referee for this match. Null when none is assigned.
- `data.referee.id` (string): Referee's id.
- `data.referee.name` (string): Referee's name.
- `data.referee.slug` (string|null): URL-friendly name, handy for building links.
- `data.referee.country` (string): Country the referee comes from.
- `data.referee.country_code` (string|null): Two-letter ISO country code, when we have it.
- `data.referee.country_slug` (string|null): URL-friendly country name.
- `data.referee.career` (object): Totals across the referee's career.
- `data.referee.career.games` (integer): Matches refereed.
- `data.referee.career.yellow_cards` (integer): Yellow cards shown.
- `data.referee.career.red_cards` (integer): Red cards shown.
- `data.referee.career.yellow_red_cards` (integer): Red cards that came from a second yellow.
Example: curl "https://api.soccer-data.co/v1/matches/match_9pd0ck6g2m9i/referee" -H "X-Api-Key: $SOCCER_DATA_KEY"