Get cricket match info by match ID through the alternate info route

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). This is the second cataloged route for match info: the catalog states that its response is the same as the match-details/get-info operation and that this is the path the mobile app calls, so choose whichever of the two routes suits your client and standardize on it. The matchId comes from the match list, schedule, series, team and venue match 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, seriesstartdt, seriesenddt), match fields (matchid, matchdesc, matchformat, matchtype, startdate, enddate, daynight), state and result text (state, status, shortstatus, hidescorestatus, tossstatus), `team1` and `team2` objects with teamid, teamname and teamsname, a `referee` object, `umpire1` to `umpire3` objects with id, name and country, a `venueinfo` object (ground, city, country, ends, established, hometeam), an `appindex` block with a page title and web URL, and boolean flags such as isfantasyenabled and islivestreamenabled. Timestamps in the example are epoch milliseconds, and several text fields (tossstatus, statetitle, venue capacity) are empty strings. The example uses 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

Second route to the same overview The catalog describes this path as returning the same response as the original match-info operation, so a client can use either route for the match overview without changing how it parses the result.
Teams as id and name objects team1 and team2 each carry a teamid, a full teamname and a short teamsname such as AFGU19, which is enough to label both sides and to join with team endpoints.
Referee and three umpire slots The sample lists a referee plus umpire1, umpire2 and umpire3, each with an id, name and country code, so an officials panel can be filled from one request.
Ground, city and home-team facts The venueinfo object in the sample gives the ground name, city, country, ends, established year and home team, with other venue fields such as capacity left blank.
Toss line and result strings tossstatus, status, shortstatus and state sit side by side, so a header can show the toss text when present and the result sentence for a completed match.
Series window and match timestamps seriesstartdt, seriesenddt, startdate and enddate are epoch-millisecond numbers in the sample, which supports date ranges and tournament-window labels once converted in your own code.

Live API Demo

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

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-alt?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

How is this different from the match-details/get-info operation?

The catalog says the response is the same and that this alternate path is the one the mobile app calls. The only documented difference is the URL path, so pick one route for your client and avoid sending both requests for the same overview.

Which parameter does it need and where do I get it?

Only the numeric matchId in the URL path is required. Take it from the match list, schedule, series, team schedule or result, and venue match endpoints. The default 41881 is a sample identifier for a completed under-19 ODI group match.

Is the response verified by a probe call?

No. No probe was recorded for this operation, so the field list comes from a source response example. Confirm field names, casing and value types against a real response for your own matchId before relying on them.

Is toss information always filled in?

Not in the sample. tossstatus is an empty string there, even though the match is complete. Treat an empty string as not available rather than as a toss result.

Does it include innings scores or commentary?

The sample shows result text such as the status and shortstatus strings, but no innings score objects, batting lines or commentary entries. Use the scorecard, live score and commentary operations for those.

How are start and end times formatted?

startdate and enddate are numbers in the sample that look like epoch milliseconds, for example 1640410200000. This is unconfirmed by a probe, so convert them in your own code and check against a live response.

Related operations

Guides

View Subscription Plans →