Skip to main content
POST
Upload new virtual GPU image

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

Example:

1

region_id
integer
required

Region ID

Example:

7

Body

application/json
name
string
required

Image name

Pattern: ^[a-zA-Z0-9][a-zA-Z 0-9._\-]{1,61}[a-zA-Z0-9._]$
Example:

"ubuntu-23.10-x64"

url
required

Image URL

Minimum string length: 1
Example:

"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
Example:

"x86_64"

cow_format
boolean
default:false

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

Example:

true

hw_firmware_type
enum<string> | null

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

Available options:
bios,
uefi
Example:

"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
Example:

"linux"

os_version
string | null

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

Example:

"19.04"

ssh_key
enum<string>
default:allow

Permission to use a ssh key in instances

Available options:
allow,
deny,
required
Example:

"allow"

tags
CreateTagsSerializer · 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. Both tag keys and values have a maximum length of 255 characters. 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.

Example:

Response

200 - application/json

OK

tasks
string[]
required

List of task IDs representing asynchronous operations. Use these IDs to monitor operation progress:

  • GET /v1/tasks/{task_id} - Check individual task status and details Poll task status until completion (FINISHED/ERROR) before proceeding with dependent operations.
Example: