Scopes

A scope is a label that grants access to a specific group of endpoints. Your key is issued with one or more scopes - any endpoint not covered by your scopes returns 403 INSUFFICIENT_SCOPE.

Scope catalog

Scope	What it grants
org:read	Read organization details, list members, read your permissions
org:write	Update organization, add/update/remove members
super-events:read	List/read hackathons, read registration fields, role invites, teams
super-events:write	Update/delete hackathons, manage registration fields, create role invites
events:read	List/read events (tracks), event roles, setup status
events:write	Update/delete events, manage event roles, open/close registration
registrations:read	List and read participant registrations
registrations:write	Register a participant, update registrations and status, create participants via magic link, assign and switch tracks
teams:read	List and read teams, plus the organizer team-management views (builders, counts, members)
teams:write	Create/edit/delete teams, add/remove members, transfer leadership, move teams between tracks
submissions:read	List and read project submissions
judging:read	Read judges, criteria, assignments, scores, results, CSV exports
judging:write	Manage criteria, assign judges to teams (single + bulk), trigger results calculation
checkin:write	Scan participants at check-in points

What’s intentionally excluded

Paid actions (Stripe checkout, going live, post-live track/event creation) are deliberately excluded from *:write scopes - they require a browser.

• Creating super events or tracks is not available via the API.
• Score submission is a judge-side action - there is no scores:write scope. judging:write covers organizer setup (criteria, assignments, results), not casting scores. If you need to bulk-import scores, contact the BuilderBase team and a dedicated scores:write scope can be added.
• There is no submissions:write scope.