League data,
on your own site.
A read-first REST API over the games your league tracks on UnderDraft — scores, standings and player stats, served by Pulse. The developer portal and OpenAPI reference are live today; keys, analytics endpoints and widgets are rolling out through early access.
- Style
- REST · JSON
- Spec
- OpenAPI 3.1
- Methods
- Read-only GET
- Version
- /v1
curl https://underdraft-pulse-z44juzncbq-uk.a.run.app/v1/health{
"status": "ok",
"service": "underdraft-pulse"
}How it fits together
From the scorekeeper's tap to your website.
Every game tracked on UnderDraft becomes structured data. Pulse turns it into stats and scores; the API hands it to you.
- 01
Games tracked
Scorekeepers log every play in the sport-specific trackers on UnderDraft.
- 02
Pulse computes
The stats engine rolls events into stat lines, standings and performance scores.
- 03
The API serves
Documented, versioned, read-only endpoints — with keys issued from the portal.
- 04
Your site shows it
League websites, club apps, dashboards and embeds — kept current automatically.
Endpoint catalog
Every route, and whether you can call it yet.
All endpoints are read-only GETs under /v1, documented in the OpenAPI reference.
/v1/healthService health check
Live/v1/players/{id}/statsSeason stat line for a player
In development/v1/players/{id}/snapshotStat line plus Pulse performance score
In development/v1/teams/{id}/analyticsTeam form, trends and splits
In development/v1/leagues/{id}/insightsLeague health score and churn risk
In development/v1/leagues/{id}/demand-forecastProjected sign-ups for upcoming seasons
In development/v1/seasons/predictSeason projections for a league
In development/v1/embed/league/{id}/scoreboardEmbeddable league scoreboard
In development/v1/embed/player/{id}/cardEmbeddable player card
In development/v1/embed/team/{id}/cardEmbeddable team card
In developmentBuilt to be trusted
Straight answers about what works today.
Read-first by design
Every endpoint is a GET. Integrations can display league data; they cannot change it.
Rate limited
Per-client rate limits protect the service for every league that depends on it.
Documented from the source
The reference is generated from the live OpenAPI spec, so it never drifts from the code.
Versioned
Everything lives under /v1. Breaking changes ship as a new version, never in place.
Developer portal
AvailableSign in, read the guides and manage your developer account.
Interactive API reference
AvailableEvery endpoint, parameter and response shape, generated from the live OpenAPI spec.
API keys
In developmentLive and test keys you create and revoke from the portal. Keys are stored hashed and shown once.
League, team & player analytics
In developmentThe player, team and league endpoints in the catalog above.
Embeddable widgets
In developmentDrop a live scoreboard or player card into any website with one script tag.
Webhooks
In developmentSigned notifications when scores change or games are scheduled.
FAQ
Questions developers ask.
Can I use the API today?
You can explore the developer portal and the full API reference now, and the health endpoint is live. Data endpoints and API keys are rolling out to early-access developers first — request access and we will reach out as they open.
Where does the data come from?
From games tracked on UnderDraft. Scorekeepers log plays in the sport-specific trackers, and Pulse turns those events into stats and scores. Nothing is scraped or imported from elsewhere.
Can an integration change league data?
No. The API is read-only — every endpoint is a GET. Scores and rosters are only ever changed inside UnderDraft by the people running the league.
Which sports are covered?
The API serves data for every sport tracked on UnderDraft. Pulse performance scores launch first for soccer, basketball and flag football, with more sports to follow.
Build with us early.
Early-access developers get keys and new endpoints first — and a say in what we build next.