Skip to main content
POST
/
storage
/
provisioning
/
v3
/
ssh_keys
Create SSH key
curl --request POST \
  --url https://api.gcore.com/storage/provisioning/v3/ssh_keys \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "my-production-key",
  "public_key": "ssh-rsa AAAAB3NzaC1yc2EAAA... user@example.com"
}
'
{
  "created_at": "2025-08-05 09:15:00+00:00",
  "id": 123,
  "name": "my-production-key",
  "public_key": "ssh-rsa AAAAB3NzaC1yc2EAAA... user@example.com"
}

Authorizations

​
Authorization
string
header
required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Body

application/json
​
name
string
required

User-defined name for the SSH key

Example:

"my-production-key"

​
public_key
string
required

The SSH public key content (ssh-rsa or ssh-ed25519 format)

Example:

"ssh-rsa AAAAB3NzaC1yc2EAAA... user@example.com"

Response

SSHKeyV3

SSHKeyV3 is the V3 response DTO for SSH keys with renamed fields

​
created_at
string
required

ISO 8601 timestamp when the SSH key was created

Example:

"2025-08-05 09:15:00+00:00"

​
id
integer<int64>
required

Unique identifier for the SSH key

Example:

123

​
name
string
required

User-defined name for the SSH key

Example:

"my-production-key"

​
public_key
string
required

The SSH public key content

Example:

"ssh-rsa AAAAB3NzaC1yc2EAAA... user@example.com"