Base URL
Authentication
All requests require an x-api-key header:
Cricket-Specific Notes
- Multiple formats — Test (5 days, up to 4 innings), ODI (50 overs/side), T20 (20 overs/side)
- Score format —
185/6 (20) = 185 runs for 6 wickets in 20 overs
- Innings scoring —
period1 through period4 (Tests use up to 4, limited-overs use 2)
- Playing XI — 11 players per side, lineups available via match endpoint
- Categories — Cricket-playing nations (Pakistan=1352, New Zealand=1354, Sri Lanka=1356, etc.)
- All out — 10 wickets = innings ends (11 players, 1 stays not out)
- Target — Second team needs first team’s score + 1 to win
- DLS method — Adjusted target in rain-affected matches
- Run rate — Runs scored per over (e.g., 9.25 r/o in T20)
Key Cricket Statistics
Endpoint Categories
Example Requests
UI Design Ideas
- Scorecard display: Show runs/wickets format: “India 185/6 (20 ov)” — not just a number
- Innings tabs: For Tests, show tabs for each innings (1st Innings, 2nd Innings per team)
- Run rate graph: Use
/match/{id}/graph — show required rate vs actual rate for chases
- Playing XI: Use
/match/{id}/lineups — show batting order, bowlers, keeper, captain
- Batting & bowling cards: Individual batting (runs, balls, 4s, 6s, SR) and bowling (overs, maidens, runs, wickets, economy)
- Man of the Match: Use
/match/{id}/award — always awarded in cricket
- Format indicator: Always show T20/ODI/Test prominently — changes how to interpret scores
- H2H records: Important in rivalries (India vs Pakistan, Ashes) — use
/match/{id}/h2h
Real-time updates (WebSocket)
Cricket live push is fully enabled — scores stream over NATS with sub-second latency, so you
can replace REST polling entirely.
The /v2/cricket/ws path scopes the sport for you — no x-sport header is needed. The
welcome frame echoes "sport": "cricket" and the subscribed frame confirms
live-scores:cricket.
Frames carry the cricket score shape, including per-innings runs, wickets, overs and run
rate:
WebSocket traffic is unmetered — the handshake, subscriptions and every frame are free.
Only REST calls count against your daily quota.
See the WebSocket reference for the full channel
list, message types and reconnection guidance — the gateway is shared across all V2 sports.