Registry API
Service accounts
Non-human identities for CI and automation, and their API tokens.
A service account is owned by an organization and has explicit scopes. Issue API tokens for it, and revoke any token on its own.
Operations
| Request | What it does |
|---|---|
| POST /api/v1/admin/service-accounts | Create a service account |
| GET /api/v1/admin/service-accounts | List service accounts |
| DELETE /api/v1/admin/service-accounts/{id} | Delete a service account |
| POST /api/v1/admin/service-accounts/{id}/tokens | Issue a new token for a service account |
| DELETE /api/v1/admin/tokens/{id} | Revoke a token |
Paths and summaries come from apps/api/openapi.json, which CI regenerates from the route definitions; this site checks its list against that file. Only the Public operations work without a token; everything else needs a signed-in session or an API token.