Legacy API

The stable compatibility contract served under /api for existing applications and integrations.

The legacy API is the compatibility surface for existing clients. Its routes remain under /api; the v1 in this documentation URL is a label, not an additional runtime path.

https://statshub.com/api

V1 route explorer

Search, filter, map, and inspect all 299 legacy operations.

V1 endpoint reference

Schemas, parameters, authentication requirements, and a request playground for legacy routes.

V1 OpenAPI schema

A legacy-only OpenAPI 3.1 document for client generation.

Value Bets V2

The prose reference for the legacy /api/value-bets-v2 endpoint.

Existing paths, query parameters, status codes, and response bodies stay compatible with the original Next.js API. Use this contract when an existing application must keep working without a migration.

The suffix in /api/value-bets-v2 is part of that endpoint's name. It does not place the route in the canonical /api/v2 contract.

Authentication

Most reads are public. Protected operations accept the existing Supabase bearer token or session behavior. The endpoint reference marks authentication per operation.

Machine-readable contract

Use openapi-v1.json when a client calls only legacy routes. The combined contract remains available for tooling that intentionally spans both versions.