POST · FTP & SSH access
List, add or remove SSH public keys
List, add or remove SSH public keys
/api/v1/hosting/ssh-keys
Description
action=list returns each authorized key {fingerprint, type, comment, bits} and needs only read access. create (alias authorize) adds a public_key — a single OpenSSH public-key line — and returns its fingerprint; delete removes one by fingerprint. Writes require write:hosting. To enable or disable SSH for the whole account use set_ssh_access.
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.
|
action
required
|
enum |
list the authorized keys, create (add) one, or delete one. Writes require write:hosting. One of list, create, delete.
|
public_key
|
string |
The OpenSSH public key line to add, e.g. ssh-ed25519 AAAAC3Nza… laptop.
|
fingerprint
|
string |
Up to 64 characters. Pattern ^SHA256:[A-Za-z0-9+\/=]{40,48}$.
|
Responses
The specification does not describe this response body; the note in the rail says what to expect.
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.