🏏

Cricket Live Scores, Scorecards & Stats API

Find live, recent and upcoming cricket matches, then carry each match ID into scorecards, commentary, innings charts, series, teams, players, rankings, news and IPL/WPL auction data. Coverage varies by competition, and some resources return no content when a feed has nothing to show.

Open the standalone cricket demo

List the matches in the live feed

Replace <API_KEY> with your authorized platform API key from the dashboard. The request URL contains your key, so keep it out of shared links, screenshots and logs.

This read-only example calls the live match list, which takes no inputs. It returned a successful response when it was recorded, but the feed changes continuously and can be thin between fixtures, so a populated response is not guaranteed. Copy a matchId from a returned match before you open a scorecard or commentary form. Loading the page, navigating, opening panels or copying an example sends no data request. Submit a request only when you intend to run it.

Base URL https://api.opendata-api.com

curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-live?key=<API_KEY>'
Match IDs, innings and paging cursors
  • Most match-detail, commentary, chart and fantasy operations need a numeric matchId. Take it from the matchId field in a live, recent, upcoming, schedule, series-match, team-result, team-schedule or venue-match response instead of typing one from memory. The IDs prefilled in the forms are only sample values, so replace them with an ID from a response you have just read, and keep each ID together with the series and format it came from.
  • The Hundred has its own scorecard, mini scorecard, commentary, player commentary, highlights and leanback operations, separate from the standard routes. Use a Hundred operation only for a match played in that format, and do not assume the two routes are interchangeable or return the same fields. Inspect the response for the specific match before you build a parser around either route.
  • Identifiers are not interchangeable. Keep matchId, seriesId, squadId, teamId, playerId, venueId, innings numbers and image IDs together with the operation that returned them, and add the letter c in front of an image id only when requesting an image. Paging cursors such as tms, lastId, lastTime, itemOrder, pt and timestamp must be copied unchanged from an earlier response, never invented.
  • Auction operations are scoped by tournament and year. Call the seasons operation first, then send the same tournament, ipl or wpl, and the same year to the player and team operations so every result belongs to one edition. Do not assume an example year is current or that a year exists for both tournaments, and note that the currency field changes only how prices are displayed.
  • Some resources return no content when a feed has nothing to show. This is most likely for fantasy research on matches without coverage, season history or points tables for series that lack them, and paging that reaches the start of an innings. Treat it as a normal empty state, not as a failed request or a permanent outage, show a clear no-data message, and do not retry in a tight loop.

Check status and message before reading match data

Read the HTTP status separately from the gateway's code, message and data business status. Gateway code 200 means the gateway reports business success, but HTTP 200 alone does not prove that a match has data. Inside data, a feed can hold empty groups or placeholder entries that are not matches, and some resources answer with no content. Keep an empty result, a request failure and a populated match as three different states.

Choose a cricket data task
Find live, recent and upcoming matches

Start here to discover matches. The live, recent and upcoming feeds take no inputs, the list operation takes a type of live, recent or upcoming, and the schedule operation takes a competition type of international, league, domestic or women plus an optional lastTime cursor copied from a previous response. Every match carries a matchId that the match-detail operations need. Feeds are grouped by competition and series, and a view can come back with no matches.

Read scorecards, match info and squads

Every operation here takes a matchId copied from a match list, schedule, series, team or venue response, and the single-team squad also needs a teamId taken from the match info. Use the full scorecard for batting rows, the mini scorecard or live score panel for a compact state, and the Hundred variants only for matches in that format. Upcoming or abandoned fixtures can return sparse bodies, so treat every field as coverage dependent.

Follow commentary and highlights by innings

Commentary and highlights start from a matchId. Add an innings number as iid to narrow to one innings, and send back the epoch-millisecond timestamp of a returned commentary entry as tms to load the next page. Player commentary requires iid, a playerId and a type of batting or bowling. Highlights accept an optional htype for fours, sixes or wickets. Commentary depth depends on the match, so an empty feed is possible.

Chart ball, over and partnership progress

These operations feed innings charts and all need a matchId. The ball graph and overs narrow by innings through iid, over details also require a tms timestamp copied from the overs response, and restrictInningsId stops overs paging at the start of the chosen innings. The runs-per-over and partnership graphs take only the match. Inspect a live response for your match before drawing, because graph structures are not guaranteed for every fixture.

Explore teams, results, fixtures and venues

List teams by category first and keep the returned teamId for rosters, results, schedules and statistics. Team statistics also need a statsType and accept optional match type, opponent, team and year narrowing. Venue operations take a venueId taken from a series venues response and return ground details, scheduled matches or ground statistics. A venue or team with nothing scheduled can return no content.

Compare ICC rankings, standings and record leaderboards

Rankings need a category of batsmen, bowlers, allrounders or teams and a format of test, odi or t20, and isWomen set to 1 requests the women's table, which has no ODI view. ICC standings take a competition number of 1 for the World Test Championship or 2 for the World Cup Super League, with an optional seasonId from the returned seasons. Read the record filters first to learn the statsType values the records operation accepts.

Collect news by feed, category, topic, author, team, player or series

The headline feed takes a type of index or premiumIndex and pages with lastId, the id of the last story returned. List the categories and topics first to get the ids their story lists need, and read an author id from a news detail response. Team, player and series news take the matching teamId, playerId or seriesId from those operations. Confirm you may store and republish article text before building an archive.

Browse photo galleries, images and video items

The gallery index pages with the publishedTime of the last gallery as pt, and a gallery lookup takes a galleryId from that index. A single image takes an imageId with the letter c placed before an image id from another response, plus optional d quality and p size choices, and it targets an image file rather than a JSON document. Buzz items need the itemID and itemType copied from the same feed entry, and match videos take a matchId. Check usage rights before republishing media.

Explore IPL and WPL auction seasons, players and teams

Call the seasons operation first to see the supported tournaments, ipl or wpl, and their years, then send the same tournament and year to every other auction operation so results come from one edition. Player lists take a status of completed, upcoming or live. Player, team and team-bid lookups need a playerId or teamId from those lists. The currency field only changes how prices are formatted.

Auctions

GET /api/project/cricbuzz-cricket/auction-get-player

Get a player's auction record for a selected edition

Full docs β†’
Details

Retrieve auction details for a numeric playerId, obtained from the auction player list. The optional tournament query selects ipl or wpl, year selects the auction year as a string, and currency selects price formatting. The documented defaults are playerId 10420, tournament ipl, year 2026 and currency INR. Currency examples include INR, USD and GBP; unrecognized currency values are documented to return prices without a currency symbol. The unverified documentation example contains playerId, playerName, playerImageId, country, countryId, role, cappedStatus, isPlayerOverseas, season, auctionStatus, auctionPrice, basePrice, playsFor, playsForTeam, teamImageId, totalEarnings, earningsDisclaimer and updatedTime. Its playerIntro is an array of text, and auctionEarnings is an array with year, auctionPrice, playsFor, playsForTeam, teamImageId and trend fields. The example also includes id and appIndex with seoTitle and webURL. No response for this operation was observed in the saved probe evidence; these example fields do not establish guaranteed field availability, historical coverage or update frequency.

Explicitly submit this cricket request 1 required Β· 3 optional
ParameterInValue
path
query
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-get-player?key=<API_KEY>&playerId=10420&currency=INR&tournament=ipl&year=2026'
GET /api/project/cricbuzz-cricket/auction-search-players

Search auction players by name within an edition

Full docs β†’
Details

Search auction participants with the required plrN name query; the documented example is Kohli. Use the optional tournament query (ipl or wpl) and year string to select the auction edition, with configured defaults ipl and 2026. Edition values are documented by the auction-seasons endpoint. Matching rules, pagination and completeness are not specified. The unverified documentation example returns auctionPlayersList plus auctionTitle, liveBlogId and appIndex. Each example list entry contains playerId, playerName, playerImageId, country, countryId, role, cappedStatus, season, auctionStatus, auctionPrice, basePrice, playsFor, playsForTeam, teamImageId, totalEarnings, updatedTime, id and a playerIntro text array. Use a returned playerId for a subsequent auction-detail lookup. This search does not declare a currency parameter. No response for this operation was observed in the saved probe evidence; the documented example does not verify which fields are always present or the behavior of a query with no matching player.

Explicitly submit this cricket request 1 required Β· 2 optional
ParameterInValue
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-search-players?key=<API_KEY>&plrN=Kohli&tournament=ipl&year=2026'
GET /api/project/cricbuzz-cricket/auction-list-players

List auction players by completed, upcoming or live state

Full docs β†’
Details

Retrieve the auction player list for a required status: completed covers auction results including sold, unsold, retained and RTM; upcoming covers players yet to be auctioned; live covers the current auction state with editor picks. The configured status is completed, tournament is ipl, year is the string 2026 and currency is INR. Optional filters are cap (Capped or Uncapped), countryId, role (Batter, Bowler, Allrounder or WK-Batter) and teamId. Use sort from a response-provided sort ID, or use sortField with sortDirection (ASC or DESC) from the same documented sort option. Leave timestamp unset for the first page; for another page, pass the last returned player's updatedTime as the numeric timestamp parameter. No timestamp unit or page-size parameter is documented. The truncated, unverified documentation example shows appIndex with seoTitle and webURL and an auctionPlayersList array. Visible player fields include playerId, playerName, playerImageId, role, country, countryId, cappedStatus, season, auctionStatus, auctionPrice, basePrice, playsFor, playsForTeam, teamImageId, totalEarnings, updatedTime, id and a playerIntro text array. The excerpt also contains editorPickLabel, isEditorPick, isPlayerOverseas, twitterArticleId and videoAnalysisId on some entries; these fields are not established as universal. Parameter documentation separately references filters, filter.team, sortFilter.sort[].id and sort.options with value1/value2 as input-discovery fields. No response for this operation was observed in the saved probe evidence, and the truncated example does not confirm complete list coverage, response structure for every status or live-update frequency.

Explicitly submit this cricket request 1 required Β· 11 optional
ParameterInValue
path
query
query
query
Optional filters and paging cursors (8)
ParameterInValue
query
query
query
query
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-list-players?key=<API_KEY>&status=completed&currency=INR&tournament=ipl&year=2026'
GET /api/project/cricbuzz-cricket/auction-list-seasons

List auction tournaments, years and default selections

Full docs β†’
Details

Discover auction tournament identifiers, available years and default selections before choosing an edition for team or player queries. The optional tournament and year query parameters use identifiers from seasons.tournament.tournaments and values from seasons.year; their documented request defaults are ipl and 2026. A saved successful HTTP 200 check confirmed a JSON object containing seasons.tournament as an object, seasons.year as an array, defaults as an object and appIndex as an object. The source example further documents seasons.tournament.tournaments entries with identifier and title, defaults.tournament with identifier and title, defaults.year, and appIndex.seoTitle and appIndex.webURL as navigation metadata. These nested example fields and values were not individually verified by that check. Use returned selections rather than assuming that a documented example year is the current default or that every listed year is available for both IPL and WPL. This endpoint discovers editions; it does not return purchased-player rosters or team budgets.

Explicitly submit this cricket request 0 required Β· 2 optional
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-list-seasons?key=<API_KEY>&tournament=ipl&year=2026'
GET /api/project/cricbuzz-cricket/auction-get-team

Get one auction team's purchased players by role

Full docs β†’
Details

Retrieve the documented purchased-player view for one auction team, grouped by role and accompanied by team strategy information where supplied. The required numeric teamId path parameter comes from the auction team list; 58 is the documented CSK example. Optional currency, tournament and year query parameters select price display and auction context, with documented defaults INR, ipl and 2026. No saved technical probe covers this operation. Its unverified, truncated source example shows an allroundersList array with playerId, playerName, playerImageId, country, countryId, role, cappedStatus, isPlayerOverseas, playsFor, playsForTeam, teamImageId and season. Purchase-related fields shown include auctionStatus, auctionPrice, basePrice, totalEarnings and updatedTime. Prices are display strings, and totalEarnings may contain a placeholder such as --; do not assume all monetary fields are numeric. The source description documents role grouping and team strategy, but the truncated example does not establish the complete set of role groups or the strategy field structure. Treat this as an auction-purchase record for the selected edition, not as a complete retained squad, a confirmed match-day lineup or a prediction of team performance. Currency examples are INR, USD and GBP; unknown currency values are documented to return prices without a currency symbol.

Explicitly submit this cricket request 1 required Β· 3 optional
ParameterInValue
path
query
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-get-team?key=<API_KEY>&teamId=58&currency=INR&tournament=ipl&year=2026'
GET /api/project/cricbuzz-cricket/auction-list-teams

List auction teams with purse, spending and player slots

Full docs β†’
Details

