Big Ball Sports API
API by Bigballsdata · rest
Unified sports data API (REST + GraphQL + WebSocket) aggregating 19+ free-tier upstream sources and 10 MCP scrapers behind a Stripe-style gateway. Every response carries a confidence score and source attribution so callers can render appropriate caveats. Pagination List endpoints page with ?limit= and ?offset=. ?page=N is an alias for ?offset=(N-1)*limit, resolved against that endpoint's own limit default, so ?page=2 and ?offset=<limit> are the same request. When both are sent, ?offset= wins; it is the more specific instruction. Endpoints that return a single page (leaderboards, one team's form, one player's stat line) document a limit and no offset. On those, ?page= is rejected with a 400 naming ?limit= rather than accepted and ignored, so a paging attempt can never silently look like it worked. Versioning /v1/ is the permanent namespace. A breaking change never ships as a second URL tree; it ships as a dated version (for example…
Endpoint: https://api.bigballsdata.com/
Verification: observed. Source: crawl.
Capabilities (166)
- Which point-in-time windows we actually observed per relation
- Availability designations as they stood at an instant
- The odds board as it stood at an instant
- The player-prop board as it stood at an instant
- Fetch an image we host
- List boxing and MMA athlete profiles
- Single athlete (fighter / boxer)
- Athlete fight record
- Single bout
- What we hold per sport and league (the discovery catalogue)
- List cricket matches
- Single cricket match
- Cricket ball-by-ball deliveries
- Cricket match scorecard
- Cricket live match state
- Cricket player career profile
- List cricket series
- Finishing positions for a Formula 1 session
- List fight cards (MMA / boxing)
- Single fight card
- World Cup group-standings formula
- World Cup progression formula
- Cross-sport games strip with live scores + odds
- Multi-book line shopping for one match (sport-agnostic)
- 5-minute snapshot timeline of moneyline + spread + total