Docs menu

SofaScore API endpoint

SofaScore referee card statistics API

Returns a referee's record per competition: matches officiated, yellow cards, red cards, yellow-red cards and penalties awarded. The per-competition appearances add up to the career matches in sofascore-referee. An empty `competitions` list is valid for a referee with no recorded competitions.

GETapiKey1 credit/requestSofaScoresofascore.refereeStatisticsResponseDoc/sofascore/referee-statistics

Endpoint facts

Method: GET
API path: /sofascore/referee-statistics
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: SofaScore
Response schema: #/definitions/sofascore.refereeStatisticsResponseDoc

SofaScore API Try SofaScore referee card statistics API in Playground SofaScore API documentation

How this endpoint behaves

Query parameters:

id: required. Numeric SofaScore referee id, e.g. 74264. Get it from the referee.id of sofascore-event or from a sofascore-search result of type referee.

Notable response behavior:

Each row has appearances, yellow_cards, red_cards, yellow_red_cards and penalties for one competition. The appearances add up to the career games of sofascore-referee. Zero counts are real values.
An empty competitions list is a valid response for a referee with no recorded competitions.

Live monitoring

Monitored request: GET /sofascore/referee-statistics?id=74264
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 0.87 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /sofascore/referee-statistics?id=74264
Items in competitions: 15
Fields filled in every checked item: 6

Field	Filled in, of 15 checked	Values in the sample
competition	15
appearances	15	1 to 111, median 3
yellow_cards	15	3 to 457, median 18
red_cards	15	0 to 7, median 0
yellow_red_cards	15	0 to 7, median 0
penalties	15	0 to 36, median 1

Request parameters

Parameter	Type	Required	Default	Description	Example
id	string	Yes		Numeric SofaScore referee id	74264
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/sofascore/referee-statistics?id=74264" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "referee_id": 74264,
    "source_url": "https://api.sofascore.com/api/v1/referee/74264/statistics",
    "fetched_at": "2026-10-07T00:00:00Z",
    "count": 1,
    "competitions": [
      {
        "competition": {
          "id": 24,
          "name": "League One",
          "slug": "league-one",
          "category": "England",
          "sport": "football"
        },
        "appearances": 27,
        "yellow_cards": 86,
        "red_cards": 4,
        "yellow_red_cards": 1,
        "penalties": 11
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/sofascore.refereeStatisticsResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	sofascore.RefereeStatisticsResponse	No
data.competitions	array	No
data.competitions[].appearances	integer	No	27
data.competitions[].competition	sofascore.UniqueTournamentBrief	No		UniqueTournamentBrief record, 6 fields: category, gender, id, name, slug, sport. Described under SofaScore team competitions API.
data.competitions[].penalties	integer	No	11
data.competitions[].red_cards	integer	No	4
data.competitions[].yellow_cards	integer	No	86
data.competitions[].yellow_red_cards	integer	No	1
data.count	integer	No
data.fetched_at	string	No
data.referee_id	integer	No	74264
data.source_url	string	No
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
429	Too Many Requests	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/sofascore/referee-statistics?id=74264" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More SofaScore endpoint docs SofaScore API SofaScore categories for a sport API documentation SofaScore competitions in a category API documentation SofaScore league draft picks API documentation SofaScore league draft API documentation SofaScore esports game detail API documentation SofaScore event at-bat pitches API documentation

Open in Playground Back to group

Docs menu

SofaScore API endpoint

SofaScore referee card statistics API

GETapiKey1 credit/requestSofaScoresofascore.refereeStatisticsResponseDoc/sofascore/referee-statistics

Endpoint facts

Method: GET
API path: /sofascore/referee-statistics
Auth: apiKey
Credits: 1 credit/request
Charged on: Successful 2xx responses only
Platform: SofaScore
Response schema: #/definitions/sofascore.refereeStatisticsResponseDoc

SofaScore API Try SofaScore referee card statistics API in Playground SofaScore API documentation

How this endpoint behaves

Query parameters:

id: required. Numeric SofaScore referee id, e.g. 74264. Get it from the referee.id of sofascore-event or from a sofascore-search result of type referee.

Notable response behavior:

Each row has appearances, yellow_cards, red_cards, yellow_red_cards and penalties for one competition. The appearances add up to the career games of sofascore-referee. Zero counts are real values.
An empty competitions list is a valid response for a referee with no recorded competitions.

Live monitoring

Monitored request: GET /sofascore/referee-statistics?id=74264
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 0.87 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /sofascore/referee-statistics?id=74264
Items in competitions: 15
Fields filled in every checked item: 6

Field	Filled in, of 15 checked	Values in the sample
competition	15
appearances	15	1 to 111, median 3
yellow_cards	15	3 to 457, median 18
red_cards	15	0 to 7, median 0
yellow_red_cards	15	0 to 7, median 0
penalties	15	0 to 36, median 1

Request parameters

Parameter	Type	Required	Default	Description	Example
id	string	Yes		Numeric SofaScore referee id	74264
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/sofascore/referee-statistics?id=74264" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "referee_id": 74264,
    "source_url": "https://api.sofascore.com/api/v1/referee/74264/statistics",
    "fetched_at": "2026-10-07T00:00:00Z",
    "count": 1,
    "competitions": [
      {
        "competition": {
          "id": 24,
          "name": "League One",
          "slug": "league-one",
          "category": "England",
          "sport": "football"
        },
        "appearances": 27,
        "yellow_cards": 86,
        "red_cards": 4,
        "yellow_red_cards": 1,
        "penalties": 11
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/sofascore.refereeStatisticsResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	sofascore.RefereeStatisticsResponse	No
data.competitions	array	No
data.competitions[].appearances	integer	No	27
data.competitions[].competition	sofascore.UniqueTournamentBrief	No		UniqueTournamentBrief record, 6 fields: category, gender, id, name, slug, sport. Described under SofaScore team competitions API.
data.competitions[].penalties	integer	No	11
data.competitions[].red_cards	integer	No	4
data.competitions[].yellow_cards	integer	No	86
data.competitions[].yellow_red_cards	integer	No	1
data.count	integer	No
data.fetched_at	string	No
data.referee_id	integer	No	74264
data.source_url	string	No
msg	string	No	OK

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
429	Too Many Requests	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/sofascore/referee-statistics?id=74264" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

Open in Playground Back to group

SofaScore referee card statistics API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related

SofaScore referee card statistics API

Endpoint facts

How this endpoint behaves

Live monitoring

Sampled response

Request parameters

cURL example

Example JSON response

Failure responses

Code examples

Shared guides

Related