Retrieve the documented auction team list for a selected IPL or WPL edition, with team identifiers, purse amounts, spending and player-slot fields. All query parameters are optional. currency, tournament and year have documented request defaults of INR, ipl and 2026. Discover tournament and year choices through the auction seasons endpoint. No saved technical probe covers this operation. Its unverified, truncated source example shows an auctionTeamsList array. Team entries include teamId, teamName, teamFullName, teamImageId and season; monetary fields include totalPurse, purseAtStart, retentionSpent, auctionSpend and purseRemaining. Player-related fields shown are playersBought, maxPlayers, maxIndianPlayers, maxOverseasPlayers, playerSlotsIndians and playerSlotsOverseas. The example presents monetary amounts as formatted strings and player counts or limits as numbers. Do not infer remaining vacancies or budget arithmetic solely from field names. appIndex is also shown with seoTitle and webURL navigation metadata. The parameter documentation describes sort as an option ID from sortFilter.sort[].id. Alternatively, sortField and sortDirection use value1 and value2 from the same sort.options entry, with ASC or DESC as direction values. Those sorting structures are not visible in the truncated example and have not been verified by a saved probe; use returned options when available instead of assuming arbitrary field names are accepted. This is an edition-scoped team budget view, not a guaranteed live balance feed or a purchased-player roster.

Explicitly submit this cricket request 0 required Β· 6 optional
ParameterInValue
query
query
Optional filters and paging cursors (4)
ParameterInValue
query
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-list-teams?key=<API_KEY>&currency=INR&tournament=ipl&year=2026'
GET /api/project/cricbuzz-cricket/auction-get-team-bids

Get the players a team bid on during a cricket auction.

Full docs β†’
Details

Retrieve auction bidding interest for the required numeric teamId, obtained from the auction teams listing. Optional currency controls price formatting; documented examples are INR, USD and GBP, while unknown currency values return prices without a currency symbol. Select tournament using ipl or wpl and year using an auction season year. The supplied defaults are teamId 58, currency INR, tournament ipl and year 2026. The unverified source example contains playersBidOn, season and teamId. Each illustrated playersBidOn record contains playerId, playerImageId, playerName, country, role, status, latestBid and totalBids. latestBid is illustrated as a string and totalBids as a number. This is a list of players the team bid on, not necessarily its purchases or a complete chronological bid history. No response was observed for this operation in the supplied probe evidence, so the example fields are documented illustrations rather than a verified response contract.

Explicitly submit this cricket request 1 required Β· 3 optional
ParameterInValue
path
query
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/auction-get-team-bids?key=<API_KEY>&teamId=58&currency=INR&tournament=ipl&year=2026'

Videos

GET /api/project/cricbuzz-cricket/videos-get-buzz-item

Get details for one selected cricket Buzz item.

Full docs β†’
Details

Retrieve a single short-form Buzz item using the required numeric itemID and string itemType query parameters. Copy itemID from a feed item's itemId field and itemType from that same item; the supplied examples are 1090351 and video. The unverified 200 source example wraps the result in buzzItem and illustrates itemId, itemType, itemOrder, title, embedTitle, imageId, timeStamp, shareURL and videoUrl, together with isPremiumFree, isloginRequired and planId access metadata. timeStamp units and the meaning of planId values are not specified by the supplied evidence. A 204 no-content case is also documented. No response was observed for this operation in the supplied probe evidence, so the example fields are not independently verified. An illustrated videoUrl does not guarantee playable media or grant redistribution rights; assess access requirements and content-use rights separately.

Explicitly submit this cricket request 2 required Β· 0 optional
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/videos-get-buzz-item?key=<API_KEY>&itemID=1090351&itemType=video'
GET /api/project/cricbuzz-cricket/videos-list-buzz

List the newest-first cricket Buzz feed with itemOrder pagination.

Full docs β†’
Details

Request the short-form Buzz discovery feed, documented as newest first and mixed with advertising slots. The only input is optional numeric itemOrder: omit it for the first page, then use the itemOrder value from the last returned content item to request the next page. The documentation gives 6879 as an example, not a default or page number. The unverified source excerpt starts with an array whose complete visible entries contain either buzzItem or ad. Visible buzzItem fields are itemId, itemType, itemOrder, title, embedTitle, imageId, timeStamp, shareURL, videoUrl, isPremiumFree, isloginRequired and planId. Visible ad fields are layout, name and position. The supplied source excerpt is incomplete and no response was observed for this operation in the probe evidence, so these structures are illustrative rather than a verified full response contract. Pass a selected content item's itemId as itemID, along with its itemType, to the single-item lookup. Do not treat ad slots as video records or assume feed discovery grants playback access or content-use rights.

Explicitly submit this cricket request 0 required Β· 1 optional
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/videos-list-buzz?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/videos-list-by-match

List analysis, preview and match-forecast video items attached to one cricket match by matchId

Full docs β†’
Details

Returns the video items related to a single cricket match. matchId is required and is a number: use the matchId value from the match list, match schedule, series matches, team schedule, team results or venue matches endpoints of this product. Three optional query inputs are supported. timestamp is a paging cursor: leave it empty for the first page, or pass the commTimestamp of the last video from the previous response to load the next page. videoType filters on the videoType field of returned videos (for example Analysis or Match Forecast); leave it empty for all types, and a type with no videos returns 204. multilangEnabled is a boolean that the source says the original app always sends as true and that had no visible effect in testing. The source 200 example is a videoList array. Each item carries headline, videoId (a number), itemId and mappingId (strings), videoType, language, imageId, commTimestamp (a string), videoUrl, appLinkUrl, adTag and infraType, a category array of id, imageID and name objects, a tags array of itemId, itemName and itemType objects (series, match, team and player in the example), and freeMinuteBeginMessage and freeMinuteExpiredMessage objects that are empty in the example. A 204 example with an empty object is also documented. No live probe was recorded for this endpoint, and the supplied 200 example is cut off after the first few items, so every field is a source-example field and optional ones are coverage-dependent.

Explicitly submit this cricket request 1 required Β· 3 optional
ParameterInValue
query
Optional filters and paging cursors (3)
ParameterInValue
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/videos-list-by-match?key=<API_KEY>&matchId=151543&multilangEnabled=true'

Fantasy

GET /api/project/cricbuzz-cricket/fantasy-list-players

List a cricket match's players grouped by role with fantasy badges.

Full docs β†’
Details

Retrieve the player research list for one cricket match, grouped by role and annotated with fantasy badges such as In form. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from a truncated, unverified source example and are documented illustrations, not a verified contract. The example shows a disclaimer array, a legends array and a playerStyles array, plus playersByRole. Each playersByRole entry has a role label (for example WICKET KEEPERS) and a players array. Each illustrated player has id, name, teamName, teamShortName, teamFlagId, faceImageId, isVisible, a playerStyle array of code/label pairs and a badges array; some players also carry a short description with form or matchup commentary. Each legends entry has a code, label and desc, and some entries add color and isSeparate fields. Badge labels illustrated include In form, Injured, Off Field Pick, Ideal for Conditions and C/VC. The list is a role-grouped research roster, not a confirmed starting XI and not a fantasy points total, and availability depends on coverage for the chosen match.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-list-players?key=<API_KEY>&matchId=151543'
GET /api/project/cricbuzz-cricket/fantasy-get-expert-corner

Get expert analysis and key-player picks for a cricket match.

Full docs β†’
Details

Retrieve the expert analysis section for one cricket match. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from a truncated, unverified source example and are documented illustrations, not a verified contract. The example shows an authorNote array whose entries have a name (for example Quick Take) and a note with a short written match view, a keyPlayer array of role groups, and a disclaimer array of informational statements. Each keyPlayer entry has a role label (for example WICKET KEEPERS or BATTERS) and a players array. Each illustrated player has id, name, teamName, teamShortName, teamFlagId, faceImageId, isVisible, a playerStyle array of code/label pairs, a badges array of code/label/desc objects and a description with matchup reasoning. The content is editorial analysis supplied by the source for human review; it is not a guaranteed recommendation, a prediction of the result or a fantasy points total, and availability depends on coverage for the chosen match.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-expert-corner?key=<API_KEY>&matchId=151543'
GET /api/project/cricbuzz-cricket/fantasy-get-match-forecast

Get the fantasy guide home for a cricket match with forecast video and section links.

Full docs β†’
Details

Retrieve the fantasy guide landing data for one cricket match, described as the guide home with a win forecast and key sections. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from an unverified source example and are documented illustrations, not a verified contract. The example contains the match header fields id, title, subtitle, matchDesc, seriesName, seriesShortName, team1ShortName and team2ShortName, a tabs array whose entries have an id, a path and a title and point to the Expert's Corner, Matchups, Venue and All Players sections, and a video object for a Match Forecast clip. The illustrated video object includes id, title, description, durationStr, videoType, videoFormat, language, source, publishedTime, imageId, category, tags and tagItems that link the clip to the series, match, teams and players. The example shows no numeric win-probability fields, so treat any forecast as source-supplied material rather than calibrated odds or an assured result. Video fields can include a signed playback link that is not meant to be stored or shared, and coverage depends on the chosen match.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-match-forecast?key=<API_KEY>&matchId=151543'
GET /api/project/cricbuzz-cricket/fantasy-get-matchups

Get match-specific batter-versus-bowler matchup stat cards for a cricket match.

Full docs β†’
Details

Retrieve match-specific batter-versus-bowler matchup cards for one cricket match. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from a truncated, unverified source example and are documented illustrations, not a verified contract. The example returns a cards array. Each card has cardHeading (for example a venue, opposition or player-versus-player title), cardLabel (a format label such as ODIs), cardType (playerStatsCard), playerOneImageId, playerTwoImageId and a subCard array. Each subCard entry has a subCardHeading naming a player and a stats array of label and value pairs, with every value returned as a string. Illustrated stat labels include Matches, Innings, Runs, Highest, Average, 100s, 50s, 0s, Wickets, Best figures, Economy, Strike-rate and 4-fers on the venue and opposition cards, and Runs scored, Balls faced and Dismissals on the player-versus-player card. The example is cut off inside that last card, so any further fields are not documented. The cards are match-scoped research context, not a complete all-time head-to-head record, a prediction or a fantasy points total, and availability depends on coverage for the chosen match.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-matchups?key=<API_KEY>&matchId=151543'
GET /api/project/cricbuzz-cricket/fantasy-get-player-info

Get a player's fantasy research profile, badges and key info within one cricket match.

Full docs β†’
Details

Retrieve the fantasy research profile of one player within one cricket match. Both inputs are required numbers. playerId goes in the path and is taken from the id field of a player returned by the fantasy match-players endpoint (/forecast/v1/allPlayers/{matchId}). matchId goes in the query and is taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied defaults are playerId 8733 and matchId 151543. No response was observed for this operation in the supplied probe evidence, so the fields below come from an unverified source example and are documented illustrations, not a verified contract. The example is a single object with id, fullName, country, role, batStyle, bowlStyle, stockDelivery, battingPosition, battingRole, faceImageId, a badges array of code and label pairs (for example In form and Ideal for Conditions), a keyInfo array of short scouting sentences and a disclaimer array of informational notes. In the example bowlStyle and stockDelivery are empty strings for a batter, so treat the bowling fields as optional. The profile is match-context fantasy research, not a full biography, a career statistics page, a projected fantasy points total or a confirmed selection, and availability depends on coverage for the chosen match.

Explicitly submit this cricket request 2 required Β· 0 optional
ParameterInValue
path
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-player-info?key=<API_KEY>&playerId=8733&matchId=151543'
GET /api/project/cricbuzz-cricket/fantasy-get-prediction-hub

List upcoming cricket matches with pre-match forecast text, or an empty result when none.

Full docs β†’
Details

Retrieve the fantasy prediction hub, a list of upcoming cricket matches with pre-match forecast information. The endpoint takes no parameters. The catalog notes that it returned HTTP 204 (no content) at the time of testing, so a call can come back with an empty body and clients should treat that as a no-content state, not as an error or a permanent outage. No response body was observed in the supplied probe evidence. The fields below come from an unverified source example filed under the 204 status and are documented illustrations, not a verified contract. The example holds a matches array. Each entry has matchId, matchName, matchFormat, state, startdt, customStatus, seriesId, seriesName and seriesCategory, plus team1 and team2 objects with id, name, shortName, imageId and color. It also shows a cbPrediction object with a label and a text value, the flags isForecastEnabled and isProbabilityEnabled, a fillerText message, highlightedTeamId, and two link fields, forecastUrl and livePredictionUrl, which appear to be app deep links rather than web addresses. The prediction text is editorial forecast copy, not calibrated betting odds or a guaranteed result, and which matches appear depends on coverage.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-prediction-hub?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/fantasy-get-venue-info

Get venue and pitch research for one cricket match: ground details, pitch notes, par score, innings averages and pace-versus-spin cards.

Full docs β†’
Details

