Docs menu
LiveScore API endpoint
LiveScore player profile API
Returns the public overview profile data for a player linked from a team squad, including player identity, current team/competition, career teams, recent-match context, and player league summary when supplied.
GETapiKey2 credits/requestLiveScorelivescore.responseDoc
LiveScore/livescore/playerEndpoint facts
- Method
- GET
- API path
- /livescore/player
- Auth
- apiKey
- Credits
- 2 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- LiveScore
- Response schema
- #/definitions/livescore.responseDoc
How this endpoint behaves
Query parameter: path is required and accepts the player page route copied from a player link in a public team squad, in the form season-stats/<player-slug>/<numeric-player-id>. Observed example: season-stats/radek-vitek/56253.
Notable response behavior: returns the public profile's initialPlayerData, including player identity, current team and competition, career teams, recent-match context, and a league summary when available. Player IDs and slugs are open-ended and are not a fixed enum. The profile's Stats tab loads a separate data flow and is not returned as a complete historical stats set by this endpoint.
Live monitoring
- Monitored request
- GET /livescore/player?path=season-stats%2Fradek-vitek%2F56253
- Checks passed, 7 days to 14 Oct 2026
- 97.9%
- Median response time
- 2.67 s
Sampled response
- Request, 14 Oct 2026
- GET /livescore/player?path=season-stats%2Fradek-vitek%2F56253
- Items in data.nextEventInitialData.tabs
- 9
- Fields filled in every checked item
- 2
- Fields empty in some or all items
- 3
| Field | Filled in, of 9 checked | Values in the sample |
|---|---|---|
| id | 9 | |
| name | 9 | “matchTabs.Info” and 7 other values |
| href | 8 | “highlights/” and 6 other values |
| isVisible | 5 | true in 0 of 5 |
| subId | 2 | “Livescore_6” |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| path | string | Yes | season-stats/player-slug/numeric-player-id path copied from a public LiveScore player link | season-stats/radek-vitek/56253 | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/livescore/player?path=season-stats%2Fradek-vitek%2F56253" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"source_url": "https://www.livescore.com/_next/data/<current-build-id>/en/season-stats/radek-vitek/56253.json",
"data": {
"player": {
"id": "56253",
"fullName": "Radek Vítek",
"teamName": "Middlesbrough"
},
"careerTeams": [],
"isError": false
}
}
}Request schema
No body schema
Response schema
#/definitions/livescore.responseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | livescore.sourceDataDoc | No | ||||
| data.data | object | No | ||||
| data.source_url | string | No | https://www.livescore.com/en/football/uefa-nations-league/league-b-group-3/austria-vs-israel/1738267/ | |||
| msg | string | No | OK |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/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/livescore/player?path=season-stats%2Fradek-vitek%2F56253" \
-H "x-api-key: $CRAWLORA_API_KEY"Shared guides
Related
More LiveScore endpoint docsLiveScore Scraper APILiveScore Competition API documentationLiveScore competition directory API documentationLiveScore live scores by sport API documentationLiveScore match statistics API documentationLiveScore match details API documentationLiveScore news article API documentation