POST
/
cloud
/
v3
/
gpu
/
virtual
/
{project_id}
/
{region_id}
/
images
Upload new virtual GPU image
curl --request POST \
  --url https://api.gcore.com/cloud/v3/gpu/virtual/{project_id}/{region_id}/images \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "architecture": "x86_64",
  "cow_format": true,
  "hw_firmware_type": "bios",
  "name": "ubuntu-23.10-x64",
  "os_distro": "<string>",
  "os_type": "linux",
  "os_version": "19.04",
  "ssh_key": "allow",
  "tags": {
    "my-tag": "my-tag-value"
  },
  "url": "http://mirror.noris.net/cirros/0.4.0/cirros-0.4.0-x86_64-disk.img"
}'
{
  "tasks": [
    "d478ae29-dedc-4869-82f0-96104425f565"
  ]
}

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

Path Parameters

​
project_id
integer
required

Project ID

Examples:

1

​
region_id
integer
required

Region ID

Examples:

7

Body

application/json
​
name
string
required

Image name

Examples:

"ubuntu-23.10-x64"

​
url
required

Image URL

Minimum length: 1
Examples:

"http://mirror.noris.net/cirros/0.4.0/cirros-0.4.0-x86_64-disk.img"

​
architecture
enum<string> | null
default:x86_64

Image architecture type: aarch64, x86_64

Available options:
aarch64,
x86_64
Examples:

"x86_64"

​
cow_format
boolean
default:false

When True, image cannot be deleted unless all volumes, created from it, are deleted.

Examples:

true

​
hw_firmware_type
enum<string> | null

Specifies the type of firmware with which to boot the guest.

Available options:
bios,
uefi
Examples:

"bios"

​
os_distro
string | null

OS Distribution, i.e. Debian, CentOS, Ubuntu, CoreOS etc.

​
os_type
enum<string> | null
default:linux

The operating system installed on the image. Linux by default

Available options:
linux,
windows
Examples:

"linux"

​
os_version
string | null

OS version, i.e. 19.04 (for Ubuntu) or 9.4 for Debian

Examples:

"19.04"

​
ssh_key
enum<string>

Permission to use a ssh key in instances

Available options:
allow,
deny,
required
​
tags
object

Key-value tags to associate with the resource. A tag is a key-value pair that can be associated with a resource, enabling efficient filtering and grouping for better organization and management. Some tags are read-only and cannot be modified by the user. Tags are also integrated with cost reports, allowing cost data to be filtered based on tag keys or values.

Response

200 - application/json

OK

​
tasks
string[]
required

List of task IDs

Examples:
["d478ae29-dedc-4869-82f0-96104425f565"]