Retrieve venue and pitch context for one cricket match from the fantasy research feed. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. The endpoint description states that most matches without fantasy coverage return HTTP 204, so an empty result is a normal outcome rather than an error. No response was observed for this operation in the supplied probe evidence, so the fields below come from a source example for a covered match and are documented illustrations, not a verified contract. The example 200 body contains groundName, city, country and an id value; groundDetails and pitchDetails arrays of heading and content text pairs (for example boundary dimensions and a written pitch assessment); runsExpected, a heading and content pair such as a par score; averageScores, a card with a heading, a label naming how many matches were counted and a values list of first-innings and second-innings averages; cards, statistic cards such as pace versus spin with cardHeading, cardLabel, cardType and subCard groups of label and value stats (Matches, Wickets, Best figures, Economy, Strike-rate, Dot%); recentMatches, a card with headers and rows where each row has a followUpLinkText slug and a values list that starts with a match ID, then a team label and the two innings scores; and a disclaimer array of informational notices. In the example every number is returned as a string. The data is pre-match research context, not a guaranteed pitch behaviour, a fantasy points total or betting odds, and availability depends on coverage for the chosen match.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-venue-info?key=<API_KEY>&matchId=151543'
GET /api/project/cricbuzz-cricket/fantasy-get-partner-predictions

Get the supplied pre-match win forecast line for one cricket match, returned as a labeled text value.

Full docs β†’
Details

Retrieve the pre-match win forecast supplied for one cricket match. The only input is the required numeric path parameter matchId, taken from the matchId field returned by the match list, schedule, series match, team schedule, team result or venue match endpoints. The supplied default is 151543. The endpoint is documented as a pre-match win prediction. No response was observed for this operation in the supplied probe evidence, so the fields below come from a source example and are documented illustrations, not a verified contract. The example 200 body is an object with a cbPrediction object holding two strings: label, a heading for the forecast (the example reads CB Prematch Forecast), and value, a single text line that names the favoured side and its win probability in the same string (the example reads IND Wins (80% Probability)). The probability is embedded in text rather than split into separate numeric fields. The source also lists a 204 response whose example body is an empty object, which indicates that a match without a supplied forecast can return no content. The forecast is informational material for one match, not a statement of accuracy, betting odds, a fantasy points projection or an outcome guarantee.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/fantasy-get-partner-predictions?key=<API_KEY>&matchId=151543'

Images

GET /api/project/cricbuzz-cricket/images-get-image

Get a cricket image by its image ID, with optional quality (d) and size (p) values.

Full docs β†’
Details

Request a cricket image by ID. The path parameter imageId is required and is a string: take the numeric image ID supplied by another endpoint, such as a player profile, and add the letter c in front of it. The supplied default is c231889. Two optional query parameters are documented. d accepts high or low, and p specifies the image size as one of de, det, gthumb or thumb. The source text does not explain what each value changes visually, so test the options you plan to use. The path ends in i.jpg, so the request targets a JPEG image resource rather than a JSON document. No response was observed for this operation in the supplied probe evidence, and the only supplied response example is an empty object, so the returned content type, byte size and pixel dimensions for each d and p value are not verified. Keep the image ID as the linking key to the endpoint that supplied it, and confirm that you have the right to publish a given image before using it in a product.

Explicitly submit this cricket request 1 required Β· 2 optional
ParameterInValue
path
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/images-get-image?key=<API_KEY>&imageId=c231889'
GET /api/project/cricbuzz-cricket/images-list-galleries

List cricket photo galleries with headline, cover image ID and publish time, paged by the pt cursor

Full docs β†’
Details

Returns the index of cricket photo galleries, newest first in the supplied example, so an interface can show a gallery grid and then open one gallery by its ID. The only input is the optional numeric `pt` query parameter, a paging cursor: leave it empty to load the first page, or send the `publishedTime` value of the last gallery returned by this same operation to load the next page. No live probe was recorded for this operation, so the response description comes from a supplied source example that is unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`) and a `photoGalleryInfoList` array of 11 entries. Each entry is either a `photoGalleryInfo` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A gallery carries `galleryId` (integer), `headline`, `imageId` (integer), `publishedTime` (a string of epoch-style digits whose unit is not documented) and, on most items, an `imageHash` string. Confirm the exact field set, the page size, the ordering, how many galleries one page holds and what an exhausted cursor returns against a live response before depending on them.

Explicitly submit this cricket request 0 required Β· 1 optional
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/images-list-galleries?key=<API_KEY>'

Matches

GET /api/project/cricbuzz-cricket/matches-live

List live cricket matches grouped by match type and series, with match IDs, teams, venues, status text and per-innings scores where available.

Full docs β†’
Details

Return the current live-match feed as one JSON object. The operation has no input parameters on this page, so a plain GET to /matches/v1/live is the whole request. The source spec also mentions optional country-code and UTC-offset request headers, but they are not exposed here, so no locale or time-zone shaping is documented. A probe call returned HTTP 200 with a JSON object containing typeMatches, an array of groups that each have a matchType label (International, League, Domestic and Women were observed) and a seriesMatches array; filters.matchType, an array listing the same group labels; appIndex, an object with seoTitle and webURL text; responseLastUpdated, a string; and contentFilters, an array of filterId and filterName pairs (a liveStream filter was observed). Each seriesMatches entry is either a seriesAdWrapper, which holds seriesId, seriesName and a matches array (some wrappers also carried isLiveStreamEnabled), or a placeholder ad object with name, layout and position that should be skipped when listing matches. Each match has a matchInfo object and, for most probed matches, a matchScore object. matchInfo carries matchId, seriesId, seriesName, matchDesc, matchFormat (for example T20 or TEST), state and stateTitle (probe values included In Progress, Toss, Innings Break, Stumps, Badlight and Complete), status, hideScoreStatus, startDate and endDate as epoch-millisecond strings, isTimeAnnounced, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone, latitude, longitude); currBatTeamId, isFantasyEnabled and livestreamEnabled appear only on some matches. matchScore holds team1Score and team2Score, each with innings objects such as inngs1 containing inningsId, runs, wickets and overs. Everything listed above was seen in the probe sample or the source example; treat optional fields as absent-able, because the sample is a single snapshot and not a guaranteed contract. The result reflects whatever is live at request time, so a short or empty list is possible, and the endpoint does not promise a particular latency or coverage of every competition.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-live?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/matches-recent

List recently played cricket matches with result text, series context, teams, venues and innings scores, grouped by match type.

Full docs β†’
Details

Return the recent-matches feed as one JSON object. The operation has no input parameters on this page, so a plain GET to /matches/v1/recent is the whole request. The source spec also mentions optional country-code and UTC-offset request headers, but they are not exposed here. No probe call was recorded for this operation, so the fields below come from a source example and are documented illustrations, not a verified contract. The example 200 body contains typeMatches, an array of groups with a matchType label and a seriesMatches array; filters.matchType, listing the labels International, League, Domestic and Women; appIndex, an object with seoTitle and webURL text; and responseLastUpdated, a string. Each seriesMatches entry holds a seriesAdWrapper with seriesId, seriesName and a matches array, and each match has a matchInfo object plus a matchScore object. In the example matchInfo carries matchId, seriesId, seriesName, matchDesc (for example a medal match or a semi-final), matchFormat (T20 in the example), state set to Complete, stateTitle such as a short winner label, a status sentence stating the result margin, hideScoreStatus, startDate and endDate as epoch-millisecond strings, seriesStartDt and seriesEndDt, isTimeAnnounced, currBatTeamId, an optional isFantasyEnabled flag, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone, latitude, longitude). matchScore holds team1Score and team2Score, each with an inngs1 object containing inningsId, runs, wickets and overs. The endpoint lists matches that have recently finished; how far back it reaches is not documented, so do not treat it as a complete historical archive. Confirm the live shape and optional fields with your own request before depending on them.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-recent?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/matches-upcoming

List upcoming cricket fixtures with match IDs, start times, teams, venues, formats and series context, grouped by match type.

Full docs β†’
Details

Return the upcoming-matches feed as one JSON object. The operation has no input parameters on this page, so a plain GET to /matches/v1/upcoming is the whole request. The source spec also mentions optional country-code and UTC-offset request headers, but they are not exposed here, so no date window or time-zone behaviour should be assumed. No probe call was recorded for this operation, so the fields below come from a source example and are documented illustrations, not a verified contract. The example 200 body contains typeMatches, an array of groups with a matchType label and a seriesMatches array; filters.matchType, listing International, League, Domestic and Women; appIndex, an object with seoTitle and webURL text; and responseLastUpdated, a string. Each seriesMatches entry holds a seriesAdWrapper with seriesId, seriesName and a matches array, and each match has a matchInfo object. In the example matchInfo carries matchId, seriesId, seriesName, matchDesc (for example 4th Match), matchFormat (T20 and ODI appear), state and stateTitle both set to Preview, a status sentence and a hideScoreStatus string that read as a start time in GMT, startDate and endDate as epoch-millisecond strings, seriesStartDt and seriesEndDt, isTimeAnnounced, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone, latitude, longitude). Because the fixtures have not started, the example matches carry no matchScore object. How many days ahead the list reaches is not documented, so do not assume a fixed schedule window or complete coverage of every competition. Confirm the live shape and optional fields with your own request before depending on them.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-upcoming?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/matches-list

List live, recent or upcoming cricket matches

Full docs β†’
Details

Returns cricket matches for one state view chosen with the required `type` path parameter: `live`, `recent` or `upcoming` (default `recent`). No probe call was recorded for this operation, so the fields below come from a source response example and are unverified. That example has a top-level `typeMatches` array grouped by competition class (`matchType`, for example International, League, Domestic and Women), each holding `seriesMatches` with a `matches` list. Each entry has `matchInfo` (matchId, seriesId, seriesName, matchDesc, matchFormat, startDate, endDate, state, stateTitle, status, team1, team2 with teamId, teamName and teamSName, and venueInfo with ground, city and timezone) and, for matches that have scores, `matchScore` with per-innings runs, wickets and overs. Dates are epoch-millisecond strings. Use the returned matchId with the match-detail endpoints. Coverage depends on current fixtures, so a view can come back with no matches.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-list?key=<API_KEY>&type=recent'
GET /api/project/cricbuzz-cricket/matches-list-schedule

List scheduled cricket matches by competition type, grouped by day, with optional lastTime paging

Full docs β†’
Details

Returns the cricket fixture schedule for one competition group. The required `type` path parameter (default `international`) takes one of `international`, `league`, `domestic` or `women`. The optional numeric `lastTime` query parameter is a paging cursor: leave it empty to load the first page, or send an epoch timestamp in milliseconds (for example 1640883600000) to load the next page; the parameter note points to the `startDt` field returned by this endpoint as the value of interest. No live probe was recorded for this operation, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`) and a `matchScheduleMap` array. Entries are either a `scheduleAdWrapper` object or an `adDetail` object with `layout`, `name` and `position`. A `scheduleAdWrapper` holds a `date` label, a `longDate` string and a `matchScheduleList` array; each item there names a series (`seriesId`, `seriesName`, `seriesCategory`, sometimes `seriesHomeCountry`) and a `matchInfo` array of matches. A match shows `matchId`, `seriesId`, `matchDesc`, `matchFormat`, `startDate` and `endDate` (strings of epoch-style digits), `team1` and `team2` objects (`teamId`, `teamName`, `teamSName`, `imageId`, sometimes `isFullMember`) and a `venueInfo` object (`ground`, `city`, `country`, `timezone`). The example names the match start fields `startDate` and `endDate`, not `startDt`, so confirm which field to send as lastTime, the page size and the result for a type with no fixtures against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/matches-list-schedule?key=<API_KEY>&type=international'

Match Details

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

Get cricket match info by match ID

Full docs β†’
Details

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.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-info?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-balls-graph

Get ball-by-ball graph data for an innings

Full docs β†’
Details

Returns ball-level graph data for one innings of a cricket match. The required numeric `matchId` path parameter selects the match (default 41881) and the optional numeric `iid` query parameter selects the innings (for example 1, default 1). No probe call was recorded for this operation, so the fields below come from a source response example and are unverified. That example is an object with a `balls` array, one entry per delivery, each with ballLabel (a short label such as a run count, W for a wicket or a dot for a dot ball), ballNbr, overNum (for example 49.6), inningsId, totalRuns, event (values seen include NONE, WICKET, FOUR and SIX, sometimes combined with over-break in a comma-separated string), batsmanStrikerId, bowlerStrikerId and an epoch-millisecond timestamp. In the example the newest delivery comes first. The payload holds compact delivery records with player ids only, so it is not a commentary feed or a full event ledger, and the actual series structure should be validated before building charts on it.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-balls-graph?key=<API_KEY>&matchId=41881&iid=1'
GET /api/project/cricbuzz-cricket/match-details-get-leanback-hundred

Get the compact leanback match view for a Hundred match

Full docs β†’
Details

