Docs menu
Cricinfo API endpoint
Get current Cricinfo match scores API
Returns the current match cards in Cricinfo's public homepage snapshot, including match state, scores, and canonical scorecard URLs. This is a point-in-time feed, not a fixture archive or streaming subscription.
GETapiKey3 credits/requestCricinfocricinfo.scoresResponseDoc
Cricinfo/cricinfo/scoresEndpoint facts
- Method
- GET
- API path
- /cricinfo/scores
- Auth
- apiKey
- Credits
- 3 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- Cricinfo
- Response schema
- #/definitions/cricinfo.scoresResponseDoc
How this endpoint behaves
There are no query parameters. The response is a point-in-time collection of
match cards on Cricinfo's public homepage, with a canonical url for each
scorecard. It is not a fixture archive or a streaming subscription.
Live monitoring
- Monitored request
- GET /cricinfo/scores
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 2.23 s
Sampled response
- Request, 14 Oct 2026
- GET /cricinfo/scores
- Items in matches
- 6
- Fields filled in every checked item
- 10
| Field | Filled in, of 6 checked | Values in the sample |
|---|---|---|
| id | 6 | |
| url | 6 | cricinfo.com |
| series | 6 | |
| title | 6 | “4th T20I” and 5 other values |
| format | 6 | T20 (2), ODI (2), TEST (2) |
| state | 6 | POST (4), PRE (1), LIVE (1) |
| status | 6 | RESULT (4), {{MATCH_START_TIME}} (1), Live (1) |
| status_text | 6 | “Match yet to begin” and 5 other values |
| start_date | 6 | 2026-10-09 to 2026-10-14 |
| teams | 6 | 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/scores" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"msg": "OK",
"data": {
"count": 1,
"matches": [
{
"id": "1496583",
"url": "https://www.cricinfo.com/series/pakistan-tour-in-england-2026-1496563/england-vs-pakistan-2nd-test-1496583/full-scorecard",
"series": {
"id": "1496563",
"name": "Pakistan tour of England",
"slug": "pakistan-tour-in-england-2026"
},
"title": "2nd Test",
"state": "LIVE",
"status_text": "Day 3 - Session 1",
"teams": [
{
"name": "England",
"score": "290 & 81/3",
"home": true,
"live": true
},
{
"name": "Pakistan",
"score": "110",
"home": false,
"live": false
}
]
}
]
}
}Request schema
No body schema
Response schema
#/definitions/cricinfo.scoresResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | cricinfo.ScoresResponse | 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/scores" \
-H "x-api-key: $CRAWLORA_API_KEY"