Docs menu

SofaScore API endpoint

SofaScore event player heatmap API

Returns one player's touch locations in a football match as `points`, each an `x` and `y` on SofaScore's 0-100 pitch scale. Get `player_id` from event-lineups. Returns 404 when SofaScore has no heatmap for that player in that match, which includes players who did not play, unstarted matches and sports other than football.

GETapiKey1 credit/requestSofaScoresofascore.eventPlayerHeatmapResponseDoc/sofascore/event-player-heatmap

Endpoint facts

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

SofaScore API Try SofaScore event player heatmap API in Playground SofaScore API documentation

How this endpoint behaves

Query parameters:

id: required. Numeric SofaScore event (match) id, e.g. 16363867.
player_id: required. Numeric SofaScore player id that played in the match, e.g. 839956. Get ids from the event-lineups endpoint.

Notable response behavior:

points are touches as an x and y on SofaScore's 0-100 pitch scale (whole numbers).
Returns 404 when SofaScore has no heatmap for that player in that match: a player who did not play, an unstarted match, or a sport other than football.

Live monitoring

Monitored request: GET /sofascore/event-player-heatmap?id=16363867&player_id=839956
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 0.88 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /sofascore/event-player-heatmap?id=16363867&player_id=839956
Items in points: 35
Fields filled in every checked item: 2

Field	Filled in, of 35 checked
x	35
y	35

Request parameters

Parameter	Type	Required	Description	Example
id	string	Yes	Numeric SofaScore event (match) id	16363867
player_id	string	Yes	Numeric SofaScore player id that played in the match	839956
x-api-key (header)	string	Yes	API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/sofascore/event-player-heatmap?id=16363867&player_id=839956" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "event_id": 16363867,
    "player_id": 839956,
    "source_url": "https://api.sofascore.com/api/v1/event/16363867/player/839956/heatmap",
    "fetched_at": "2026-07-08T00:00:00Z",
    "count": 8,
    "points": [
      {
        "x": 47,
        "y": 55
      },
      {
        "x": 56,
        "y": 77
      },
      {
        "x": 52,
        "y": 33
      },
      {
        "x": 48,
        "y": 47
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/sofascore.eventPlayerHeatmapResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	sofascore.EventPlayerHeatmapResponse	No
data.count	integer	No
data.event_id	integer	No	16363867
data.fetched_at	string	No
data.player_id	integer	No	839956
data.points	array	No
data.points[].x	number	No	47.6
data.points[].y	number	No	55.9
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/event-player-heatmap?id=16363867&player_id=839956" \
  -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 player heatmap API

GETapiKey1 credit/requestSofaScoresofascore.eventPlayerHeatmapResponseDoc/sofascore/event-player-heatmap

Endpoint facts

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

SofaScore API Try SofaScore event player heatmap API in Playground SofaScore API documentation

How this endpoint behaves

Query parameters:

id: required. Numeric SofaScore event (match) id, e.g. 16363867.
player_id: required. Numeric SofaScore player id that played in the match, e.g. 839956. Get ids from the event-lineups endpoint.

Notable response behavior:

points are touches as an x and y on SofaScore's 0-100 pitch scale (whole numbers).
Returns 404 when SofaScore has no heatmap for that player in that match: a player who did not play, an unstarted match, or a sport other than football.

Live monitoring

Monitored request: GET /sofascore/event-player-heatmap?id=16363867&player_id=839956
Checks passed, 7 days to 14 Oct 2026: 100%
Median response time: 0.88 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /sofascore/event-player-heatmap?id=16363867&player_id=839956
Items in points: 35
Fields filled in every checked item: 2

Field	Filled in, of 35 checked
x	35
y	35

Request parameters

Parameter	Type	Required	Description	Example
id	string	Yes	Numeric SofaScore event (match) id	16363867
player_id	string	Yes	Numeric SofaScore player id that played in the match	839956
x-api-key (header)	string	Yes	API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/sofascore/event-player-heatmap?id=16363867&player_id=839956" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "event_id": 16363867,
    "player_id": 839956,
    "source_url": "https://api.sofascore.com/api/v1/event/16363867/player/839956/heatmap",
    "fetched_at": "2026-07-08T00:00:00Z",
    "count": 8,
    "points": [
      {
        "x": 47,
        "y": 55
      },
      {
        "x": 56,
        "y": 77
      },
      {
        "x": 52,
        "y": 33
      },
      {
        "x": 48,
        "y": 47
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/sofascore.eventPlayerHeatmapResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	sofascore.EventPlayerHeatmapResponse	No
data.count	integer	No
data.event_id	integer	No	16363867
data.fetched_at	string	No
data.player_id	integer	No	839956
data.points	array	No
data.points[].x	number	No	47.6
data.points[].y	number	No	55.9
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/event-player-heatmap?id=16363867&player_id=839956" \
  -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 player heatmap 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 player heatmap 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