Returns the compact leanback view of one match through the route reserved for The Hundred format. The only input is matchId, sent in the URL path. The response fields listed here come from a source example that is cut off at 4000 characters and were not confirmed by a live probe, so anything after the cut-off is unknown. The example has two top-level objects. matchheaders carries matchdesc, matchformat, matchstarttimestamp, matchendtimestamp, seriesid, seriesname, state, status, winningteamid, revisedtarget, livestreamenabled, alerttype, team1 and team2 objects (teamid, teamname, teamsname and flag fields), teamdetails (batteamid, batteamname, bowlteamid, bowlteamname), tossresults, and momplayers and mosplayers lists of player objects with id, name, role and faceimageid. miniscore carries the current or final snapshot: batsmanstriker and batsmannonstriker (runs, balls, fours, sixes, strkrate), bowlerstriker and bowlernonstriker (overs, maidens, runs, wickets, economy), batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, event, inningsid, inningsnbr and an inningsscores.inningsscore list with balls, batteamid, batteamshortname, inningsid, isdeclared, isfollowon, overs and runs. In the sample the matchformat value is HUN while matchdesc and seriesname describe a T20I series, and innings figures such as overs 19.6 and balls 120 look like six-ball overs, so use it to learn the shape and verify the values on a real Hundred fixture. Treat every field as optional.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-leanback-hundred?key=<API_KEY>&matchId=40381'
GET /api/project/cricbuzz-cricket/match-details-get-miniscorecard-hundred

Get the compact mini scorecard for a Hundred match

Full docs β†’
Details

Returns the compact mini scorecard of one match through the route reserved for The Hundred format. The only input is matchId, sent in the URL path. The response fields listed here come from a source example that is cut off at 4000 characters and were not confirmed by a live probe, so anything after the cut-off is unknown. The example has two top-level objects. matchheader carries matchdesc, matchformat, matchstarttimestamp, matchendtimestamp, seriesid, seriesname, state, status, winningteamid, revisedtarget, livestreamenabled and alerttype, team1 and team2 objects (teamid, teamname, teamsname and flag fields), teamdetails (batteamid, batteamname, bowlteamid, bowlteamname), tossresults (decision, tosswinnerid, tosswinnername), and momplayers and mosplayers lists of player objects with id, name, role, faceimageid and teamname. miniscore carries the snapshot: batsmanstriker and batsmannonstriker (runs, balls, fours, sixes, strkrate), bowlerstriker and bowlernonstriker (overs, balls, maidens, runs, wickets, economy, rpb), batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, custstatus, event, inningsid, inningsnbr and an inningsscores.inningsscore list that begins with balls, batteamid, batteamshortname, inningsid and isdeclared. The sample reports matchformat HUN while matchdesc and seriesname describe a T20I series, its inningsscore shows 120 balls, which is more than a 100-ball innings, and it pairs inningsid 2 with inningsnbr 1st inn, so use it to learn the shape and verify the values on a real Hundred fixture. The header object is named matchheader (singular) in this sample; confirm the name before sharing a parser with other compact match views. Treat every field as optional.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-miniscorecard-hundred?key=<API_KEY>&matchId=40381'
GET /api/project/cricbuzz-cricket/match-details-get-scorecard-hundred

Get the full batting and bowling scorecard for a Hundred match

Full docs β†’
Details

Returns the match scorecard through the route reserved for The Hundred format. The only input is matchId, sent in the URL path. The response fields listed here come from a source example that is cut off at 4000 characters and were not confirmed by a live probe, so anything after the cut-off is unknown. The example has an appindex object (seotitle, weburl), an ismatchcomplete flag, a numeric responselastupdated and a scorecard array. The first scorecard entry shows ballnbr and a batsman array in which each batter has id, name, nickname, runs, balls, fours, sixes, strkrate (a string such as 150 or 154.55), outdec (the dismissal text), iscaptain, iskeeper, isoverseas, imageid, inmatchchange, playingxichange and media or plan fields (videoid, videotype, videourl, premiumvideourl, planid, ispremiumfree, iscbplusfree). Bowling figures, extras and other innings sections are not visible in the truncated example, so do not assume them. The sample belongs to the default matchId 40381 and its title describes a USA versus Ireland T20I from 2021, so it shows the response shape but not a populated Hundred scorecard; verify values on a real Hundred fixture before building scoring or over logic. Treat every field as optional.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-scorecard-hundred?key=<API_KEY>&matchId=40381'
GET /api/project/cricbuzz-cricket/match-details-get-info-alt

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

Full docs β†’
Details

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.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-info-alt?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-leanback

Get the compact leanback live view for a standard cricket match

Full docs β†’
Details

Returns the compact live view (leanback) for one cricket match, selected by the required numeric `matchId` path parameter (default 40381). The matchId comes from the match list, schedule, series, team and venue match endpoints. No probe call was recorded for this operation and the stored source example is cut off partway through `miniscore.inningsscores`, so every field below is unverified and anything after that point is not visible. The example is a completed T20 international and has two top-level sections. `matchheaders` holds the series (seriesid, seriesname), match description and format, state and status text, start and end timestamps, `team1` and `team2` objects, a `teamdetails` block with batting and bowling team ids and short names, a `tossresults` block, revisedtarget, winningteamid, and the `momplayers` and `mosplayers` lists of player entries with id, name, role and image ids. `miniscore` holds the current snapshot: batsmanstriker and batsmannonstriker, bowlerstriker and bowlernonstriker, batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, curovsstats, event, inningsid, inningsnbr and an inningsscores list. Timestamps are epoch milliseconds and many team and player fields are empty strings or zero. The Hundred format has its own leanback operation; this one is the standard route. Nothing here promises a smaller response or a faster refresh than other match-detail operations.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-leanback?key=<API_KEY>&matchId=40381'
GET /api/project/cricbuzz-cricket/match-details-get-livescore

Get the live score panel for one cricket match by match ID

Full docs β†’
Details

Returns the live score data for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). 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. The example is a completed under-19 ODI, so it shows the final state rather than an in-progress score. The response has a `comwrapper` array holding the latest commentary entry (commtxt, eventtype, overnum, ballnbr, inningsid, timestamp and a commentaryformats list), an inningsid, an empty `matchvideos` array and a `miniscore` object. The miniscore carries the current batters (batsmanstriker, batsmannonstriker) and bowlers (bowlerstriker, bowlernonstriker) with runs, balls, overs, wickets and economy, `batteamscore` (teamid, teamscore, teamwkts), crr, rrr, target, ballsrem, oversrem, custstatus, event, lastwkt, partnership, a `performance` list (for example last 5 and last 10 overs), a `pp` powerplay block, an `inningsscores` list (runs, wickets, overs, balls, target, isdeclared, isfollowon per innings) and a timestamp. A responselastupdated field appears at the top level and inside miniscore with different values, and its unit is not documented. This is a focused score panel, not the full batting and bowling scorecard.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-livescore?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-miniscorecard

Get a compact cricket mini scorecard by match ID

Full docs β†’
Details

Returns a compact scorecard for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series, team schedule and result, and venue match endpoints. There are no query parameters, so one request returns one match snapshot. No probe call was recorded for this operation, so the fields below come from a source response example and are unverified; that example is truncated and covers a completed under-19 ODI group match from the ACC U19 Asia Cup 2021. It has two top-level objects. `matchheader` holds the match context: matchdesc, matchformat, state, status, seriesid, seriesname, matchstarttimestamp and matchendtimestamp (epoch milliseconds), winningteamid, revisedtarget, `team1` and `team2` objects (teamid, teamname, teamsname), a `teamdetails` object (batteamid, batteamname, bowlteamid, bowlteamname), a `tossresults` object (decision, tosswinnerid, tosswinnername) and player lists named momplayers and mosplayers. `miniscore` holds the live-style state: batsmanstriker and batsmannonstriker (id, name, runs, balls, fours, sixes, strkrate), bowlerstriker and bowlernonstriker (id, name, overs, maidens, runs, wickets, economy), batteamscore (teamid, teamscore, teamwkts), crr, ballsrem, curovsstats (text for the current over), custstatus, event, inningsid, inningsnbr, an inningsscores.inningsscore list (batteamid, batteamshortname, inningsid, runs, wickets, overs, balls, target, isdeclared, isfollowon) and lastwkt. Some values in the sample are placeholders: the non-striker entry is zeroed with an empty name, and tossresults.decision reads 'yet to be decided' with tosswinnerid 0 although the match state is Complete. Key casing is mostly lowercase but some player keys are camelCase, so confirm names against a real response. This is a summary view, not the full innings-by-innings batting and bowling tables.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-miniscorecard?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-overs

Get an over-by-over summary of a cricket innings by match ID

Full docs β†’
Details

Returns the over-by-over summary of a cricket match. The path parameter `matchId` is required (default 41881) and comes from the match list, schedule, series, team and venue match endpoints. Three optional query parameters control which part of the match is returned: `iid` is the innings id (for example 1), `tms` is the paging cursor and `restrictInningsId` is a boolean. Leave `tms` empty to load the first page; to load the next page pass an epoch timestamp in milliseconds (for example 1640883600000) taken from the `timestamp` field returned by this same endpoint. When `restrictInningsId` is true, paging with `tms` stops at the start of the innings given in `iid` and returns HTTP 204 instead of continuing into the previous innings. These behaviours come from the catalog parameter notes and are not verified by a probe, because no probe call was recorded for this operation. The source response example attached to this operation is truncated and unverified. Its visible part, from a completed under-19 ODI group match, is a `matchheaders` object (matchdesc, matchformat, state, status, seriesid, seriesname, team1, team2, teamdetails, tossresults, winningteamid and match start and end timestamps) followed by a `miniscore` object (batsmanstriker, bowlerstriker, batteamscore, crr, curovsstats, custstatus, event, inningsid, inningsnbr, inningsscores, lastwkt). The per-over list itself is not visible in that excerpt, so confirm the over field names against a real response. The example uses the plural key `matchheaders`, while the compact scorecard example uses `matchheader`.

Explicitly submit this cricket request 1 required Β· 3 optional
ParameterInValue
path
query
Optional filters and paging cursors (2)
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-overs?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-over-details

Get the details of one cricket over by match, innings and timestamp

Full docs β†’
Details

Returns the detail for a single over of a cricket match. All three inputs are required: the path parameter `matchId` (default 41881, from the match list, schedule, series, team and venue match endpoints), the query parameter `iid`, the innings id (default 1), and the query parameter `tms`, an epoch timestamp in milliseconds that identifies the over (default 1640424493537). Take `tms` from the `timestamp` field returned by the over-by-over summary operation for the same match; there is no over-number parameter. The catalog describes this operation as ball-by-ball commentary for one over. No probe call was recorded, so the fields below come from a source response example that is truncated and unverified. That example is a JSON object with an `overs` list whose rows hold batteamid, inningsid, osummary (a text of ball outcomes such as '0 0 W W '), overnum (for example 14.4 or 49.6), runs, score, wickets, wicketover, runrate, requiredrunrate and timestamp. Rows run from the newest over of innings 2 back through innings 1, and the default tms equals the timestamp of the innings 1 row with overnum 49.6. The example therefore shows over-summary rows rather than commentary text, so the catalog description and the example differ; check a real response before depending on either shape.

Explicitly submit this cricket request 3 required Β· 0 optional
ParameterInValue
path
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-over-details?key=<API_KEY>&matchId=41881&iid=1&tms=1640424493537'
GET /api/project/cricbuzz-cricket/match-details-get-overs-graph

Get cricket runs-per-over graph data by match ID

Full docs β†’
Details

Returns runs-per-over graph data for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series, team schedule and result, and venue match endpoints. There are no query parameters, so no innings, over-range or team filter can be sent; one request targets one match. No probe call was recorded for this operation, and the only source response example is an empty JSON object (`{}`), so this operation has no documented response fields: no over numbers, run totals, innings keys or team identifiers are confirmed here. Treat the output shape as unverified, inspect a live response for the match you care about, and only then bind it to a chart or table. The payload is intended as aggregated over-level data, which is a different view from the delivery-level data in the over-details and commentary operations of the match-details group. Coverage depends on the competition and match state, so an empty or minimal body is a plausible result for fixtures that have no graph data yet or never had any.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-overs-graph?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-partnership-graph

Get cricket innings partnership graph data by match ID

Full docs β†’
Details

Returns partnership graph data per innings for one cricket match, selected by the required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series, team schedule and result, and venue match endpoints. There are no query parameters, so one request returns the partnerships for the whole match. No probe call was recorded for this operation, so the fields below come from a source response example and are unverified; that example is truncated and covers an under-19 ODI group match from the ACC U19 Asia Cup 2021 between Afghanistan U19 and United Arab Emirates U19. The top level is an array with one object per innings: batTeamId, batTeamName, batTeamShortName, inningsID and a `partnershipDataDTO` list. Each partnership row carries two batter blocks, bat1Id, bat1Name, bat1Runs, bat1balls, bat1ImageID and bat2Id, bat2Name, bat2Runs, bat2balls, bat2ImageID, plus the pair totals totalRuns and totalBalls. Several sample details need care. In the first innings every bat1balls and bat2balls value is 0 while totalBalls is not, whereas the second innings shows populated per-batter balls. totalRuns can be higher than bat1Runs plus bat2Runs on some rows, so do not assume the two are equal. The same image ID (182026) repeats for many different players, which suggests it can be a generic value rather than a player-specific picture. No wicket-number or fall-of-wicket field appears in the sample rows. Coverage depends on the competition and match state, so an empty array or missing innings is possible.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-partnership-graph?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-quick-access

