Developer API
Build on ZKickoff data
Read-only JSON APIs over your competition data and public profiles. We don’t self-mint keys — request access below and we approve by hand. API access is part of a paid, higher-tier plan.
Your competition data (leagues & tournaments)
Higher planRead your own event's live snapshot — divisions, teams, schedule, standings, brackets and results — with an org-scoped key (zk_live_…) tied to your organization. Generate and revoke it yourself in the Organizer Portal → your event → Data & API; a token only ever reads events your org owns. Offered on our paid plans — see pricing for scope.
/api/v1/events/{id}org-scopedA read-only JSON snapshot of one of your events. Returns 403 if the token doesn't own the event.
curl https://zkickoff.com/api/v1/events/evt_… \
-H "Authorization: Bearer zk_live_…"Public profiles (players · referees · coaches)
Read the public profile data those pages already show — nothing private, and only for people who opted in. Scoped read keys (zk_pk_…).
/api/v1/players/{code}player:readA player passport — identity, positions, languages, career totals, competition history, self-assessment (only what the player made public).
/api/v1/referees/{code}referee:readA referee profile — roles, grade, stats, competitions officiated, and verified credentials.
/api/v1/coaches/{code}coach:readA coach profile — coaching experience, languages, and verified credentials.
Authentication
Send your key on every request, either header works:
Authorization: Bearer zk_pk_…
X-API-Key: zk_pk_…Keys are rate-limited per minute and scoped to exactly the resources you were granted. Contact details (email, phone) and dates of birth are never returned.
Example
curl https://zkickoff.com/api/v1/players/ABC1234 \
-H "Authorization: Bearer zk_pk_…"Returns { "data": { … } }, or 404 if the profile is private or unknown.