Deny a CLI sign-in
Browser sessions only. The CLI's next redeem answers `cli-login-closed`.
openapi/harthelm.yaml at v1.5.0__Host-harthelm_session<token>Browser session of the UI (12 h idle, 7 days absolute). State-changing requests also need the header
Harthelm-CSRF: 1 and a matching Origin.
code*stringThe user code hart login printed, e.g. BDFH-KMNP (case and the dash do not matter).
8 <= length <= 9Denied.
curl -X POST 'https://console.example.com/api/v1/me/cli-logins/stringst/deny'Approve a CLI sign-in
Browser sessions only (403 with an API key): the user confirms in the console that the sign-in is theirs. The CLI then redeems it for a new API key of the approving user (`POST /cli/logins/{login}/token`). For a loopback sign-in the response names the CLI's local callback, which the console navigates to; it carries no secret.
A pending CLI sign-in, for the console's confirmation
What `hart login` asked for: the console's `/cli-login?code=<user code>` page shows it before the user approves. 404 when the code is unknown, expired, or already approved or denied.