{"errors":[{"field":"fieldname","reason":"fieldname must be a valid value"}]}
Responses
A collection of Linode Types.
data
array of objects
addons
object
A list of optional add-on services for Linodes and their associated costs.
backups
object
Information about the optional Backup service offered for Linodes.
price
object
Cost of enabling Backups for this Linode Type.
hourly
integer
The cost (in US dollars) per hour to add Backups service.
monthly
integer
The cost (in US dollars) per month to add Backups service.
class
Filterable
string
Enum:
nanodestandarddedicatedgpuhighmem
The class of the Linode Type. We currently offer five classes of Linodes:
nanode - Nanode instances are good for low-duty workloads,
where performance isn’t critical. Note: As of June 16th, 2020, Nanodes became
1 GB Linodes in the Cloud Manager, however, the API, the CLI, and billing will
continue to refer to these instances as Nanodes.
standard - Standard Shared instances are good for medium-duty workloads and
are a good mix of performance, resources, and price. Note: As of June 16th, 2020,
Standard Linodes in the Cloud Manager became Shared Linodes, however, the API, the CLI, and
billing will continue to refer to these instances as Standard Linodes.
dedicated - Dedicated CPU instances are good for full-duty workloads
where consistent performance is important.
gpu - Linodes with dedicated NVIDIA Quadro ® RTX 6000 GPUs accelerate highly
specialized applications such as machine learning, AI, and video transcoding.
highmem - High Memory instances favor RAM over other resources, and can be
good for memory hungry use cases like caching and in-memory databases.
All High Memory plans contain dedicated CPU cores.
disk
Filterable
integer
The Disk size, in MB, of the Linode Type.
gpus
Filterable
integer
The number of GPUs this Linode Type offers.
id
string
The ID representing the Linode Type.
label
Filterable
string
The Linode Type’s label is for display purposes only.
memory
Filterable
integer
Amount of RAM included in this Linode Type.
network_out
Filterable
integer
The Mbits outbound bandwidth allocation.
price
object
Cost in US dollars, broken down into hourly and monthly charges.
hourly
integer
Cost (in US dollars) per hour.
monthly
integer
Cost (in US dollars) per month.
successor
Nullable
string
The Linode Type that a
mutate will upgrade to for a Linode of this type. If “null”, a Linode of this type may not mutate.
transfer
Filterable
integer
The monthly outbound transfer amount, in MB.
vcpus
Filterable
integer
The number of VCPU cores this Linode Type offers.
page
integer
pages
integer
results
integer
Error
errors
array of objects
field
string
The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as “null” if the error is not specific to any single element of the request.
reason
string
What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to
open a Support Ticket or perform some other action before you can complete the request successfully.
Type View
GET
https://api.linode.com/v4/linode/types/{typeId}
Returns information about a specific Linode Type, including pricing and specifications. This is used when
creating or
resizing Linodes.
{"errors":[{"field":"fieldname","reason":"fieldname must be a valid value"}]}
Responses
A single Linode Type.
addons
object
A list of optional add-on services for Linodes and their associated costs.
backups
object
Information about the optional Backup service offered for Linodes.
price
object
Cost of enabling Backups for this Linode Type.
hourly
integer
The cost (in US dollars) per hour to add Backups service.
monthly
integer
The cost (in US dollars) per month to add Backups service.
class
Filterable
string
Enum:
nanodestandarddedicatedgpuhighmem
The class of the Linode Type. We currently offer five classes of Linodes:
nanode - Nanode instances are good for low-duty workloads,
where performance isn’t critical. Note: As of June 16th, 2020, Nanodes became
1 GB Linodes in the Cloud Manager, however, the API, the CLI, and billing will
continue to refer to these instances as Nanodes.
standard - Standard Shared instances are good for medium-duty workloads and
are a good mix of performance, resources, and price. Note: As of June 16th, 2020,
Standard Linodes in the Cloud Manager became Shared Linodes, however, the API, the CLI, and
billing will continue to refer to these instances as Standard Linodes.
dedicated - Dedicated CPU instances are good for full-duty workloads
where consistent performance is important.
gpu - Linodes with dedicated NVIDIA Quadro ® RTX 6000 GPUs accelerate highly
specialized applications such as machine learning, AI, and video transcoding.
highmem - High Memory instances favor RAM over other resources, and can be
good for memory hungry use cases like caching and in-memory databases.
All High Memory plans contain dedicated CPU cores.
disk
Filterable
integer
The Disk size, in MB, of the Linode Type.
gpus
Filterable
integer
The number of GPUs this Linode Type offers.
id
string
The ID representing the Linode Type.
label
Filterable
string
The Linode Type’s label is for display purposes only.
memory
Filterable
integer
Amount of RAM included in this Linode Type.
network_out
Filterable
integer
The Mbits outbound bandwidth allocation.
price
object
Cost in US dollars, broken down into hourly and monthly charges.
hourly
integer
Cost (in US dollars) per hour.
monthly
integer
Cost (in US dollars) per month.
successor
Nullable
string
The Linode Type that a
mutate will upgrade to for a Linode of this type. If “null”, a Linode of this type may not mutate.
transfer
Filterable
integer
The monthly outbound transfer amount, in MB.
vcpus
Filterable
integer
The number of VCPU cores this Linode Type offers.
Error
errors
array of objects
field
string
The field in the request that caused this error. This may be a path, separated by periods in the case of nested fields. In some cases this may come back as “null” if the error is not specific to any single element of the request.
reason
string
What happened to cause this error. In most cases, this can be fixed immediately by changing the data you sent in the request, but in some cases you will be instructed to
open a Support Ticket or perform some other action before you can complete the request successfully.