Add SSH key to instance

curl --request POST \
  --url https://api.thundercompute.com:8443/v1/instances/{id}/add_key \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{}'

{
  "success": true,
  "uuid": "<string>",
  "key": "<string>",
  "message": "<string>"
}

Instances

Add SSH key to instance

Append an SSH public key to an existing instance’s authorized_keys.

Behavior:

If public_key is provided, that raw key material is appended to authorized_keys. If the same public key is already attached, the request is a no-op (no error).
If public_key is omitted, Thunder generates a new key pair, appends the public half to authorized_keys, and returns the private key in the response. The private key is only returned once — store it immediately.

Note: SSH keys saved in your account (Authentication section of the console) are a separate store and are NOT automatically attached to instances. To use one of those keys, copy its public key material into the public_key field on this request.

POST

instances

{id}

add_key

Add SSH key to instance

curl --request POST \
  --url https://api.thundercompute.com:8443/v1/instances/{id}/add_key \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{}'

{
  "success": true,
  "uuid": "<string>",
  "key": "<string>",
  "message": "<string>"
}

Authorizations

Authorization

string

header

required

Bearer token authentication. Provide your API token prefixed with "Bearer ", e.g. "Bearer your-api-token".

Path Parameters

string

required

Instance ID

Body

application/json

Optional: provide an existing public key to add

Option 1
Option 2

The body is of type object.

Response

success

boolean

required

Whether the key was successfully added

uuid

string

required

key

string

Private key (only when generated)

message

string

Status message

List instances

Delete instance

Documentation Index

Authorizations

Path Parameters

Body

Response