cricket

List cricket series

The competitions we actually hold cricket matches for, with a match count and first/latest kickoff each, ordered by match count descending. Returns a JSON ARRAY in data. This endpoint returns a SINGLE PAGE (by default the complete list), so ?page= and ?offset= are rejected with a 400 rather than accepted and ignored. Use ?limit= to size it.

get/v1/cricket/series

Request

  • Base URL: https://api.bigballsdata.com
  • URL: https://api.bigballsdata.com/v1/cricket/series
  • Auth: one of:
    • API key in header x-api-key
    • HTTP bearer

Query parameters

limitinteger

Size the single page returned. Omit for the COMPLETE list, which is the default and has always been the behaviour of this endpoint.

countrystring

NOT a supported filter on this endpoint; there is no column to filter on. Sending it returns 400 rather than being ignored.

format'test' | 'odi' | 't20' | 't20i' | 'list_a' | 'ipl' | 'bbl' | 'psl'

NOT a supported filter on this endpoint; there is no column to filter on. Sending it returns 400 rather than being ignored.

Response

ok. data is an array of competitions, each with id, name, match_count, first_match and latest_match. meta.count is the number returned.

Example response

{
  "meta": {
    "date_window": {
      "timezone": "UTC",
      "start_utc": "2026-09-13T00:00:00.000Z",
      "end_utc": "2026-09-14T00:00:00.000Z"
    },
    "source": "official-league",
    "confidence": 0.95,
    "cache_age_ms": 4200,
    "request_id": "req_abc123",
    "note": "match_id is omitted on 380 of 380 rows in this response. The live feed behind them does not carry an id we can resolve to a stored match, so we return no id rather than one that will not work. For rows with ids you can call back into, use /v1/stored/matches with the same sport or league, for example /v1/stored/matches?league=epl."
  },
  "error": {
    "code": "NOT_FOUND"
  }
}

Changes

No recorded changes to this operation across all 3 revisions of this API.