Replace registered SSH public keys
Replaces the account’s full set of registered SSH public keys. Existing keys not present in the request are removed; send [] to remove all keys. Keys take effect for pods created afterwards with startSsh — running pods are not updated.
Authorizations
Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.
Body
The full set of SSH public keys to register — this is a complete
replacement, not a merge. Each entry is an authorized_keys-style
line: <type> <base64-key> [comment], e.g. from
~/.ssh/id_ed25519.pub. Send [] to remove all keys. These keys
are provisioned into pods created with startSsh and
authenticate both SSH paths reported in the pod's ssh block.
^(ssh|ecdsa|sk)-[^\s]+ [^\s]+([ \t][^\n\r]*)?$Response
OK — the updated key set
The account's registered SSH public keys, one authorized_keys-style entry per element (<type> <base64-key> [comment]).