\n
SDKs & examples

Use the API in your stack.

SportsFoundry keeps HTTP as the canonical contract and provides thin first-party clients generated from that same OpenAPI definition.

API v1 · SDK release 0.1.0-alpha.1 published
Start with the APIOpen OpenAPI JSON
Client libraries

One contract, four ecosystems.

Package versions follow semantic versioning independently of the long-lived /api/v1 contract. The clients stay deliberately thin: authentication, typed API surface, transport/errors and pagination rather than a second domain model.

PyPI · Python

sportsfoundry

sportsfoundry==0.1.0a1
pip install sportsfoundry==0.1.0a1
PublishedAPI v1Generated contract

View on PyPI

Maven Central · Java

sportsfoundry-java

app.sportsfoundry:sportsfoundry-java:0.1.0-alpha.1
implementation("app.sportsfoundry:sportsfoundry-java:0.1.0-alpha.1")
PublishedAPI v1Generated contract

View on Maven Central

NuGet · .NET

SportsFoundry

SportsFoundry 0.1.0-alpha.1
dotnet add package SportsFoundry --version 0.1.0-alpha.1
PublishedAPI v1Generated contract

View on NuGet

Publication status. Version 0.1.0-alpha.1 is published in all four supported registries. These are pre-release SDKs generated from the SportsFoundry API v1 contract; pin the version during the pilot and review release notes before upgrading.
Raw contract

HTTP always works.

The SDKs are convenience clients, not a different product. Every operation remains available through the documented HTTP contract.

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