Useful context, in machine-readable form.

These resources explain how automated clients and agentic assistants can discover the public tournament and session experience without depending on JavaScript. Start with the OpenAPI specification, which describes public endpoints, response objects, operation identifiers, and the authentication boundaries around private family and staff data.

When to use the API

Use the public endpoints when an assistant needs to find an upcoming tournament, read a public tournament board, or guide a family to check-in. Parent, staff, and administrative endpoints remain protected by the application session and permission checks. Do not guess or scrape private player records.

Operational expectations

Responses are JSON, errors include a stable error code and a human-readable message, and rate-limited responses include standard RateLimit headers plus Retry-After. Clients should respect those values, retry only after the indicated delay, and preserve the request identifier when reporting a failure.