Get cricket match info by match ID

View all Cricket Live Scores, Scorecards & Stats API endpoints →

Returns the overview facts for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). The matchId comes from the match, schedule, series, team or venue listing endpoints. No probe call was recorded for this operation, so the fields below come from a source response example and are unverified. In that example (a completed under-19 ODI group match) the response includes series fields (seriesid, seriesname, seriestype, seriesstartdt, seriesenddt), match fields (matchid, matchdesc, matchformat, matchtype, startdate, enddate), state fields (state, status, shortstatus, hidescorestatus), `team1` and `team2` objects, `referee`, `umpire1` to `umpire3`, a `venueinfo` object (ground, city, country, ends, established, hometeam) and boolean flags such as isfantasyenabled and islivestreamenabled. Timestamps are epoch milliseconds and some text fields are empty strings. The example shows lowercase field names, so confirm key casing against a real response. This is a match overview, not a scorecard or a commentary feed.

API Features

One-call match overview A single matchId request returns the header-level facts for a match, which suits a detail page opened from a list without pulling the full scorecard.
Series and format context Series id and name, match description, format (such as ODI) and match type tell your interface which competition and level of cricket the game belongs to.
Referee and umpire records The example lists the match referee and up to three umpires, each with an id, name and country code, ready for an officials panel.
Embedded venue profile venueinfo carries ground name, city, country, ends, home team and established year, so venue facts arrive with the match instead of needing a separate venue request.
Result and availability flags State, status and short status text sit beside boolean flags for fantasy, live stream and poll availability, letting you decide which modules to show for a match.

Live API Demo

GET /api/project/cricbuzz-cricket/match-details-get-info

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-info?key=<API_KEY>&matchId=41881'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Where do I get the matchId for this endpoint?

Use the matchId value returned by the match listing, schedule, series match, team schedule or result, and venue match endpoints. The default 41881 is an example identifier for a completed match.

Does this endpoint return the scorecard or commentary?

No. It returns overview facts such as teams, series, venue, officials and status text. Innings scores, ball data and commentary come from separate match-detail endpoints.

Why are some fields empty or zero?

In the source example, values such as toss status, venue capacity and image ids are empty strings or 0. Coverage varies by match, so treat blank or zero values as not available instead of as real data.

How are start and end times formatted?

In the source example, startdate and enddate are epoch-millisecond numbers. This was not confirmed by a probe call, so convert them in your own code and verify against a real response.

Are the response keys lowercase or camelCase?

The source example shows lowercase keys such as matchid and venueinfo, while other endpoints show camelCase. Because no probe was recorded, parse keys defensively and confirm the casing in a live response.

Related operations

Guides

View Subscription Plans →