Docs menu

SofaScore API endpoint

SofaScore event statistics API

Returns one match's statistics (possession, shots, passes, and more, grouped and split by period). Returns 404 when SofaScore has no tracked statistics for the match.

GETapiKey2 credits/requestSofaScoresofascore.eventStatisticsResponseDoc/sofascore/event-statistics

Endpoint facts

Method: GET
API path: /sofascore/event-statistics
Auth: apiKey
Credits: 2 credits/request
Charged on: Successful 2xx responses only
Platform: SofaScore
Response schema: #/definitions/sofascore.eventStatisticsResponseDoc

SofaScore API Try SofaScore event statistics API in Playground SofaScore API documentation

How this endpoint behaves

Query parameters:

id: required. Numeric SofaScore event (match) id.

Notable response behavior:

Successful responses are cached for 10 minutes by default.
A genuine not-found response is cached for 30 minutes by default. Repeating the same request during that window returns the cached 404; upstream blocks and other failures are not cached by this policy.
Statistics can appear later for an upcoming or live match. A cached absence can delay their visibility by up to 30 minutes, so avoid immediate retries and recheck after that interval when new coverage is expected.
404 responses consume the plan’s request-rate allowance but do not consume credits.
Returns 404 when SofaScore has no tracked statistics for the match (common for lower-tier/friendly fixtures).
periods groups statistics by period (e.g. ALL, 1ST, 2ND); each period has named groups (e.g. "Match overview", "Shots") of home/away items.

Live monitoring

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

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /sofascore/event-statistics?id=14025013
Items in periods: 3
Fields filled in every checked item: 2

Field	Filled in, of 3 checked	Values in the sample
period	3	“ALL” and 2 other values
groups	3	median 7 entries

Request parameters

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

cURL example

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

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "event_id": 14025013,
    "source_url": "https://api.sofascore.com/api/v1/event/14025013/statistics",
    "fetched_at": "2026-07-08T16:45:00Z",
    "periods": [
      {
        "period": "ALL",
        "groups": [
          {
            "name": "Match overview",
            "items": [
              {
                "name": "Ball possession",
                "key": "ballPossession",
                "home": "61%",
                "away": "39%"
              }
            ]
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/sofascore.eventStatisticsResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	sofascore.EventStatisticsResponse	No
data.event_id	integer	No		SofaScore event id the statistics belong to.
data.fetched_at	string	No		Time the data was fetched, in UTC (RFC 3339).
data.periods	array	No		Statistics for the whole match and for each period.
data.periods[].groups	array	No		Statistic groups for the period.
data.periods[].groups[].items	array	No		Statistics in the group.
data.periods[].groups[].items[].away	string	No	39%	Away side's value as displayed, for example 39%.
data.periods[].groups[].items[].home	string	No	61%	Home side's value as displayed, for example 61%.
data.periods[].groups[].items[].key	string	No	ballPossession	Stable key for the statistic, for example `ballPossession`.
data.periods[].groups[].items[].name	string	No	Ball possession	Statistic name, for example "Ball possession".
data.periods[].groups[].name	string	No		Group name, for example "Match overview" or "Shots".
data.periods[].period	string	No	ALL	Period the statistics cover: `ALL`, `1ST` or `2ND`.
data.source_url	string	No		SofaScore URL the data was read from.
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/event-statistics?id=14025013" \
  -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 event statistics API

Returns one match's statistics (possession, shots, passes, and more, grouped and split by period). Returns 404 when SofaScore has no tracked statistics for the match.

GETapiKey2 credits/requestSofaScoresofascore.eventStatisticsResponseDoc/sofascore/event-statistics

Endpoint facts

Method: GET
API path: /sofascore/event-statistics
Auth: apiKey
Credits: 2 credits/request
Charged on: Successful 2xx responses only
Platform: SofaScore
Response schema: #/definitions/sofascore.eventStatisticsResponseDoc

SofaScore API Try SofaScore event statistics API in Playground SofaScore API documentation

How this endpoint behaves

Query parameters:

id: required. Numeric SofaScore event (match) id.

Notable response behavior:

Successful responses are cached for 10 minutes by default.
A genuine not-found response is cached for 30 minutes by default. Repeating the same request during that window returns the cached 404; upstream blocks and other failures are not cached by this policy.
Statistics can appear later for an upcoming or live match. A cached absence can delay their visibility by up to 30 minutes, so avoid immediate retries and recheck after that interval when new coverage is expected.
404 responses consume the plan’s request-rate allowance but do not consume credits.
Returns 404 when SofaScore has no tracked statistics for the match (common for lower-tier/friendly fixtures).
periods groups statistics by period (e.g. ALL, 1ST, 2ND); each period has named groups (e.g. "Match overview", "Shots") of home/away items.

Live monitoring

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

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /sofascore/event-statistics?id=14025013
Items in periods: 3
Fields filled in every checked item: 2

Field	Filled in, of 3 checked	Values in the sample
period	3	“ALL” and 2 other values
groups	3	median 7 entries

Request parameters

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

cURL example

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

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "event_id": 14025013,
    "source_url": "https://api.sofascore.com/api/v1/event/14025013/statistics",
    "fetched_at": "2026-07-08T16:45:00Z",
    "periods": [
      {
        "period": "ALL",
        "groups": [
          {
            "name": "Match overview",
            "items": [
              {
                "name": "Ball possession",
                "key": "ballPossession",
                "home": "61%",
                "away": "39%"
              }
            ]
          }
        ]
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/sofascore.eventStatisticsResponseDoc

Field	Type	Required	Example	Description
code	integer	No	200
data	sofascore.EventStatisticsResponse	No
data.event_id	integer	No		SofaScore event id the statistics belong to.
data.fetched_at	string	No		Time the data was fetched, in UTC (RFC 3339).
data.periods	array	No		Statistics for the whole match and for each period.
data.periods[].groups	array	No		Statistic groups for the period.
data.periods[].groups[].items	array	No		Statistics in the group.
data.periods[].groups[].items[].away	string	No	39%	Away side's value as displayed, for example 39%.
data.periods[].groups[].items[].home	string	No	61%	Home side's value as displayed, for example 61%.
data.periods[].groups[].items[].key	string	No	ballPossession	Stable key for the statistic, for example `ballPossession`.
data.periods[].groups[].items[].name	string	No	Ball possession	Statistic name, for example "Ball possession".
data.periods[].groups[].name	string	No		Group name, for example "Match overview" or "Shots".
data.periods[].period	string	No	ALL	Period the statistics cover: `ALL`, `1ST` or `2ND`.
data.source_url	string	No		SofaScore URL the data was read from.
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/event-statistics?id=14025013" \
  -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 event 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 event 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