Skip to main content
GET
List SSH keys

Authorizations

Authorization
string
header
required

Your API key, sent as a bearer token. Create one in the control panel under API Keys, give it only the permissions the integration needs, and copy it when it is created. It cannot be shown again. Each key is restricted to one owned team. The key determines the team for every request.

Response

The whole set, as a JSON array. There is no envelope and no paging.

id
string
required

The uuid. A key's autoincrement id never leaves the server.

Example:

"97721fd4-746a-40cc-8da0-4c9f623c112e"

name
string
required

The name shown to customers.

Example:

"gordon-workstation"

public_key
string
required

The SSH public key in OpenSSH format.

Example:

"ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPDNr9XsCkWrb0LklstkNHufnF8gAVKsPIFsZeFdoZEO gordon@bmrf-workstation"

fingerprint
string | null
required

The value of fingerprint.

Example:

"SHA256:0wwKzu+9eBzR6xq9nUxZ18417RQ5GKXSzi7ScY39ing"

algorithm
string | null
required

The algorithm as OpenSSH names it, read off the key material rather than stored beside it, so it cannot disagree with the key it labels.

Example:

"ssh-ed25519"

is_default
boolean
required

Ticked for the customer when a reinstall form opens; several keys can carry it, since a rebuild installs any number of them.

Example:

true

owner
AccountOwnerData · object | null
required

The key owner, when requested for a specific server.

Example:
belongs_to_server_owner
boolean
required

Which account's key this is, as a flag the reinstall form can act on: only the server owner's keys open ticked, never an administrator's own on somebody else's rebuild.

Example:

true

created_at
string | null
required

The date and time for created at, in UTC.

Example:

"2025-11-18T21:31:02+00:00"

Example: