Admin
Challenge management, uploads, teams, verifications, submissions, settings, and admin bot service routes.
These admin API pages cover challenges, uploads, teams, email verification, submission logs, runtime settings, admin bot work, and external auth clients. The admin challenge solves and instance routes are copies of the player-facing routes that skip challenge visibility, CTF start, captcha, and ban checks, so the admin panel can work with hidden or unreleased challenges. Most user-facing routes require a user auth token with the listed permission bits. Admin bot service routes use the shared admin bot bearer token. See External auth for the user-facing half of the external auth flow.
Permissions, captcha actions, and rate limit conventions are documented in the API overview.
Permissions
| Permission | Used by |
|---|---|
challsRead |
Reading admin challenge data, challenge solves, upload state, instancer schemas, admin bot status, admin user solve history, and managing the admin’s own instances. |
challsWrite |
Updating challenges and uploading files. |
challsSolveWrite |
Removing solves. |
usersWrite |
Listing and editing teams, creating team tokens, managing pending verifications, and reading submission audit rows. |
settingsWrite |
Reading and updating runtime settings. |
When a route lists more than one permission bit, the token needs every listed bit.