Get cricket match-center quick-access shortcuts by match ID

Full docs β†’
Details

Returns the quick-access shortcuts for the match center of one cricket match, selected by the required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series, team schedule and result, and venue match endpoints. There are no query parameters, so one request returns one match-specific shortcut list. No probe call was recorded for this operation, so the fields below come from a source response example and are unverified; that example appears complete and covers the ACC U19 Asia Cup 2021 match with matchId 41881. The response is an object with an `items` array of four entries in the sample: Graphs, Table, Schedule and Series Stats. Each entry has name (display label), iconName (a comma-separated list of icon aliases such as 'graph-nodes, graph_nodes'), showToPaidUsers (true on all four sample entries) and url. One entry also has highlightType, an empty string in the sample. The url values are app-style deep links with a custom scheme rather than https addresses. The Graphs link carries the match id and a page value of graphs, while the other three carry the series id (3926 in the sample), a page value (points, schedule, stats) and the series name slug. The meaning of showToPaidUsers and highlightType is not documented, and other page values may exist for other matches. This operation returns navigation metadata only: it does not contain scores, scorecards, commentary or any statistics themselves.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-quick-access?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-scorecard

Get a cricket match scorecard with batting rows by match ID

Full docs β†’
Details

Returns the scorecard for one cricket match, selected by the required numeric `matchId` path parameter (default 40381). Take the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints. There are no query parameters, so one request targets one match and no innings, team or player filter can be sent. A probe call for matchId 40381 returned HTTP 200 with a JSON object holding a `scorecard` array, a boolean `ismatchcomplete`, an `appindex` object, a string `status` and an integer `responselastupdated`; the declared nested numeric types matched, including integral JSON numbers. The supplied source example is unverified and truncated: it shows `appindex` with `seotitle` and `weburl`, and a `scorecard` entry with `ballnbr` plus a `batsman` list whose rows include `id`, `name`, `runs`, `balls`, `fours`, `sixes`, `strkrate` (a string such as "154.55"), `outdec` (dismissal text), `iscaptain` and `iskeeper`. Bowling figures, extras and fall-of-wicket sections were not visible in that example, so confirm them against a live response before depending on them. The unit of `responselastupdated` is not documented and should not be inferred. Coverage depends on the match, so an upcoming or abandoned fixture may return a sparse body.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-scorecard?key=<API_KEY>&matchId=40381'
GET /api/project/cricbuzz-cricket/match-details-get-team

Get one team's squad in a cricket match by match and team ID

Full docs β†’
Details

Returns the squad of a single team for one cricket match, selected by two required numeric path parameters: `matchId` (default 35878) and `teamId` (default 9). Take the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints, and the teamId from the match info operation of the match-details group. There are no query parameters, so no role or category filter can be sent. No probe call was recorded for this operation, so the fields below come only from a truncated, unverified source example: a top-level `player` array of groups, each with a `category` label (the example shows "playing XI" and "bench") and a nested `player` list. Each player row in the example carries `id` (a string), `name`, `role` (values such as Batsman, Bowler, WK-Batsman and Batting Allrounder), `teamname`, the booleans `captain`, `keeper`, `isoverseas` and `isheader`, the image references `faceimageid`, `countryimageid` and `imageId`, and the text fields `battingStyle`, `bowlingStyle`, `battingsummary`, `bowlingsummary`, `inmatchchange` and `playingxichange`. Several of those text fields were empty strings in the example, so do not rely on them being populated. The `category` label is the only selection hint, so do not treat every listed player as a confirmed playing XI member. Coverage depends on the competition and match state, and a fixture without published squads may return a sparse or empty body.

Explicitly submit this cricket request 2 required Β· 0 optional
ParameterInValue
path
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-team?key=<API_KEY>&matchId=35878&teamId=9'
GET /api/project/cricbuzz-cricket/match-details-get-teams

Get both teams' squads for a cricket match by match ID

Full docs β†’
Details

Returns the squads of both teams for one cricket match, selected by the single required numeric `matchId` path parameter (default 41881). Take the matchId from the match list, schedule, series matches, team schedule and result, and venue match endpoints. There are no query parameters and no teamId, so the response always covers the whole fixture. No probe call was recorded for this operation, so the fields below come only from a truncated, unverified source example: an `appindex` object with `seotitle` and `weburl` strings, and a `team1` object whose `players` list contains category groups (the example shows "playing XI"), each with a nested `player` list. Each player row carries `id` (a string), `name`, `role` (values such as Batter, Bowler, WK-Batter and Batting Allrounder), `teamname`, the booleans `captain`, `keeper`, `isoverseas` and `isheader`, the image references `faceimageid`, `countryimageid` and `imageId`, and the text fields `battingStyle`, `bowlingStyle`, `battingsummary`, `bowlingsummary`, `inmatchchange` and `playingxichange`. The example is cut off before any second team appears, so the key that holds the other side is not confirmed here. Match squads are not series-wide squads, and a listed player is not a confirmed playing XI member unless the category says so. Coverage depends on the competition and match state.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-teams?key=<API_KEY>&matchId=41881'

Match Commentary

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

Get ball-by-ball match commentary, optionally by innings

Full docs β†’
Details

Returns the text commentary feed for one cricket match identified by matchId. Optionally restrict the feed to a single innings with iid, and page through it by passing the epoch-millisecond timestamp of a previously returned entry as tms; leave both empty to load the first page. The response fields listed here come from a truncated source example and were not confirmed by a live probe. The comwrapper array holds items with a commentary object carrying commtxt, eventtype (for example NONE or WICKET), inningsid, overnum, ballnbr, batteamscore, timestamp, commentaryformats and media reference fields such as videoid, imageid and videourl. The example also shows an appindex object (seotitle, weburl) and a buzz object (applink, imageids, isbuzzenabled, position). Commentary availability depends on the match, so treat every field as optional.

Explicitly submit this cricket request 1 required Β· 2 optional
ParameterInValue
path
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-commentaries?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-player-commentaries

Get commentary filtered to one player in an innings

Full docs β†’
Details

Returns the commentary lines connected to a single player within one innings of a match. All four inputs are required: matchId in the path, iid for the innings, playerId for the player and type set to batting or bowling. The response fields listed here come from a truncated source example and were not confirmed by a live probe. The comwrapper array holds items with a commentary object carrying commtxt, eventtype, inningsid, overnum, ballnbr, timestamp and commentaryformats, plus an appindex object (seotitle, weburl). In the example, entries whose eventtype is over-break also contain an oversep object with the strike and non-strike batter names and figures, bowler name and figures, battingteamname, oversummary, runs, score, wickets, ovrbatnames and ovrbowlnames. Availability depends on the match and the player's involvement in the chosen innings.

Explicitly submit this cricket request 4 required Β· 0 optional
ParameterInValue
path
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-player-commentaries?key=<API_KEY>&matchId=41881&iid=2&playerId=23016&type=batting'
GET /api/project/cricbuzz-cricket/match-details-get-commentaries-hundred

Get match commentary for The Hundred format

Full docs β†’
Details

Returns commentary through the route reserved for matches played in The Hundred format, taking matchId in the path and the optional iid (innings) and tms (epoch-millisecond paging) query parameters. The response fields listed here come from a minimal source example and were not confirmed by a live probe. That example contains a comwrapper array, an inningsid, a matchvideos array and a responselastupdated value. Its only comwrapper item is an empty placeholder commentary object with commtxt empty, eventtype NONE, inningsid 0 and a fixed timestamp, which is what a match with no commentary content looks like. The default matchId 41881 is the same sample used by the standard commentary operation, so the example does not show a populated Hundred feed.

Explicitly submit this cricket request 1 required Β· 2 optional
ParameterInValue
path
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-commentaries-hundred?key=<API_KEY>&matchId=41881'
GET /api/project/cricbuzz-cricket/match-details-get-player-commentaries-hundred

Get commentary lines for one batter or bowler in a Hundred innings

Full docs β†’
Details

Returns the text commentary lines that involve one chosen player in one innings of a match, through the route reserved for The Hundred format. The request takes matchId in the path and three required query parameters: iid (the innings number), playerId (a player taking part in that match, found through the match teams endpoint) and type, which must be batting or bowling to select the player's role. The response fields listed here come from a source example that is cut off at 4000 characters and were not confirmed by a live probe. That example shows an appindex object (seotitle, weburl) and a comwrapper array. Each comwrapper item holds a commentary object with commtxt, eventtype (NONE, FOUR, WICKET, or a combined value such as over-break,SIX), inningsid, overnum, ballnbr, batteamscore, boundarytracker, timestamp, commentaryformats (bold id and value pairs such as B0$ and B1$) and media reference fields (videoid, videotype, videourl, premiumvideourl, imageid, planid, ispremiumfree). Over-break entries add an oversep object with oversummary, runs, wickets, score, batstrikername, batnonstrikername, battingteamname, bowlname and bowldetails. The default values (matchId 40381, iid 1, playerId 11131, type batting) belong to a sample whose lines describe a T20I with six-ball overs, so the example does not show a populated Hundred feed. Treat every field as optional.

Explicitly submit this cricket request 4 required Β· 0 optional
ParameterInValue
path
query
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-player-commentaries-hundred?key=<API_KEY>&matchId=40381&iid=1&playerId=11131&type=batting'
GET /api/project/cricbuzz-cricket/match-details-get-highlights-hundred

Get text highlights for one innings of a Hundred match

Full docs β†’
Details

Returns highlights commentary for one innings of a match, through the route reserved for The Hundred format. The request takes matchId in the path, a required iid (the innings number) and an optional htype filter: 0 returns all entries, 2 fours, 4 sixes, 6 fours and sixes, and 8 wickets. When htype is omitted the catalog describes the result as fours, sixes and wickets, and odd htype values behave like the even value below them. No response fields are documented for this operation: the source example is an empty JSON object and no live probe was run, so the field names and item shape are unverified. Inspect a real response for a Hundred fixture before modelling it, and treat the result as text commentary rather than video clips, because no media or playback fields are documented.

Explicitly submit this cricket request 2 required Β· 1 optional
ParameterInValue
path
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-highlights-hundred?key=<API_KEY>&matchId=40381&iid=1'
GET /api/project/cricbuzz-cricket/match-details-get-highlights

Get text highlights (fours, sixes, wickets) for one innings of a match

Full docs β†’
Details

Returns highlights commentary for one innings of a match: the fours, sixes and wickets passages of the text commentary. The request takes matchId in the URL path, a required iid (the innings number, for example 1) and an optional htype filter. htype accepts 0 for all entries, 2 for fours, 4 for sixes, 6 for fours and sixes together, and 8 for wickets. When htype is omitted the catalog describes the result as fours, sixes and wickets, and odd htype values behave like the even value just below them. No response fields are documented for this operation: the source example is an empty JSON object and no live probe was run, so field names and item shape are unverified. Inspect a real response for your own matchId before modelling it, and treat the result as written commentary rather than video clips, because no media or playback fields are documented. The Hundred format has its own highlights operation; this one is the standard route.

Explicitly submit this cricket request 2 required Β· 1 optional
ParameterInValue
path
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/match-details-get-highlights?key=<API_KEY>&matchId=41881&iid=1'

News

GET /api/project/cricbuzz-cricket/news-list-by-author

List cricket news articles written by one author

Full docs β†’
Details

Returns the news articles written by a single author, selected by the required numeric `authorId` path parameter (default 197). Take the authorId from the `id` field inside the `authors` array of a news detail response. The optional numeric `lastId` query parameter pages through the list: leave it empty to load the first page, or send the `id` of the last story from the previous response to request the next page (the parameter notes give 140342 as an example value). No live probe was recorded for this operation, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context`, `storyType`, `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), an empty `entitlements` object and a `coverImage` with `caption`, `id` and `source`. Confirm the exact field set, the page size and the behaviour for an author with no stories against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-list-by-author?key=<API_KEY>&authorId=197'
GET /api/project/cricbuzz-cricket/news-get-author-info

Get a cricket news author profile by author ID

Full docs β†’
Details

