Endpoints
- GETCount virtual machines in a project
- PATCHAttach a disk to a virtual machine
- PUTDetach a disk from a virtual machine
- POSTCreate a virtual machine
- POSTUpdate virtual machine authorized SSH keys
- POSTPurchase a commitment for a virtual machine
- POSTUpdate virtual machine expiration time
- POSTUpdate virtual machine metadata
- POSTUpdate virtual machine password
- PATCHAttach a security group to a virtual machine
- PATCHDetach a security group from a virtual machine
- GETList virtual machines
- GETGet a virtual machine
- GETConnect to a virtual machine
- GETMonitor a virtual machine
- POSTReboot a virtual machine
- POSTResize a virtual machine
- POSTStart a virtual machine
- POSTStop a virtual machine
- POSTDelete a virtual machine
- GETList virtual machine data centers
- GETGet a virtual machine type
- GETList virtual machine GPU models
- GETList virtual machine types
- GETLists virtual machine types (deprecated)deprecated
- GET
Changelog
curl --request GET \
--url https://rest.compute.cudo.org/v1/vms/data-centers/{dataCenterId}/machine_types/{machineTypeId} \
--header 'Authorization: <api-key>'{
"cpuModel": "<string>",
"dataCenterId": "<string>",
"gpuModel": "<string>",
"gpuModelId": "<string>",
"gpuPriceHr": {
"value": "<string>"
},
"ipv4PriceHr": {
"value": "<string>"
},
"machineType": "<string>",
"maxGpuFree": 123,
"maxMemoryGibFree": 123,
"maxStorageGibFree": 123,
"maxVcpuFree": 123,
"maxVcpuPerGpu": 123,
"maxVcpuPerMemoryGib": 123,
"memoryGibPriceHr": {
"value": "<string>"
},
"minMemoryGib": 123,
"minStorageGibPriceHr": {
"value": "<string>"
},
"minVcpu": 123,
"minVcpuPerGpu": 123,
"minVcpuPerMemoryGib": 123,
"prices": [
{
"commitmentTerm": "COMMITMENT_TERM_NONE",
"gpuPriceHr": {
"value": "<string>"
},
"memoryGibPriceHr": {
"value": "<string>"
},
"vcpuPriceHr": {
"value": "<string>"
}
}
],
"renewableEnergy": true,
"totalGpuFree": 123,
"totalMemoryGibFree": 123,
"totalStorageGibFree": 123,
"totalVcpuFree": 123,
"vcpuPriceHr": {
"value": "<string>"
}
}Get a virtual machine type
Retrieves the details of a virtual machine type.
curl --request GET \
--url https://rest.compute.cudo.org/v1/vms/data-centers/{dataCenterId}/machine_types/{machineTypeId} \
--header 'Authorization: <api-key>'{
"cpuModel": "<string>",
"dataCenterId": "<string>",
"gpuModel": "<string>",
"gpuModelId": "<string>",
"gpuPriceHr": {
"value": "<string>"
},
"ipv4PriceHr": {
"value": "<string>"
},
"machineType": "<string>",
"maxGpuFree": 123,
"maxMemoryGibFree": 123,
"maxStorageGibFree": 123,
"maxVcpuFree": 123,
"maxVcpuPerGpu": 123,
"maxVcpuPerMemoryGib": 123,
"memoryGibPriceHr": {
"value": "<string>"
},
"minMemoryGib": 123,
"minStorageGibPriceHr": {
"value": "<string>"
},
"minVcpu": 123,
"minVcpuPerGpu": 123,
"minVcpuPerMemoryGib": 123,
"prices": [
{
"commitmentTerm": "COMMITMENT_TERM_NONE",
"gpuPriceHr": {
"value": "<string>"
},
"memoryGibPriceHr": {
"value": "<string>"
},
"vcpuPriceHr": {
"value": "<string>"
}
}
],
"renewableEnergy": true,
"totalGpuFree": 123,
"totalMemoryGibFree": 123,
"totalStorageGibFree": 123,
"totalVcpuFree": 123,
"vcpuPriceHr": {
"value": "<string>"
}
}Authorizations
Bearer HTTP authentication. Allowed headers-- Authorization: Bearer <api_key>
Query Parameters
Return custom prices for a specific project.
Response
A successful response.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
Show child attributes
Show child attributes
COMMITMENT_TERM_NONE, COMMITMENT_TERM_1_MONTH, COMMITMENT_TERM_3_MONTHS, COMMITMENT_TERM_6_MONTHS, COMMITMENT_TERM_12_MONTHS, COMMITMENT_TERM_24_MONTHS, COMMITMENT_TERM_36_MONTHS, COMMITMENT_TERM_60_MONTHS A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.
A representation of a decimal value, such as 2.5. Clients may convert values into language-native decimal formats, such as Java's BigDecimal or Python's decimal.Decimal.
Show child attributes
Show child attributes
The decimal value, as a string.
The string representation consists of an optional sign, + (U+002B)
or - (U+002D), followed by a sequence of zero or more decimal digits
("the integer"), optionally followed by a fraction, optionally followed
by an exponent.
The fraction consists of a decimal point followed by zero or more decimal digits. The string must contain at least one digit in either the integer or the fraction. The number formed by the sign, the integer and the fraction is referred to as the significand.
The exponent consists of the character e (U+0065) or E (U+0045)
followed by one or more decimal digits.
Services should normalize decimal values before storing them by:
- Removing an explicitly-provided
+sign (+2.5->2.5). - Replacing a zero-length integer value with
0(.5->0.5). - Coercing the exponent character to lower-case (
2.5E8->2.5e8). - Removing an explicitly-provided zero exponent (
2.5e0->2.5).
Services may perform additional normalization based on its own needs
and the internal decimal implementation selected, such as shifting the
decimal point and exponent value together (example: 2.5e-1 <-> 0.25).
Additionally, services may preserve trailing zeroes in the fraction
to indicate increased precision, but are not required to do so.
Note that only the . character is supported to divide the integer
and the fraction; , should not be supported regardless of locale.
Additionally, thousand separators should not be supported. If a
service does support them, values must be normalized.
The ENBF grammar is:
DecimalString =
[Sign] Significand [Exponent];
Sign = '+' | '-';
Significand =
Digits ['.'] [Digits] | [Digits] '.' Digits;
Exponent = ('e' | 'E') [Sign] Digits;
Digits = { '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9' };Services should clearly document the range of supported values, the maximum supported precision (total number of digits), and, if applicable, the scale (number of digits after the decimal point), as well as how it behaves when receiving out-of-bounds values.
Services may choose to accept values passed as input even when the
value has a higher precision or scale than the service supports, and
should round the value to fit the supported scale. Alternatively, the
service may error with 400 Bad Request (INVALID_ARGUMENT in gRPC)
if precision would be lost.
Services should error with 400 Bad Request (INVALID_ARGUMENT in
gRPC) if the service receives a value outside of the supported range.