Get started

Make your first useful request.

Confirm the data fits, create a workspace and API key, then call the same public API contract you can inspect before signing in.

1. Explore live dataCheck published coverage and freshness before integrating. 2. Inspect the contractReview the customer OpenAPI definition without signing in. 3. Create API accessCreate or sign in to a workspace and issue a key.
1

Confirm the product fits

Use Coverage and the API console to confirm the competition, season, capability and freshness you need.

Explore live dataCheck coverage
2

Inspect the API before committing

The filtered customer OpenAPI contract is public and excludes operator/provider internals.

Browse API docsOpen JSON
3

Create or sign in to your workspace

Account manages workspace access, API clients, credentials, usage, onboarding milestones and plan state.

Open account
4

Create an API client and key

Create a separate client for each application/environment where practical. Save the secret when shown; SportsFoundry does not retain a reversible copy for later display.

5

Make an authenticated request

Send the key in the X-API-Key header to the stable SportsFoundry domain.

curl -s https://sportsfoundry.app/api/v1/sports \ -H "X-API-Key: $SPORTSFOUNDRY_API_KEY"
6

Choose your integration style

Stay with raw HTTP or use the first-party JavaScript, Python, Java or .NET client built from the same contract.

SDKs & examplesMigrating from another API?
Having trouble? A 401 usually means the API key is missing or invalid; 403 means the key/plan does not allow the operation; 429 means a limit was reached. Keep X-Correlation-Id when contacting support.