Returns the profile of one news author, selected by the required numeric `authorId` path parameter (default 197). Take the authorId from the `id` field inside the `authors` array of a news detail response. There are no query parameters, so one request returns one profile. No live probe was recorded for this operation, so the response description comes from a single supplied source example that parses as a complete JSON object but is unverified. It shows six keys: `id` (integer, matching the requested author), `name` (string), `designation` (string, for example a role title), `aboutMe` (a short biography string), `imageId` (integer) and `twitterHandle`. Despite its name, `twitterHandle` holds a full profile URL in the example rather than a bare handle, so do not assume a username format. The `imageId` is an identifier for the image operations of this catalog and is not a ready-to-use image URL. Fields can be missing or empty for some authors, and the public social reference is display data only. Confirm the field set and types against a live response before relying on them.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-get-author-info?key=<API_KEY>&authorId=197'
GET /api/project/cricbuzz-cricket/news-get-categories

List all cricket news story categories with IDs

Full docs β†’
Details

Returns the catalog of cricket news story categories. The operation takes no path, query or header parameters, so one request returns the whole list. No live probe was recorded, so the response description comes from a supplied source example that parses as a complete JSON object but is unverified. The example is an object with a single `storyType` array. Each entry has an integer `id`, a `name` string and a `description` string. The example lists 15 categories, including News (id 1), Editor's Picks (2), Editorial (3), Interviews (4), Specials (5), Reports (6), Previews (7), Statistics & Analysis (8), Live Blogs (10), Tour Diaries (13), Match Features (18), Features (19), Social Tattle (20), Premium Editorials (21) and Pulse (25). The ids are not contiguous, which is why they should be read from the response instead of being guessed. Use an id from this list when you call the news list by category operation. The set of categories can change over time, so confirm the current list against a live response.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-get-categories?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/news-list-by-category

List the latest cricket news stories in one category

Full docs β†’
Details

Returns the latest news stories for a single news category, selected by the required numeric `categoryId` path parameter (default 5). Take the categoryId from the `id` field returned by the news categories operation. The optional numeric `lastId` query parameter pages through the list: leave it empty to load the first page, or send the `id` of the last story returned by this same operation to request the next page. No live probe was recorded for this operation, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context` (a tournament or series label in the example), `storyType`, `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), empty `adsType` and `entitlements` objects and a `coverImage` with `caption`, `id` and `source`. Confirm the exact field set, the page size and the behaviour for a category with no stories against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-list-by-category?key=<API_KEY>&categoryId=5'
GET /api/project/cricbuzz-cricket/news-detail

Get the full text and metadata of one cricket news story

Full docs β†’
Details

Returns the full detail of a single news story, selected by the required numeric `newsId` path parameter (default 122025). Take the newsId from the `id` field of a story returned by the news list, news by category or news by topic operations. No live probe was recorded for this operation, so the response description comes from a supplied source example (3,356 characters, not truncated) and is unverified. In that example the body is one object with an `appIndex` object (`seoTitle`, `webURL`), an `authors` array (each entry has `id`, `imageId`, `name` and `twitterHandle`), a `content` array, `headline`, `intro`, `context`, `storyType`, `source`, an integer `id`, the string timestamps `publishTime` and `lastUpdatedTime` (epoch-style digits whose unit is not documented), an empty `entitlements` object, a `coverImage` with `caption`, `id` and `source`, a `tags` array and a `format` array. Each `content` entry is either a `content` object holding `contentType` (`text` in the example) and `contentValue` (one paragraph), sometimes with `hasFormat`, or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. Paragraphs flagged with `hasFormat` contain short placeholder markers, and the `format` array (entries of type `urls` and `links`, each with an `id` and a `value`) lists what each marker stands for. Each `tags` entry has `itemId`, `itemName` and `itemType` (`team` and `player` in the example). The article body is editorial content, so confirm your content-use terms before storing or republishing it, and check the exact field set against a live response before depending on it.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-detail?key=<API_KEY>&newsId=122025'
GET /api/project/cricbuzz-cricket/players-get-news

Get cricket news stories about one player by player ID

Full docs β†’
Details

Returns the news stories associated with a single player, selected by the required numeric `playerId` path parameter (default 8733). Take the playerId from the `id` field returned by the trending players or player search operations. The operation accepts no other parameters, so the supplied evidence documents no paging cursor for it. No live probe was recorded, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context` (a tour or series label in the example), `storyType`, `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), empty `adsType` and `entitlements` objects and a `coverImage` with `caption`, `id` and `source`. Confirm the exact field set, the number of stories returned and the behaviour for a player with no coverage against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-news?key=<API_KEY>&playerId=8733'
GET /api/project/cricbuzz-cricket/series-get-news

Get cricket news stories for one series or tournament by series ID

Full docs β†’
Details

Returns the news stories attached to a single cricket series, selected by the required numeric `seriesId` path parameter (default 3636). Take the seriesId from the `id` field returned by the series list or series archives operations. The operation accepts no other parameters, so the supplied evidence documents no paging cursor for it. No live probe was recorded, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context` (the series name in the example), `storyType` (for example News or Match Features), `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), empty `adsType` and `entitlements` objects and a `coverImage` with `caption`, `id` and `source`. Confirm the exact field set, the number of stories returned and the behaviour for a series with no coverage against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-news?key=<API_KEY>&seriesId=3636'
GET /api/project/cricbuzz-cricket/teams-get-news

Get cricket news stories about one team by team ID

Full docs β†’
Details

Returns the news stories associated with a single cricket team, selected by the required numeric `teamId` path parameter (default 2). Take the teamId from the `teamId` field returned by the teams list operation. The operation accepts no other parameters, so the supplied evidence documents no paging cursor for it. No live probe was recorded, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array; for the default teamId 2 the example seoTitle names India. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context` (an interview label or a tour label in the example), `storyType` (for example Interviews or Previews), `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), empty `adsType` and `entitlements` objects and a `coverImage` with `caption`, `id` and `source`. Confirm the exact field set, the number of stories returned and the behaviour for a team with no coverage against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-news?key=<API_KEY>&teamId=2'
GET /api/project/cricbuzz-cricket/news-get-topics

List all available cricket news topics with IDs and headlines

Full docs β†’
Details

Returns the catalogue of editorial news topics. The operation takes no parameters: a plain GET returns every topic the service exposes. No live probe was recorded, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with a `topics` array, and each entry holds three fields: `id` (integer), `headline` (the topic title) and `description` (a short free-text line). The topics in the example are event or storyline collections such as an auction, a team-preview series, a tournament controversy or a player retirement. The ids in the example run downward from 375 with gaps, so do not assume they are contiguous or sorted. Some description values read like a credit or a repeat of the headline rather than a summary, so use `headline` as the label and treat `description` as optional display text. Keep the `id` of a chosen topic and pass it to the news by topic operation to load the stories for that topic. Confirm the exact field set, the total number of topics and their ordering against a live response before depending on them.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-get-topics?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/news-list-by-topic

List the latest cricket news stories for one topic by topic ID, with optional lastId paging

Full docs β†’
Details

Returns the latest cricket news stories filed under one editorial topic. The required numeric `topicId` path parameter (default 349) is the `id` value returned by the news topics operation. The optional numeric `lastId` query parameter is a paging cursor: leave it empty to load the first page, or pass the `id` of the last story returned by this same operation to load the next page. No live probe was recorded for this operation, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context`, `storyType`, `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), an empty `adsType` object, an `entitlements` object and a `coverImage` with `caption`, `id` and `source`. In the example the entitlements of the listed stories carry `name` and `type` values, sometimes a `teamId` array or a `seriesId`, and the stories also carry a `planId`, which suggests that some topic stories are premium-gated. Confirm the exact field set, the page size, the paging behaviour and the result for a topic with no stories against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-list-by-topic?key=<API_KEY>&topicId=349'
GET /api/project/cricbuzz-cricket/news-list

List the latest cricket news stories from the index or premium index feed, with optional lastId paging

Full docs β†’
Details

Returns the latest cricket news stories as a headline feed. The required string `type` path parameter (default `index`) selects the feed and is documented as one of `index` or `premiumIndex`. The optional numeric `lastId` query parameter is a paging cursor: leave it empty to load the first page, or pass the `id` of the last story returned by this operation to load the next page. One recorded probe with `type=index` returned HTTP 200 and a JSON object with a `storyList` array, a `lastUpdatedTime` string and an `appIndex` object (`seoTitle`, `webURL`). That probe contained 12 `storyList` entries: 10 `story` objects and 2 `ad` objects with `layout`, `name` and `position`, so a client has to skip the ad slots. Each observed story had `id` (integer), `hline`, `seoHeadline`, `intro`, `context`, `source`, `storyType`, `imageId` (integer), `pubTime` (a string of digits whose unit is not documented), `adsType` and `entitlements` objects (both empty in the probe) and a `coverImage` with `caption`, `id` and `source`. Observed `storyType` values were News, Features, Reports and Match Features. A supplied source example, truncated and unverified, shows the same shape. The `premiumIndex` feed value and the `lastId` continuation were not probed, so the contents of the premium feed, the page size and the result for an unknown cursor are unconfirmed.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-list?key=<API_KEY>&type=index'

Series

GET /api/project/cricbuzz-cricket/series-list-archives

List archived cricket series by competition type, with optional year filter and lastId paging

Full docs β†’
Details

