Endpoint reference

Every public REST endpoint on api.bigballsdata.com. Open any row to see the full field tree, the plan tier, the update cadence, and a copy-ready curl example.

Authentication: all /v1/* endpoints require an API key in the Authorization: Bearer ... header or the x-api-key header.

Each row also carries a live reading from our own endpoint health checks — which sports the route is currently returning data for, out of the sports we probed. Where we have not observed a route, the row says status unknown and why, rather than leaving it blank.

89 endpoints · 1609 documented fields. Click any row to see every field it returns. 59 of 89 carry a live status; the rest read status unknown and say why.

Endpoints land here as the data layer is populated per sport. For the complete machine-readable contract see /openapi.json.