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
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/cricbuzz-cricket/match-details-get-info API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-info?key=<API_KEY>&matchId=41881'
Query Result
Use Cases
- Open a match detail header after a user taps a fixture, showing the teams, series name, format and result line.
- Show the referee and three umpires with their countries on a match facts card.
- Enrich a venue directory with ground, city, country, ends and established year for each match you track.
- Check state and flags such as isfantasyenabled or islivestreamenabled before deciding which tabs to render for a match.
- Archive match metadata, including start and end timestamps, series id and match type, for completed games in a results database keyed by matchid.
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.