Linode Types

Types List

get
https://api.linode.com/v4/linode/types

Returns collection of Linode Types, including pricing and specifications for each Type. These are used when creating or resizing Linodes.

Request Samples

curl https://api.linode.com/v4/linode/types

Response Samples

{
  "data": [
    {
      "id": "",
      "label": "Linode 4GB",
      "transfer": 4000,
      "disk": 81920,
      "class": "standard",
      "price": {
        "hourly": 0.03,
        "monthly": 20
      },
      "addons": {
        "backups": ""
      },
      "network_out": 1000,
      "memory": 4096,
      "successor": "",
      "vcpus": 2,
      "gpus": ""
    }
  ],
  "page": 1,
  "pages": 1,
  "results": 1
}

Responses

200: A collection of Linode Types.

data
array of objects
id
string

The ID representing the Linode Type.

label
Filterable
string

The Linode Type's label is for display purposes only.

transfer
Filterable
integer

The monthly outbound transfer amount, in MB.

disk
Filterable
integer

The Disk size, in MB, of the Linode Type.

class
Filterable
string
Enum: "nanode""standard""dedicated""premium""gpu""highmem"

The class of the Linode Type.

We currently offer six classes of compute instances:

  • 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.
  • premium (limited Regions) - In addition to the features of Dedicated instances, Premium instances come equipped with the latest AMD EPYC CPUs, ensuring your applications are running on the latest hardware with consistently high performance. Only available in Regions with "Premium Plans" in their capabilities
  • gpu (limited Regions) - Linodes with dedicated NVIDIA Quadro® RTX 6000 GPUs accelerate highly specialized applications such as machine learning, AI, and video transcoding. Only available in Regions with "GPU Linodes" in their capabilities
  • 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.
price
object

Cost in US dollars, broken down into hourly and monthly charges.

hourly
number

Cost (in US dollars) per hour.

monthly
number

Cost (in US dollars) per month.

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.

network_out
Filterable
integer

The Mbits outbound bandwidth allocation.

memory
Filterable
integer

Amount of RAM included in this Linode Type.

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.

vcpus
Filterable
integer

The number of VCPU cores this Linode Type offers.

gpus
Filterable
integer

The number of GPUs this Linode Type offers.

page
integer

The current page.

pages
integer

The total number of pages.

results
integer

The total number of results.

default: Error

errors
array of objects
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.

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.