Docs menu

LiveScore API endpoint

LiveScore Scores and Fixtures API

Returns either the unpaged full-day scoreboard or one cursor-paged UI-style section page for a supported sport and date. The response's Nav values indicate whether another page is available; use the last returned section Id as cursor. Sport ids are discoverable from /livescore/sports.

GETapiKey2 credits/requestLiveScorelivescore.responseDoc/livescore/scores

Endpoint facts

Method: GET
API path: /livescore/scores
Auth: apiKey
Credits: 2 credits/request
Charged on: Successful 2xx responses only
Platform: LiveScore
Response schema: #/definitions/livescore.responseDoc

LiveScore Scraper API Try LiveScore Scores and Fixtures API in Playground LiveScore API documentation

How this endpoint behaves

Query parameters:

sport (required): one of soccer, hockey, basketball, tennis, or cricket. Obtain the complete set from /api/v1/livescore/sports.
date (required): calendar date in YYYYMMDD format.
timezone_offset (optional): UTC offset in whole hours from -12 through 14; defaults to 0.
paging (optional): true returns one UI-style page; defaults to false, which requests the full-day feed.
cursor (optional): section ID from the previous paged response, formatted as s- followed by digits. Supplying a cursor enables paged mode.
direction (optional, paged mode): one of down or up; defaults to down. Direction requires paging=true or a cursor.

Paged responses preserve the upstream Ts, Nav, and Sctns fields. When Nav.Hn indicates another page, pass the last returned section's Id as cursor. The unpaged response includes the full-day sections in one response. The response shape and sport-specific fields follow LiveScore's current feed.

Live monitoring

Monitored request: GET /livescore/scores?date=20260926&sport=soccer&timezone_offset=0
Checks passed, 7 days to 14 Oct 2026: 99.7%
Median response time: 2.11 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /livescore/scores?date=20260926&sport=soccer&timezone_offset=0
Items in data.Sctns: 169
Fields filled in every checked item: 3

Field	Filled in, of 169 checked	Values in the sample
Id	169
Tp	169	1
Ts	169

Request parameters

Parameter	Type	Required	Default	Description	Example
sport	string	Yes		LiveScore sport id Allowed values: soccer, hockey, basketball, tennis, cricket.	soccer
date	string	Yes		Calendar date in YYYYMMDD format	20260926
timezone_offset	integer	No	0	UTC offset in hours from -12 through 14; defaults to 0 Minimum: -12. Maximum: 14.
paging	boolean	No	false (full-day feed	Request one UI-style page; defaults to false (full-day feed)
cursor	string	No		Section Id from the prior paged response, e.g. s-26031	s-26031
direction	string	No		Page direction in paged mode Allowed values: down, up.
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/livescore/scores?sport=soccer&date=20260926&paging=true&direction=down" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://prod-cdn-mev-api.lsmedia1.com/api/v2/date/soccer/20260926/0?direction=up&locale=en&paging=false",
    "data": {
      "Ts": 1790382940,
      "Nav": {
        "Hn": false
      },
      "Sctns": [
        {
          "Id": "s-24563",
          "Tp": "..."
        }
      ]
    }
  }
}

Request schema

No body schema

Response schema

#/definitions/livescore.responseDoc

Field	Type	Required	Example
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/scores?sport=soccer&date=20260926&paging=true&direction=down" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Shared guides

Authentication Errors and retries Rate limits and credits Pricing Acceptable use

More LiveScore endpoint docs LiveScore Scraper API LiveScore Competition API documentation LiveScore competition directory API documentation LiveScore live scores by sport API documentation LiveScore match statistics API documentation LiveScore match details API documentation LiveScore news article API documentation

Open in Playground Back to group

Docs menu

LiveScore API endpoint

LiveScore Scores and Fixtures API

GETapiKey2 credits/requestLiveScorelivescore.responseDoc/livescore/scores

Endpoint facts

Method: GET
API path: /livescore/scores
Auth: apiKey
Credits: 2 credits/request
Charged on: Successful 2xx responses only
Platform: LiveScore
Response schema: #/definitions/livescore.responseDoc

LiveScore Scraper API Try LiveScore Scores and Fixtures API in Playground LiveScore API documentation

How this endpoint behaves

Query parameters:

sport (required): one of soccer, hockey, basketball, tennis, or cricket. Obtain the complete set from /api/v1/livescore/sports.
date (required): calendar date in YYYYMMDD format.
timezone_offset (optional): UTC offset in whole hours from -12 through 14; defaults to 0.
paging (optional): true returns one UI-style page; defaults to false, which requests the full-day feed.
cursor (optional): section ID from the previous paged response, formatted as s- followed by digits. Supplying a cursor enables paged mode.
direction (optional, paged mode): one of down or up; defaults to down. Direction requires paging=true or a cursor.

Live monitoring

Monitored request: GET /livescore/scores?date=20260926&sport=soccer&timezone_offset=0
Checks passed, 7 days to 14 Oct 2026: 99.7%
Median response time: 2.11 s

Current status of every endpoint

Sampled response

Request, 14 Oct 2026: GET /livescore/scores?date=20260926&sport=soccer&timezone_offset=0
Items in data.Sctns: 169
Fields filled in every checked item: 3

Field	Filled in, of 169 checked	Values in the sample
Id	169
Tp	169	1
Ts	169

Request parameters

Parameter	Type	Required	Default	Description	Example
sport	string	Yes		LiveScore sport id Allowed values: soccer, hockey, basketball, tennis, cricket.	soccer
date	string	Yes		Calendar date in YYYYMMDD format	20260926
timezone_offset	integer	No	0	UTC offset in hours from -12 through 14; defaults to 0 Minimum: -12. Maximum: 14.
paging	boolean	No	false (full-day feed	Request one UI-style page; defaults to false (full-day feed)
cursor	string	No		Section Id from the prior paged response, e.g. s-26031	s-26031
direction	string	No		Page direction in paged mode Allowed values: down, up.
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/livescore/scores?sport=soccer&date=20260926&paging=true&direction=down" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "source_url": "https://prod-cdn-mev-api.lsmedia1.com/api/v2/date/soccer/20260926/0?direction=up&locale=en&paging=false",
    "data": {
      "Ts": 1790382940,
      "Nav": {
        "Hn": false
      },
      "Sctns": [
        {
          "Id": "s-24563",
          "Tp": "..."
        }
      ]
    }
  }
}

Request schema

No body schema

Response schema

#/definitions/livescore.responseDoc

Field	Type	Required	Example
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/scores?sport=soccer&date=20260926&paging=true&direction=down" \
  -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

LiveScore Scores and Fixtures 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

LiveScore Scores and Fixtures 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