Docs menu
Cricinfo API endpoint
Cricinfo live matches API
Returns Cricinfo's current live-score list with no parameters, covering live, upcoming and recently completed matches. Each match has its title, format, state, status text, start date, series, both teams with scores, and a scorecard `url` you can pass to the match endpoint.
GETapiKey3 credits/requestCricinfocricinfo.liveMatchesResponseDoc
Cricinfo/cricinfo/liveEndpoint facts
- Method
- GET
- API path
- /cricinfo/live
- Auth
- apiKey
- Credits
- 3 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- Cricinfo
- Response schema
- #/definitions/cricinfo.liveMatchesResponseDoc
How this endpoint behaves
Query parameters: none.
Returns the current public live-score page snapshot, including live, upcoming, and recently completed match cards. Match URLs can be passed to cricinfo-match.
Live monitoring
- Monitored request
- GET /cricinfo/live
- Checks passed, 7 days to 14 Oct 2026
- 99.9%
- Median response time
- 2.02 s
Sampled response
- Request, 14 Oct 2026
- GET /cricinfo/live
- Items in matches
- 28
- Fields filled in every checked item
- 9
- Fields empty in some or all items
- 1
| Field | Filled in, of 28 checked | Values in the sample |
|---|---|---|
| id | 28 | |
| url | 28 | cricinfo.com |
| series | 28 | |
| title | 28 | “Plate Group” and 15 other values |
| format | 28 | TEST (18), T20 (8), ODI (2) |
| state | 28 | LIVE (20), PRE (7), POST (1) |
| status | 28 | Stumps (15), {{MATCH_START_TIME}} (7), Live (3) and 2 more |
| status_text | 27 | “Day 3 - Sikkim trail by 106 runs.” and 20 other values |
| start_date | 28 | 2026-10-11 to 2026-10-14 |
| teams | 28 | median 2 entries |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/cricinfo/live" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"msg": "OK",
"data": {
"count": 1,
"matches": [
{
"id": "1496583",
"title": "2nd Test",
"state": "LIVE",
"url": "https://www.cricinfo.com/series/.../full-scorecard"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/cricinfo.liveMatchesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | cricinfo.LiveMatchesResponse | No | ||||
| data.count | integer | No | ||||
| data.fetched_at | string | No | ||||
| data.matches | array | No | MatchSummary record, 20 fields: format, id, series, start_date, state, status, status_text, teams, title, url. Described under Cricinfo team profile API. | |||
| data.source_url | string | No | ||||
| msg | string | No | OK |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 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/cricinfo/live" \
-H "x-api-key: $CRAWLORA_API_KEY"