Returns archived cricket series for one competition group, grouped by year. The required `type` path parameter (default `international`) takes one of `international`, `league`, `domestic` or `women`. The optional numeric `year` query parameter lists the series of that year (the note gives 2024 as an example). The optional numeric `lastId` query parameter is a paging cursor: leave it empty to load the first page, or send the `id` value of a series returned by this same endpoint to load the next page. No live probe was recorded for this operation, so the response description comes from a supplied source example that is unverified and was not tied to a stated type, year or lastId. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`) and a `seriesMapProto` array. Each `seriesMapProto` entry has a `date` string (the year, 2026 in the example) and a `series` array of 20 items. A series shows `id` (integer), `name`, `startDt` and `endDt` (strings of epoch-style digits whose unit is not documented), `thumborImageId` (integer) and, on some items, an `isDefaultImage` flag. The example `seoTitle` reads as a current-series title rather than an archive title, so confirm the exact field set, the page size, the ordering and the result for a year with no series against a live response before depending on them.

Explicitly submit this cricket request 1 required Β· 2 optional
ParameterInValue
path
query
Optional filters and paging cursors (1)
ParameterInValue
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-list-archives?key=<API_KEY>&type=international'
GET /api/project/cricbuzz-cricket/series-get-matches

List recent and upcoming matches in a cricket series by seriesId

Full docs β†’
Details

Returns the fixtures of one cricket series, selected with the required numeric seriesId path parameter (the id value from the series list or archived series list endpoints). The source response example documents an appIndex block (seoTitle, webURL) and a matchDetails array. Each matchDetailsMap entry has a date-range key, a match list and the seriesId. Every match carries matchInfo (matchId, matchDesc, matchFormat, state, status, startDate and endDate as epoch-millisecond strings, currBatTeamId, isTimeAnnounced, team1 and team2 with teamId, teamName, teamSName and imageId, and venueInfo with ground, city and timezone) plus a matchScore object with per-team, per-innings runs, wickets, overs and declaration flags. Advertisement placeholder entries (adDetail with layout, name and position) can appear between fixtures and should be skipped. These fields come from a source example rather than a live probe, so treat optional blocks such as matchScore as coverage-dependent.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-matches?key=<API_KEY>&seriesId=3641'
GET /api/project/cricbuzz-cricket/series-get-seasons

List all seasons of a recurring cricket series by seriesId

Full docs β†’
Details

Returns the season history of a recurring competition, selected with the required numeric seriesId path parameter (the id value from the series list or archived series list endpoints). The source response example documents a seasons array in which each season has id, name, shortName, season (year label), seriesType, host (comma-separated countries), startDate and endDate as epoch-millisecond strings, isArchived, and winner and runnerUp team objects (teamId, teamName, teamSName, imageId, isActive, isLeagueTeam, teamPriority and, on some teams, isVideoPresent). A series without season history answers HTTP 204 with an empty body, and in testing only IPL editions returned season data, so do not assume other recurring series work. The fields shown are from a source example rather than a live probe.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-seasons?key=<API_KEY>&seriesId=9237'
GET /api/project/cricbuzz-cricket/series-get-squads

List the squads registered in a cricket series by seriesId

Full docs β†’
Details

Returns the squad directory of one series, selected with the required numeric seriesId path parameter (the id value from the series list or archived series list endpoints). The source response example documents appIndex (seoTitle, webURL), seriesId, seriesName and a squads array holding two row shapes: header rows with isHeader set to true and a squadType group label such as Test, and squad rows with squadId, squadType (the squad label, which in the example is a team name), teamId and imageId. The response identifies squads only and does not include player rosters. The fields shown are from a source example rather than a live probe, so squad availability depends on coverage for the competition.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-squads?key=<API_KEY>&seriesId=3718'
GET /api/project/cricbuzz-cricket/series-get-players

List the players of one squad in a cricket series by seriesId and squadId

Full docs β†’
Details

Returns the player list of one squad inside one cricket series. Both path parameters are required numbers: seriesId, the id value from the series list or archived series list endpoints, and squadId, the squadId value from the series squads endpoint of this product. The source response example documents a flat player array that mixes two kinds of entries. Header rows carry isHeader true and a name such as BATTERS, ALL ROUNDERS, WICKET KEEPERS or BOWLERS. Player rows carry id (a string), name, role, imageId (a number), battingStyle and, for many players, bowlingStyle, plus a captain flag on the player marked as captain. A 204 example with an empty object is also documented. These fields come from a source example rather than a live probe, so treat bowlingStyle, captain and the header names as coverage-dependent.

Explicitly submit this cricket request 2 required Β· 0 optional
ParameterInValue
path
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-players?key=<API_KEY>&seriesId=3718&squadId=15826'
GET /api/project/cricbuzz-cricket/series-get-venues

List the venues and grounds used by a cricket series by seriesId

Full docs β†’
Details

Returns the grounds associated with one cricket series. The only input is the required numeric seriesId path parameter, the id value from the series list or archived series list endpoints. The source response example documents an appIndex block (seoTitle and webURL page metadata), seriesId, seriesName and a seriesVenue array. Each seriesVenue entry has id (a number), ground, city, country, imageId (a string) and an isDefaultImage boolean. These fields come from a source example rather than a live probe. The example carries no coordinates, capacity, ticketing or pitch details, so do not expect them from this endpoint.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-venues?key=<API_KEY>&seriesId=3718'
GET /api/project/cricbuzz-cricket/series-list

List cricket series by type: international, league, domestic or women

Full docs β†’
Details

Returns cricket series grouped by month for one category chosen with the required type path parameter. The documented values are international, league, domestic and women, and the default is international. A recorded probe with type=international returned HTTP 200 and a JSON object with a seriesMapProto array (11 month groups in that sample), an appIndex object (seoTitle and webURL) and a contentFilters array whose single entry had filterId liveStream and filterName Live Streaming. Each seriesMapProto group has a date label such as OCTOBER 2026 and a series array. Each series entry has id (a number), name, startDt and endDt, with the two dates serialized as epoch-millisecond strings. The id is the seriesId used by the other series endpoints of this product. The league, domestic and women values come from the parameter description and were not probed.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-list?key=<API_KEY>&type=international'
GET /api/project/cricbuzz-cricket/series-get-stats

Get a cricket series statistics leaderboard by seriesId and statsType, such as the default mostRuns table, as a headers array plus player rows

Full docs β†’
Details

Returns the statistics leaderboard for one cricket series. Send seriesId in the URL path (required number; the default 3718 is the documented example value) and statsType as a required query string (the default mostRuns is the documented example value). Both values come from other operations of this product: seriesId is the id field returned by the series list or series archive operations, and statsType is the value field returned by the series stats filter operation. The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a filter object whose matchtype array lists matchTypeDesc and matchTypeId strings (a single Test entry in the example) and a testStatsList object with a headers array (Batter, M, I, R, SR) and a values array. Each element of values is an object that holds its own values array of strings: in the example the first string looks like a numeric player id, the second is the player name, and the strings after that line up with the columns that follow the Batter header, so a row carries one more string than headers has entries. The example lists fifteen rows for the Plunket Shield 2021-22 series. No live probe was recorded for this endpoint, so every response field described here comes from the source example and is not independently verified. The supplied evidence does not show how the list object, its headers or the matchtype filter change for other statsType values, and coverage depends on the series.

Explicitly submit this cricket request 2 required Β· 0 optional
ParameterInValue
path
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-stats?key=<API_KEY>&seriesId=3718&statsType=mostRuns'
GET /api/project/cricbuzz-cricket/series-get-points-table

Get a cricket series points table by seriesId, with team standings, net run rate, recent form, a column legend and per-team match results

Full docs β†’
Details

Returns the points table of one cricket series. Send seriesId in the URL path (required number; the default 7572 is the documented example value, and the source example for it is ICC Cricket World Cup League Two 2023-27). Take the id from the id field of the series list or series archive operations. The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a lastUpdatedTime string that holds an epoch-millisecond timestamp, a legend array of key and value pairs that explain the column abbreviations (PTS, NRR, Q, E, P, W, L, NR, D) and a pointsTable array. Each pointsTable entry has a groupName (Teams in the example) and a pointsTableInfo array with one object per team: teamId, teamFullName, teamImageId, matchesPlayed, matchesWon, matchesLost, noRes and points as numbers, nrr as a signed string such as +0.677, a form array of recent result letters (W or L in the example) and a teamMatches array. Each teamMatches entry gives matchId, matchName, opponent, opponentId, opponentSName, opponentImageId, a result text, a startdt epoch-millisecond string, an nrrChanges signed string and a winner team id. The source also documents an HTTP 204 response with an empty object, which is the answer for a series that has no points table. No live probe was recorded for this endpoint, and the supplied 200 example is cut off inside the first team's teamMatches list, so later teams and any further fields are not visible. Every field described here comes from the source example and is not independently verified. The table is the competition's own standings and not a global ranking.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-points-table?key=<API_KEY>&seriesId=7572'

Rankings

GET /api/project/cricbuzz-cricket/stats-get-icc-standings

Get the ICC team standings table for the World Test Championship or World Cup Super League by matchType and optional seasonId

Full docs β†’
Details

Returns an ICC competition standings table for teams. matchType is a required path number with two documented values: 1 for the World Test Championship and 2 for the World Cup Super League. seasonId is an optional query number: use the id of an entry in the seasonStandings array returned by this same endpoint, and leave it empty to let the endpoint choose its own default season, which the source does not describe. The source 200 example, recorded for matchType 2, contains three parts. headers is a string array that names the columns (Rank, Flag, Team, Points). seasonStandings is an array of objects with a numeric id and a name, shown as id 3 with the name ICC Men's Cricket World Cup Super League (2021 - 2023). values is an array of row objects, each with a value array of strings in the same order as headers, from 1 New Zealand with 175 points down to 13 Netherlands with 35 points. The Flag cell is a numeric-looking string that appears to be an image identifier, which is unverified. No live probe was recorded, and the example season should not be read as the current one.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/stats-get-icc-standings?key=<API_KEY>&matchType=2'
GET /api/project/cricbuzz-cricket/stats-get-icc-rankings

Get ICC cricket rankings by category (batsmen, bowlers, allrounders or teams), format (Test, ODI or T20) and men's or women's table

Full docs β†’
Details

Returns an ICC ranking table. Send category in the URL path (required string: batsmen, bowlers, allrounders or teams; default batsmen) and formatType in the query string (required string: test, odi or t20; default t20). Add isWomen=1 to request the women's table; the parameter notes say that with isWomen set to 1 there is no odi table. The response is an object with a rank array and an appIndex object (seoTitle and webURL strings). A live probe with category batsmen and formatType t20 returned HTTP 200 with that shape, 15 entries in rank, and string values for the ranking fields. The observed and source-example entries carry id, rank, name, country, countryId, faceImageId, rating, points, lastUpdatedOn (a YYYY-MM-DD date) and trend (Flat, Up or Down). An integer difference field, a signed change such as 1 or -2 in the source example, appears only on some entries. Ranks are strings and can tie: the source example gives two players rank 5 and then continues at 7. The example seoTitle mentions a top 100 list, but the example and the probe each show 15 entries, so the list length is not documented as fixed. Only the batsmen and t20 combination was probed; the entry fields for bowlers, allrounders, teams, the other formats and the women's table are not verified, and team entries in particular may not carry the player fields. Coverage and the update date depend on the data source.

Explicitly submit this cricket request 2 required Β· 1 optional
ParameterInValue
path
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/stats-get-icc-rankings?key=<API_KEY>&category=batsmen&formatType=t20'

Players

GET /api/project/cricbuzz-cricket/players-get-info

Get one cricket player's profile by playerId: name, role, batting and bowling style, birth details, best rankings, team IDs and recent form

Full docs β†’
Details

Returns the profile of a single cricket player. playerId is required, goes in the URL path and is a number: use the id value from the trending players or player search operations of this product. The default 6635 is an example value. A live probe for playerId 6635 returned HTTP 200 with a JSON object whose observed fields are id, name, fullName, role, bat (batting style), bowl (bowling style), height, birthPlace, intlTeam, teams (a comma-separated string of team names), DoB, DoBFormat, image (a URL string), bio, rankings, appIndex, faceImageId and intlTeamImageId (both integers), teamNameIds (an array of teamId and teamName objects), playerTeamIds (a comma-separated string of team IDs), and recentBatting and recentBowling objects that each hold a headers array and a rows array. In that probe, rankings.bat held testBestRank, odiBestRank and t20BestRank as strings while rankings.bowl and rankings.all were empty objects. Some text values carry trailing spaces, DoB includes an age in brackets, and bio contains HTML line-break tags. In the probe each row of recentBatting had five values against four headers, with the leading value looking like a match identifier and followUpLinkText holding a relative page path. The source 200 example is cut off inside bio, so fields after it are known only from the probe. Fields are coverage-dependent and a player may have empty ranking or form sections.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-info?key=<API_KEY>&playerId=6635'
GET /api/project/cricbuzz-cricket/players-get-batting

Get a cricket player's batting statistics by playerId as a format-by-metric table, optionally limited to one series with seriesId

Full docs β†’
Details

Returns the batting statistics of a single cricket player as a table. playerId is required, goes in the URL path and is a number: use the id value from the trending players or player search operations of this product. The default 8733 is an example value. seriesId is optional, goes in the query string and is a number: pass the id value of a series from the series list or series archive operations to limit the statistics to that series, or leave it empty for the default view. The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a headers array (ROWHEADER, Test, ODI, T20 and IPL in the example), a seriesSpinner array of objects with a seriesName (a single Career entry in the example) and a values array. Each element of values is an object with its own values array of strings: the first string is the metric label and the following strings line up with the format columns in headers. The example metrics are Matches, Innings, Runs, Balls, Highest, Average, SR, Not Out, Fours, Sixes, Ducks, 50s, 100s, 200s, 300s and 400s, and every number is a string. No live probe was recorded for this endpoint, so all fields are source-example fields. The columns, the series options and the defaults when seriesId is supplied are not verified, and career coverage is not guaranteed.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-batting?key=<API_KEY>&playerId=8733'
GET /api/project/cricbuzz-cricket/players-get-bowling

Get a cricket player's bowling statistics table by playerId, with Test, ODI, T20 and IPL columns and an optional seriesId filter

Full docs β†’
Details

Returns one player's bowling statistics as a table. Send playerId in the URL path (required number; the default 8733 is the documented example value) and, optionally, seriesId as a query parameter to limit the stats to one series. The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a headers array (ROWHEADER, Test, ODI, T20, IPL), a seriesSpinner array whose single entry has seriesName set to Career, and a values array. Each element of values is an object that holds its own values array of strings: the first string is the row label and the strings after it line up with the headers that follow ROWHEADER. The example rows are Matches, Innings, Balls, Runs, Maidens, Wickets, Avg, Eco, SR, BBI, BBM, 4w, 5w and 10w. Every figure is delivered as a string, and a player with no bowling innings shows 0, 0.0 or -/- placeholders, as the example for the default id does (70 matches in the Test column but 0 innings). No live probe was recorded for this endpoint, so every response field described here comes from the source example and is not independently verified. How the table and the seriesSpinner entries change when seriesId is set is not described in the supplied evidence, and coverage can differ by player and series.

Explicitly submit this cricket request 1 required Β· 1 optional
ParameterInValue
path
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-bowling?key=<API_KEY>&playerId=8733'
GET /api/project/cricbuzz-cricket/players-get-career

Get a cricket player's career debut and last-played details per format by playerId, with opponent, date, venue and match IDs

Full docs β†’
Details

Returns a player's career milestones by competition format. The only input is playerId, a required number sent in the URL path (the default 8733 is the documented example value). The source 200 example is an object with an appIndex object (seoTitle and webURL strings) and a values array with one entry per format. Each entry has a name (t20, test, odi, ipl and cl in the example), a debut string, a lastPlayed string and, for formats the player has appeared in, debutMatchID and lastPlayedMatchId as numeric strings. The debut and lastPlayed strings are free text in the pattern opponent, date (YYYY-MM-DD) and venue, for example a line that starts with vs followed by a team name; the example contains a doubled space after the first comma. For a format the player never appeared in, the example shows the text Not played in both debut and lastPlayed and omits the two match ID fields. The entries are not sorted in a documented order, and the spelling of the two match ID keys differs (debutMatchID and lastPlayedMatchId), so read each key exactly as returned. No live probe was recorded for this endpoint, so every response field described here comes from the source example and is not independently verified. This operation gives debut and last-played markers, not a per-match history or career totals.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-career?key=<API_KEY>&playerId=8733'

Teams

GET /api/project/cricbuzz-cricket/teams-get-stats

Get cricket team statistics by teamId and statsType, narrowed by match type, opponent, team or year, with match-type and team filter lists in the payload

Full docs β†’
Details

Returns a statistics view for one cricket team. Send teamId in the URL path (required number; the default 2 is the documented example value) and statsType as a required query string (the default mostRuns is the documented example value). Four optional numeric query parameters narrow the view: matchType, opponent, team and year (a calendar year, with 2021 as the documented example). None of the optional parameters has a default. teamId is the teamId field returned by the teams list operation, and statsType is the value field returned by the team stats filter operation. matchType, opponent and team are documented as values returned by this same endpoint: the matchTypeId field for matchType and a teamId field for opponent and team. The source 200 example is an object with an appIndex object (seoTitle and webURL strings) and a filter object. filter.matchtype lists matchTypeDesc and matchTypeId strings (test 1, odi 2 and t20 3 in the example), filter.selectedMatchType and filter.selectedTeam hold the active selections (t20 and IND in the example), and filter.team is a long array of entries with an id string and a teamShortName string that covers national, women's and franchise sides. The entries in the visible example use id rather than the teamId name mentioned in the parameter notes. The supplied example is cut off inside the filter.team array, so the statistics rows that statsType returns are not visible in the evidence and are not described here. No live probe was recorded for this endpoint, so every field described comes from the source example and is not independently verified. The teamId path parameter and the team query parameter are separate inputs and are not documented as interchangeable.

Explicitly submit this cricket request 2 required Β· 4 optional
ParameterInValue
path
query
query
query
Optional filters and paging cursors (2)
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-stats?key=<API_KEY>&teamId=2&statsType=mostRuns'
GET /api/project/cricbuzz-cricket/teams-get-players

Get the player list for a cricket team by teamId

Full docs β†’
Details

Returns the player list for one cricket team. The single required path input is teamId, a numeric team identifier taken from the teamId field of the teams list endpoint; the default example value is 2. The source response example shows a top-level player array whose rows are either role headings (a name such as BATSMEN, ALL ROUNDER, WICKET KEEPER or BOWLER with only an imageId) or player rows with id (string), name, imageId, battingStyle and, for most non-keeper players, bowlingStyle. No live probe was recorded for this operation, so these fields come from an unverified source example and the example list may be truncated; treat optional style fields as possibly absent. This is a team-level roster, not a match squad or a series-edition squad.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-players?key=<API_KEY>&teamId=2'
GET /api/project/cricbuzz-cricket/teams-get-results

Get completed match results for a cricket team by teamId

Full docs β†’
Details

Returns match results for one cricket team. The single required path input is teamId, a numeric team identifier taken from the teamId field of the teams list endpoint; the default example value is 2. The source response example shows a top-level appIndex object with navigation metadata and a teamMatchesData array. Result entries use a matchDetailsMap whose key is the series name, with a match array and a seriesId. Each match has matchInfo (matchId, matchDesc, matchFormat, state, status, hideScoreStatus, startDate and endDate as millisecond epoch strings, seriesId, seriesName, team1 and team2 with teamId, teamName, teamSName and imageId, and venueInfo with id, ground, city and timezone) and, when scores exist, matchScore with per-team innings runs, wickets and overs. Some array entries are advertisement slots with an adDetail object instead of match data, and an abandoned match in the example has no matchScore. No live probe was recorded, so these fields come from an unverified, possibly truncated source example. The path takes no documented paging or date-range inputs.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-results?key=<API_KEY>&teamId=2'
GET /api/project/cricbuzz-cricket/teams-get-schedules

Get upcoming scheduled matches for a cricket team by teamId

Full docs β†’
Details

Returns the scheduled matches for one cricket team. The single required path input is teamId, a numeric team identifier taken from the teamId field of the teams list endpoint; the default example value is 2. The request path ends in /schedule. The source response example shows a top-level appIndex object with navigation metadata and a teamMatchesData array. Fixture entries use a matchDetailsMap whose key is a date label such as Tue, 06 Oct 2026, with a match array and a seriesId. Each match has matchInfo (matchId, matchDesc, matchFormat, state such as Preview or Upcoming, status and hideScoreStatus text such as Match starts at Oct 06, 13:30 GMT, isTimeAnnounced, startDate and endDate as millisecond epoch strings, seriesId, seriesName, series start and end dates, team1 and team2 with teamId, teamName, teamSName and imageId, and venueInfo with id, ground, city and timezone). Some array entries are advertisement slots with an adDetail object instead of fixture data. No live probe was recorded, so these fields come from an unverified, possibly truncated source example. The path takes no documented paging or date-range inputs.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-schedules?key=<API_KEY>&teamId=2'
GET /api/project/cricbuzz-cricket/teams-list

List cricket teams by type: international, league, domestic or women

Full docs β†’
Details

Returns the team directory for one team category. The single required path input is type, which the endpoint documents as one of international, league, domestic or women; the default is international. A live probe with type=international returned HTTP 200 and a JSON object with a list array (40 rows) and an appIndex object holding seoTitle and webURL strings. In that probe, list mixes two row shapes: team rows carrying teamId (number), teamName, teamSName and imageId, with countryName present on some of them, and section heading rows that contain only teamName, such as Test Teams and Associate Teams. Only the international type was probed; the shape for league, domestic and women is not verified and may differ in grouping or in which optional fields appear. Use the teamId values with other team endpoints for players, results, schedules, news and stats.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-list?key=<API_KEY>&type=international'

Records

GET /api/project/cricbuzz-cricket/stats-get-record-filters

List the cricket record types (statsType values) accepted by the records operation, grouped into Batting and Bowling with display headers

Full docs β†’
Details

Returns the catalog of record types that the cricket records operation of this product accepts in its statsType parameter. The operation takes no parameters: there is no path, query or body input to set. The source 200 example is an object with a statsTypesList array. Each element has a category string and a types array, and each entry of types has a category string, a header string (the display label, such as Most Runs) and a value string (the machine value to send as statsType, such as mostRuns). The example lists two groups: Batting with nine types (mostRuns, highestScore, highestAvg, highestSr, mostHundreds, mostFifties, mostFours, mostSixes, mostNineties) and Bowling with six types (mostWickets, lowestAvg, bestBowlingInnings, mostFiveWickets, lowestEcon, lowestSr). The header of bestBowlingInnings is Best Bowling followed by a trailing space in the example, so trim display labels before comparing them. The example contains no team or match type lists; those filters appear in the response of the records operation itself. No live probe was recorded for this endpoint, so every field described here comes from the source example and is not independently verified, and the evidence does not show whether the list changes by season or coverage.

Explicitly submit this cricket request 0 required Β· 0 optional

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/stats-get-record-filters?key=<API_KEY>'
GET /api/project/cricbuzz-cricket/stats-get-records

Get cricket records such as most runs by statsType (default mostRuns), optionally narrowed by matchType, team, opponent and year, as a headers array plus player rows

Full docs β†’
Details

Returns a cricket record table for one record type. statsType is the only required input: a query string whose default mostRuns is the documented example value, and whose accepted values come from the value field of the record filters operation of this product. Four optional numeric query filters narrow the table: matchType (the matchTypeId from the filter.matchtype list of this operation's own response), team and opponent (team ids from the filter.team list of this operation's own response), and year (a calendar year such as 2021). The source 200 example is an object with an appIndex object (seoTitle and webURL strings), a filter object, a headers array and a values array. In the filter object, matchtype lists matchTypeDesc and matchTypeId strings (test 1, odi 2 and t20 3 in the example), selectedMatchType is a string (t20 in the example) and team lists id and teamShortName strings (twelve teams such as IND with id 2 and PAK with id 3). The headers array is Batter, M, I, R, SR in the example, and each element of values is an object that holds its own values array of strings: the first string looks like a numeric player id, the second is the player name, and the four that follow line up with the M, I, R and SR columns. The saved example is cut off after several dozen rows, so the full row count is not confirmed, and the evidence does not say which request parameters produced it or how headers change for other statsType values. No live probe was recorded, so every response field described here comes from the source example and is not independently verified.

Explicitly submit this cricket request 1 required Β· 4 optional
ParameterInValue
query
query
query
Optional filters and paging cursors (2)
ParameterInValue
query
query

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/stats-get-records?key=<API_KEY>&statsType=mostRuns'

Venues

GET /api/project/cricbuzz-cricket/venues-get-stats

Get cricket statistics for one venue by venueId: matches played, wins batting or bowling first, average scores and highest and lowest totals as key and value pairs

Full docs β†’
Details

Returns a summary of historical statistics for one cricket venue. Send venueId in the URL path (required number; the default 24 is the documented example value). The id comes from the id field returned by the series venues operation of this product. The source 200 example is an object with a venueStats array of key and value string objects, eight entries in total: Total Matches (48), Matches won batting first (7), Matches won bowling first (19), Avg. scores recorded (a multi-line string, 1st inns-310, 2nd inns-337, 3rd inns-261 and 4th inns-159 separated by newline characters), Highest total recorded (765/6(248.5) by PAK vs SL), Lowest total recorded (80/10(53.1) by AUS vs PAK), Highest score chased (315/9(106.1) by PAK vs AUS) and Lowest score defended (149/10(47.1) by SL vs PAK). Every value is text, including counts and scores, and the total and result counts in the example are not guaranteed to add up, so do not derive percentages without checking. The evidence does not say which venue the example belongs to, which match formats are counted, or how the list changes for other venues. No live probe was recorded, so every response field described here comes from the source example and is not independently verified. These are historical figures, not a pitch report, weather feed or forecast.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/venues-get-stats?key=<API_KEY>&venueId=24'
GET /api/project/cricbuzz-cricket/venues-get-info

Get cricket venue details by venueId

Full docs β†’
Details

Returns the profile of one cricket ground. The single required path input is venueId, a numeric venue identifier taken from the id field returned by the series venues endpoint; the default example value is 45. The source response example is a flat JSON object with ground, city, country, timezone, homeTeam, ends, capacity, imageId and imageUrl. In that example capacity is a formatted string (11,600), imageId is a string, ends lists the named ends of the ground as one comma-separated string and timezone is a UTC offset string such as +13:00. No live probe was recorded for this operation, so these fields come from an unverified source example; treat each field as optional and expect values to vary by venue. The example contains no coordinates, pitch report or ticketing fields.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/venues-get-info?key=<API_KEY>&venueId=45'
GET /api/project/cricbuzz-cricket/venues-get-matches

Get scheduled cricket matches at a venue by venueId

Full docs β†’
Details

Returns the scheduled matches for one cricket ground. The single required path input is venueId, a numeric venue identifier taken from the id field returned by the series venues endpoint; the default example value is 45. The source response example shows a top-level matchDetails array whose entries hold a matchDetailsMap with a key (the series name, such as a domestic one-day trophy) and a match array of matchInfo objects, plus an appIndex object with seoTitle and webURL. Each matchInfo carries matchId, matchDesc, matchFormat, state, status, hideScoreStatus, isTimeAnnounced, startDate and endDate (epoch milliseconds as strings), seriesId, seriesName, seriesStartDt, seriesEndDt, team1 and team2 (teamId, teamName, teamSName, imageId) and venueInfo (id, ground, city, timezone). No live probe was recorded for this operation, so these fields come from an unverified source example, and the example is truncated. It covers scheduled fixtures, not a complete archive of past results at the ground, and a venue with nothing scheduled can return no content.

Explicitly submit this cricket request 1 required Β· 0 optional
ParameterInValue
path

Request cost is temporarily unavailable. No price is assumed.

View pricing
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/venues-get-matches?key=<API_KEY>&venueId=45'

Matches, scorecards, commentary, series, players, news and IPL/WPL auctions

Structured cricket data over a simple JSON API: find live, recent and upcoming matches, then follow the IDs in each response to scorecards, commentary, series, teams, players and venues.

  • Match lists & schedules: live, recent and upcoming matches plus schedule feeds by competition type, with match IDs, teams, venues and status text
  • Match center: full and mini scorecards, live score panels, ball-by-ball and player commentary, highlights, over summaries, graphs and squads, including The Hundred variants
  • Series & teams: series lists and archives by year, squads, venues, points tables, team players, fixtures and results
  • Players & venues: name search, profiles, batting, bowling and career statistics, trending players, venue details and ground statistics
  • Rankings & records: ICC player and team rankings by format, ICC standings by season, and filterable record leaderboards
  • News, photos & video: stories by category, topic, team, player, series or author, photo galleries, Buzz items and match video lists
  • Fantasy research: match player lists, forecasts, batter-versus-bowler matchups, pitch notes and expert picks (research data, not fantasy points)
  • IPL & WPL auctions: supported seasons, player outcomes, team purse summaries, purchased players and bid interest

RESTful JSON API for live score widgets, match-center pages, sports media, analytics, tournament companions and fantasy research tools. Coverage varies by competition, and some resources return no content when a feed has nothing to show.

Guides