Authentication
WarmHub HTTP endpoints authenticate requests with a Bearer token in the Authorization header:
curl -H "Authorization: Bearer <token>" \ https://api.warmhub.ai/api/repos/myorg/myrepo/headWarmHub accepts interactive session JWTs, personal access tokens (PATs), and component-issued tokens — some of which can authenticate the mounted routes they were created for — subject to the user’s organization and repository role.
Personal Access Tokens
Section titled “Personal Access Tokens”PAT management REST endpoints such as POST /api/pats, GET /api/pats, and DELETE /api/pats/:name are not currently mounted.
Create and manage PATs with the CLI (wh token), the SDK (client.token.*), or the Settings page in the web UI (/settings). The Settings page uses your interactive sign-in and manages all your tokens. The CLI and SDK accept either an interactive user session — which also manages all your tokens — or a PAT, which manages only the tokens it created (and tokens those created in turn). See Personal Access Tokens for the full guide.
Scopes
Section titled “Scopes”PATs can carry resource-scoped permissions: repo:read, repo:checkpoint-read, repo:checkpoint-generate, repo:write, repo:configure, repo:admin, repo:action-callback, org:read, org:configure, org:admin, and org:action-callback. Scopes are independent — request the specific permissions your token needs. For what each scope grants, which role includes it, and the minimum scope per task, see the access reference. JWT tokens do not use PAT scope narrowing, but are still limited by the user’s role.