Skip to main content
POST
Push SSH keys to a machine
CLI equivalent: ornn ssh-keys assignments sync <reservation-id> pushes the assigned keys to every machine in the reservation.

Authorizations

Authorization
string
header
required

Create an organization API key in Account Settings > Developer. Do not send this key to the Kubernetes API server.

Path Parameters

node_id
string<uuid>
required

The host node ID (a Bare Metal node_id, or a VM's node_id) on a reservation your organization holds. A VM's own id returns 404 node_not_found.

Body

application/json
ssh_key_ids
string<uuid>[]
required

Active organization keys to assign to the machine's reservation before delivery.

Minimum array length: 1
request_id
string

Optional delivery ID for your own correlation. Omit it to let Ornn generate one. If you send it, use a new value for every push; reusing a value for the same machine returns the earlier delivery instead of queuing the current key set.

Response

Key delivery is queued for the machine.

id
string<uuid>
required

The machine ID from the request path.

node_id
string<uuid>
required

The physical node that hosts the machine.

reservation_id
string<uuid>
required
packet_ids
string<uuid>[]
required

One queued delivery ID per updated VM or host.

ssh_key_ids
string<uuid>[]
required

The reservation's full key set that was queued.

packet_id
string<uuid> | null

The first queued delivery ID, or null when nothing was queued.