What the Cricbuzz Cricket API does and who it is for
Cricket fans expect real-time data — live scores, over-by-over commentary, and up-to-the-minute squad changes. The Cricbuzz Cricket API surfaces all of that through a straightforward REST interface, pulling from the same data engine behind cricbuzz.com, one of the most-visited cricket properties on the web.
The API suits a wide audience: hobbyists building score widgets, media companies enriching cricket coverage, fantasy sports platforms that need player stats and rankings, or mobile app developers who want rich cricket content without maintaining a scraper. The 100% average success rate and 262 ms average latency suggest solid reliability for production use.
Key capabilities and endpoint walkthrough
The 53 endpoints fall into logical groups that map well to common product features.
Live match data
GET /matches/v1/live returns currently active matches, while GET /matches/v1/{type} lets you filter across live, recent, and upcoming states in a single call. Once you have a matchId, GET /mcenter/v1/{matchId} gives full match info — scorecards, team lineups, and status. For the play-by-play experience, GET /mcenter/v1/{matchId}/comm delivers ball-by-ball commentaries, which is the backbone of any live score product.
Schedules and series
GET /schedule/v1/{type} and GET /matches/v1/upcoming handle fixture listing. You can drill down to a specific series with GET /series/v1/{seriesId} for its matches, or fetch squad rosters with GET /series/v1/{seriesId}/squads and individual squad members via GET /series/v1/{seriesId}/squads/{squadId}. Archived series are available through GET /series/v1/archives/{type}, which is useful for historical research or displaying past tournament brackets.
Player and team stats
Player coverage is thorough. You can retrieve a player's general profile (GET /stats/v1/player/{playerId}), career summary (GET /stats/v1/player/{playerId}/career), batting figures (GET /stats/v1/player/{playerId}/batting), and bowling figures (GET /stats/v1/player/{playerId}/bowling). Trending players are accessible at GET /stats/v1/player/trending, useful for surfacing popular athletes in your UI.
On the team side, GET /teams/v1/{teamId}/players returns a team roster, while GET /teams/v1/{teamId}/results and GET /teams/v1/{teamId}/schedule let you build a team-specific results and fixtures view. Venue-level stats come from GET /stats/v1/venue/{venueId}, allowing pitch and ground analysis.
Rankings and standings
GET /stats/v1/rankings/{category} covers ICC rankings by category (batting, bowling, all-rounder), and GET /stats/v1/iccstanding/team/matchtype/{matchType} gives ICC team standings filtered by match format (Tests, ODIs, T20Is). Records are retrievable through GET /stats/v1/topstats/0 after calling GET /stats/v1/topstats to understand available filter options.
News and editorial content
The news group is notably complete. GET /news/v1/{type} lists the latest articles, and you can filter by category (GET /news/v1/cat/{categoryId}), topic, player, team, or series. GET /news/v1/detail/{newsId} fetches full article content. This makes it straightforward to build a cricket news feed that is contextually tied to a match, player, or team your users are already viewing.
Images and venues
GET /img/v1/i1/{imageId}/i.jpg retrieves images by ID, supporting photo galleries listed through GET /photos/v1/index. Venue info and scheduled matches per ground are covered by /venues/v1/{venueId} endpoints.
Pricing breakdown
| Plan | Price | Monthly requests | Rate limit |
|---|---|---|---|
| BASIC | $0 / month | 200 | — |
| PRO | $9.99 / month | 20,000 | 10 req/sec |
| ULTRA | $29.99 / month | 100,000 | 25 req/sec |
| MEGA | $139.99 / month | 1,500,000 | 100 req/sec |
The BASIC tier at 200 requests per month is intentionally narrow — enough to prototype and validate the response shapes but not enough to run even a small production widget that polls live scores every few minutes during a match. A single Test match day with per-minute polling across a handful of endpoints would exhaust that quota within hours.
PRO at $9.99 gives 20,000 requests, which suits a personal project or small app with modest traffic. ULTRA at $29.99 is marked as the recommended tier; 100,000 requests per month with a 25 req/sec ceiling is a reasonable budget for a mid-sized app that covers multiple simultaneous live matches. MEGA's 1.5 million requests and 100 req/sec is for high-traffic platforms, and it includes overage billing at $0.0002 per request if you exceed the monthly cap, giving you a known cost ceiling rather than a hard cutoff.
Practical use cases
- Live score apps and widgets: Combine
/matches/v1/live,/mcenter/v1/{matchId}, and/mcenter/v1/{matchId}/commfor a full live experience. - Fantasy cricket platforms: Player batting and bowling stats, career data, and trending players feed squad-selection and scoring engines.
- News aggregators: The categorized, player-, team-, and series-scoped news endpoints let you serve contextually relevant articles alongside scorecards.
- Sports analytics tools: ICC rankings, team standings, venue stats, and records endpoints provide enough structured data to build comparative dashboards.
- Chatbots and voice assistants: The clean REST structure and distinct endpoints for schedules, results, and rankings map naturally to question-answer flows.
Limitations and things to check before integrating
Request volume is the main constraint to plan for. Commentary polling during a live match can be request-intensive; you should implement client-side caching and only request commentary updates at sensible intervals rather than on every UI render.
The BASIC tier's 200-request cap means free usage is effectively limited to exploration. Budget at least PRO before committing to a live product. If you expect spikes during high-profile tournaments (World Cup finals, India vs. Pakistan fixtures), check whether the ULTRA rate limit of 25 req/sec is sufficient or whether you need MEGA headroom.
The API does not appear to offer webhook or streaming endpoints in the listed surface — it is a polling model. Real-time responsiveness depends on your polling frequency and your request budget.
With 53 endpoints, some parameter values (format types, category IDs, record filter values) are discovered dynamically via dedicated lookup endpoints like GET /news/v1/cat and GET /stats/v1/topstats. Build your integration to call these first and cache the reference data rather than hardcoding IDs.
Getting started
Subscribe on the marketplace (the API has over 27,000 existing subscribers, so onboarding is well-traveled). Start on BASIC to explore the response structures across schedule, match, player, and news endpoints. Draft your polling strategy before moving to a paid tier — map out which endpoints you call, how often, and during what event windows. That exercise will tell you whether PRO or ULTRA is the right starting point for your production workload.
