Public API

Read-only tournament data for discovery clients

This surface is intentionally small. It exposes public tournament facts that agents, search systems, and lightweight integrations can consume without scraping page HTML.

Catalog

/.well-known/api-catalog lists the public APIs.

Spec

/docs/api/openapi

Status

/api/health

Response envelope

Public data endpoints return JSON in a stable envelope with `type`, `data`, and `lastUpdated`. The schedule endpoint can also include a `message` while the schedule is not yet published.

{
  "type": "teams | divisions | schedule | venues",
  "data": [],
  "lastUpdated": "ISO-8601 timestamp",
  "message": "optional"
}

Endpoints

Teams export

/api/data/teams

Current team list grouped by division and season.

Cache policy: public responses use shared caching with stale-while-revalidate.

Divisions export

/api/data/divisions

Division catalog with pricing and capacity fields.

Cache policy: public responses use shared caching with stale-while-revalidate.

Schedule export

/api/data/schedule

Schedule feed placeholder until match schedule is published.

Cache policy: public responses use shared caching with stale-while-revalidate.

Venues export

/api/data/venues

Venue metadata including address and coordinates.

Cache policy: public responses use shared caching with stale-while-revalidate.

Not public

Checkout, Stripe webhooks, lead management, and admin APIs are intentionally excluded from this public surface. They are not stable integration contracts and should not be relied on by crawlers or third-party agents.