Platform API

Your tournament data, one Bearer token away

Read standings into your club site, push live scores from your own scoreboard, automate entries. REST, OpenAPI 3.1, an envelope that never surprises you.

60-second start

# 1. Create a key in Org settings → Platform API (Pro)
# 2. Read your competitions
curl https://seazn.club/api/v1/competitions \
  -H "Authorization: Bearer sc_your_key"

# → { "ok": true, "data": { "items": [...] }, "requestId": "…" }

Three scopes, one ladder

Every key carries a scope; every endpoint declares the scope it needs (x-required-scope in the spec). Higher rungs include the lower ones.

read

Fetch everything your org can see — competitions, fixtures, standings, registrations.

score

Push score events and start divisions. Built for scoreboard integrations.

manage

The full surface: create, generate, schedule, moderate. Treat it like a password.

Public dashboards need no key at all — the public tag is open, cacheable JSON.

API reference

Every operation with schemas, examples and a try-it console.

Guides

Auth & scopes, reading standings, pushing live scores.

Changelog & versioning

Additive changes announced here; breaking changes get a new version path.

Rate limits: 60 requests/minute per key (300 on Pro). Every response carries X-RateLimit-Limit / -Remaining / -Reset; a 429 uses the standard error envelope.

Pin a key: limit it to one competition when handing it to a vendor — it can’t touch anything else.