Cricket score and schedule snapshots
Cricbuzzエンドポイントを使えば、「Cricket score and schedule snapshots」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Follow cricket across international, league, domestic, and women's fixtures; resolve dynamic team-stat filters and carry canonical match, edition, and story URLs into detail routes.
Collect Cricbuzz match snapshots, schedules, series, scorecards, team statistics, rankings, auction news, and public story details as structured JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
122
サンプル数
35
ライブカタログスナップショット
稼働エンドポイント
35
メソッド
GET
必須パラメータ
78
スキーマ参照
35
{
"platform": "Cricbuzz",
"endpoint": "cricbuzz-matches",
"method": "GET",
"path": "/cricbuzz/matches",
"auth": "apiKey"
}ユースケース
Collect Cricbuzz match snapshots, schedules, series, scorecards, team statistics, rankings, auction news, and public story details as structured JSON.
Cricbuzzエンドポイントを使えば、「Cricket score and schedule snapshots」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Cricbuzzエンドポイントを使えば、「Team batting and bowling tables」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Cricbuzzエンドポイントを使えば、「Series and ranking research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Cricbuzzエンドポイントを使えば、「Auction roster and result analysis」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Cricbuzzエンドポイントを使えば、「Cricket news and live-blog snapshots」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のCricbuzzエンドポイントカタログから取得しています(エンドポイント35件、ドキュメント化されたリクエストパラメータ122個、公開レスポンススキーマ35件)。DocsとPlaygroundが参照しているカタログと同じものです。
Cricbuzzのエンドポイントは35件、17つのリクエストファミリーに分類されています(Auction、News、Seriesほか14件)。
これらのCricbuzzエンドポイントには122個のリクエストパラメータがドキュメント化されており、うち78個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
35件のCricbuzzエンドポイントのうち35件が実際のサンプルレスポンスを、35件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Cricbuzzのエンドポイントは成功時のスキーマに加えてエラーレスポンス(400、404、429、503)もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Cricbuzzのエンドポイントは35個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
/cricbuzz/auction/seasons
/cricbuzz/news/topics
/cricbuzz/series
/cricbuzz/team/stats/options
/cricbuzz/videos/categories
/cricbuzz/archives
主要エンドポイント
/cricbuzz/matchesReturns Cricbuzz match cards grouped by source category and series, including teams, scores when available, venue, time, status, and the canonical live-score URL for detail endpoints. The homepage-only Live Now and Today controls are not included because their effects were not verified. Category filtering is local over the route-backed match groups.
MCPツール cricbuzz_matches
/cricbuzz/scheduleReturns every match in the current date window shown by Cricbuzz's Matches By Day page, grouped by date and series. Category and q filters run locally over that complete page payload. The date window is dynamic and can change with the upstream page.
MCPツール cricbuzz_schedule
/cricbuzz/seriesReturns current and future series grouped by month, with series IDs, dates, and canonical URLs. Filter by the live route-backed category, the Live Streaming flag, or a local case-insensitive series-name substring. Live Streaming may validly return an empty result set when Cricbuzz has no matching entries at the time of the request.
MCPツール cricbuzz_series
/cricbuzz/scorecardReturns match header, toss/result, teams/venue, and every innings' batting, bowling, totals, extras, powerplays, wickets, and partnerships. Pass the canonical match URL returned by /cricbuzz/matches. Future matches can return an explicit no_scorecard state. Media assets are not returned.
MCPツール cricbuzz_scorecard
/cricbuzz/match-factsReturns the public Info-tab match title, toss, venue guide, umpires, third umpire, referee, both team squads, bench players, and support staff. Use the canonical match URL returned by /cricbuzz/matches. Squad member links are preserved where Cricbuzz publishes them.
MCPツール cricbuzz_match_facts
/cricbuzz/match-graphsReturns the first-party Graphs page's runs, run-rate, runs-per-over, win-probability, innings, and wicket-over values. Commentary prose and media are omitted. Pass the canonical match URL returned by /cricbuzz/matches.
MCPツール cricbuzz_match_graphs
関連API
Sports & Gaming
Browse public sports and event data from FanDuel Sportsbook. Discover market-specific event types, follow a league or schedule, and read the markets and prices FanDuel publishes for that event and market.
Sports & Gaming
Follow public horse-racing cards across tracks and countries. Discover today's tracks, inspect races and runners, and read official results, wager-type reference data, and published pool information without placing a wager.
Sports & Gaming
Explore FanDuel Research's public editorial and sports-data surfaces. Discover sport slugs and teams, read articles and player updates, inspect live fixtures, and retrieve the published projection tables with their source-specific slate identifiers.
Cricbuzzのスクレイピング方法
Cricbuzz describes its cricket coverage as live scores, ball-by-ball reporting, news, match reports, editorials, and expert video; Times Internet lists Cricbuzz among its products. Crawlora's 35 production-published routes now include match and schedule snapshots, series, scorecards, rankings, auction records, edition-scoped auction news and videos, public NewsArticle details, and team batting/bowling tables. The team-stat options call returned 3 format IDs, 91 year values, and 983 opponent values for India; following those returned filters produced 12 ODI runs rows for 2025 vs Australia on 2026-10-30. A 2026-10-30 production check returned two SA20 2027 auction-news cards and ten IPL 2026 auction-video cards; the IPL live-blog and canonical story routes returned public article metadata and body fields. Auction cards are changing page snapshots without source pagination, and a live-blog route can return 404 when an edition has no Live Blog tab. `/cricbuzz/news/story` requires a canonical story URL and does not unlock premium or login-gated content. Cricbuzz's terms describe its editorial and media content as proprietary; API access does not grant redistribution rights. The routes expose author names on returned stories, but no author-profile or byline-search operation.
`/cricbuzz/matches` accepts `status=live`, `recent`, or `upcoming` and category `all`, `international`, `league`, `domestic`, or `women`. A recent response on 2026-10-29 contained 67 matches in four groups. Store the fetch time and returned match URLs; the list changes as matches move between states.
`/cricbuzz/schedule` returns the dates currently present on Cricbuzz's Matches By Day page. Its category filter and `q` match series, descriptions, and team names locally; there is no arbitrary from/to date range or page cursor, so it is not a historical schedule API.
Pass a match `url` returned by `/cricbuzz/matches` as `match_url` to `/cricbuzz/scorecard`, `/match-facts`, `/match-graphs`, and `/match-overs`. Do not construct a URL from a title or reuse a numeric ID from another source; the source URL is the route key.
Use `/cricbuzz/series` to discover a series and its canonical `series_url`; `/cricbuzz/series-stats` takes that URL plus a stat topic and format from the response's current options. Preserve the format and fetch time because tables may differ across Test, ODI, and T20 views.
Use `/cricbuzz/teams` to choose a category and copy a team ID from its returned directory. Call `/cricbuzz/team/stats/options` with that category and ID, then pass one returned stat, format ID, year, and opponent ID to `/cricbuzz/team/stats`. A live India request returned the current formats, years, and opponents; the 2025 ODI most-runs table for Australia returned 12 rows. There is no sort parameter, and the options cache can identify stale fallback data.
Start with `/cricbuzz/auction-seasons` and the matching options routes for the tournament and year. Results and unauctioned players use one-based `page` values and source-owned role, country, cap, status, and sort values; carry IDs from the same edition into team/player detail.
`/cricbuzz/auction/news` and `/auction/videos` require a supported `tournament` and `year`. Their cards have no source sort, filter, or page controls; an explicit publisher empty-state is returned as an empty list. Video cards contain metadata and canonical page URLs, not a playback URL.
Pass a canonical `url` from auction news, `/cricbuzz/news/topics`, or another Cricbuzz story page to `/cricbuzz/news/story` for its public NewsArticle metadata, body text/HTML, links, authors, dates, and tags. `/cricbuzz/auction/live-blog` takes `tournament` and `year` and only exists when that edition has a Live Blog tab; preserve 404s for editions without one. Neither route provides premium or login-gated access, and no author profile or byline search is exposed.
FAQ
No. `/cricbuzz/schedule` mirrors the current Matches By Day page window. It filters those rows but does not accept a date range, page number, or historical season selector.
Take the canonical `url` from `/cricbuzz/matches` and pass it unchanged as `match_url` to the scorecard, facts, graphs, or overs route. The API does not accept a guessed title or numeric match ID for these details.
A public canonical story URL can be passed to `/cricbuzz/news/story`, and an available edition Live Blog can be read with `/cricbuzz/auction/live-blog`. These return public story body fields; they do not unlock premium or login-gated pages. Author names may appear in a story response, but there is no author-profile or byline-search route.
`/cricbuzz/auction/videos` returns edition-scoped card metadata and canonical page URLs, not a media or playback URL. The source card list has no page or sort control.
No. Cricbuzz's terms describe its site content as proprietary. Keep canonical source links and follow the publisher's terms; access to a returned story body is not a redistribution license.
Use only the values returned by the matching auction options route for the chosen tournament and edition. The result lists are page-numbered, and team or player IDs must come from that same tournament/year.
No. The 67-match total was one `recent`/`all` production snapshot on 2026-10-29. Retain the response's `fetched_at`, state, category, and canonical URLs rather than treating a changing list as a historical total.