PUT · FTP & SSH access
Hold an SSH-access change for confirmation
Hold an SSH-access change for confirmation
/api/v1/hosting/ssh
Description
Returns {status:"confirmation_required", confirmationUrl, …} — it changes nothing on this call. enabled=true turns shell access on, false off. Show the human the confirmationUrl; do not approve it yourself. To manage the account's SSH keys use manage_ssh_keys.
Body
Send as application/json.
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response.
|
enabled
required
|
boolean |
true to enable SSH (shell) access for the account, false to disable it.
|
attempt_key
|
string | Idempotency key for this intent. Keep it stable across retries so a timed-out retry cannot buy the same thing twice. Up to 128 characters. |
Responses
A 200 response returns the shape shown in the rail.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.