Appearance
Auth
Token lifecycle for automation, plus a way to identify the current caller.
Session-only flows are excluded
Endpoints used by the operator portal — /auth/login, /auth/signup, /auth/forgot-password, etc. — are intentionally not part of the public API. They depend on cookies and are not designed for programmatic use.
Identify the current caller
List the caller's API tokens
Mint a new API token
POST
/api/auth/tokens
Session-only — minting a bearer token from a bearer token would let a leaked token self-propagate. The plaintext is in the response once; store it immediately.
Authorizations
bearer
Type
HTTP (bearer)
Request Body
application/json
{
"name": "string",
"scope": {
},
"expiresAt": "string"
}
Responses
Revoke an API token
DELETE
/api/auth/tokens/{id}
Session callers can revoke any of their own tokens. Bearer callers can only revoke the token they are authenticating with — lets nuc auth logout clean up after itself without opening a "one token can retire another" hole.
Authorizations
bearer
Type
HTTP (bearer)
Parameters
Path Parameters
id*
Type
Requiredstring