openapi: 3.2.0 info: contact: email: support@linode.com name: Linode url: https://linode.com description: Add a Cloud Computing instance so you can build, release, and scale applications faster with virtual machines. license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html title: 'Akamai: Linode VPC subnets API' version: 4.215.0 servers: - url: https://api.linode.com tags: - name: VPC subnets paths: /{apiVersion}/vpcs/{vpcId}/subnets: parameters: - description: __Enum__ Call either the `v4` URL, or `v4beta` for operations still in Beta. example: '{{apiVersion}}' in: path name: apiVersion required: true schema: enum: - v4 - v4beta type: string x-akamai: file-path: parameters/api-version-path.yaml - description: The `id` of the VPC. example: '{{vpcId}}' in: path name: vpcId required: true schema: example: 527 type: integer x-akamai: file-path: parameters/vpc-id.yaml x-akamai: file-path: paths/subnets.yaml path-info: /{apiVersion}/vpcs/{vpcId}/subnets x-linode-cli-command: vpcs post: description: 'Create a VPC Subnet. - The User accessing this operation must have `read_write` grants to the VPC. - A successful request triggers a `subnet_create` event. Once a VPC Subnet is created, it can be attached to a Linode by assigning the Subnet to one of the Linode''s Configuration Profile Interfaces. This step can be accomplished with the following operations: - Create a Linode - Create a config profile - Update a config profile - Add a configuration profile interface > --- - __CLI__. ``` linode-cli vpcs subnet-create $vpcId \ --label cool-vpc-subnet \ --ipv4 10.0.1.0/24 ``` Learn more... - __OAuth scopes__. ``` vpc:read_write ``` Learn more...' externalDocs: description: See documentation for this operation in Akamai's Linode API url: https://techdocs.akamai.com/linode-api/reference/post-vpc-subnet operationId: post-vpc-subnet requestBody: content: application/json: schema: additionalProperties: false description: VPC Subnet Create request object. properties: ipv4: description: 'IPv4 range in CIDR canonical form. - The range must belong to a private address space as defined in [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918). - Allowed prefix lengths: 1-29. - The range must not overlap with 192.168.128.0/17. - The range must not overlap with other Subnets on the same VPC.' example: '{{ipv4}}' format: ip type: string x-linode-cli-display: 3 label: description: '__Filterable__ The VPC Subnet''s label, for display purposes only. - Must be unique among the VPC''s Subnets. - Can only contain ASCII letters, numbers, and hyphens (`-`). You can''t use two consecutive hyphens (`--`).' example: '{{label}}' maxLength: 64 minLength: 1 type: string x-akamai: labels: - Filterable x-linode-cli-display: 2 x-linode-filterable: true required: - ipv4 - label type: object x-akamai: file-path: schemas/added-post-vpc-subnet.yaml x-example: x-ref: ../examples/post-vpc-subnet.json description: VPC Subnet Create request object. required: true responses: '200': content: application/json: schema: additionalProperties: false description: An object describing a VPC Subnet. properties: created: description: __Filterable__, __Read-only__ The date-time of VPC Subnet creation. example: '2023-07-11T00:00:00' format: date-time readOnly: true type: string x-akamai: labels: - Filterable x-linode-filterable: true id: description: __Filterable__, __Read-only__ The unique ID of the VPC Subnet. example: 456 readOnly: true type: integer x-akamai: labels: - Filterable x-linode-cli-display: 1 x-linode-filterable: true ipv4: description: 'IPv4 range in CIDR canonical form. - The range must belong to a private address space as defined in [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918). - Allowed prefix lengths: 1-29. - The range must not overlap with 192.168.128.0/17. - The range must not overlap with other Subnets on the same VPC.' example: 10.0.1.0/24 format: ip type: string x-linode-cli-display: 3 label: description: '__Filterable__ The VPC Subnet''s label, for display purposes only. - Must be unique among the VPC''s Subnets. - Can only contain ASCII letters, numbers, and hyphens (`-`). You can''t use two consecutive hyphens (`--`).' example: cool-vpc-subnet maxLength: 64 minLength: 1 type: string x-akamai: labels: - Filterable x-linode-cli-display: 2 x-linode-filterable: true linodes: description: '__Read-only__ An array of Linode IDs assigned to the VPC Subnet. A Linode is assigned to a VPC Subnet if it has a Configuration Profile with a `vpc` purpose interface with the subnet''s `subnet_id`. Even if the Configuration Profile is not active, meaning the Linode does not have access to the Subnet, the Linode still appears in this array.' items: additionalProperties: false properties: id: description: ID of a Linode assigned to the VPC Subnet. example: 111 type: integer interfaces: description: VPC purpose interfaces with the subnet's `subnet_id` assigned to the Linode. items: additionalProperties: false properties: active: description: Returns `true` if the Interface is in use, meaning that the Linode was powered on using the Configuration Profile to which the Interface belongs. Otherwise returns `false`. example: true type: boolean config_id: description: The globally general entity identifier for the Linode configuration profile that includes the VPC. If this is a VPC Linode interface, the value is `null`. example: 4567 type: - integer - 'null' id: description: ID of the interface. example: 421 type: integer type: object type: array type: object readOnly: true type: array x-linode-cli-display: 5 updated: description: __Filterable__, __Read-only__ The date-time of the most recent VPC Subnet update. example: '2023-09-11T00:00:00' format: date-time readOnly: true type: - string - 'null' x-akamai: labels: - Filterable x-linode-filterable: true type: object x-akamai: file-path: schemas/vpc-subnet.yaml x-example: x-ref: ../examples/post-vpc-subnet-200.json description: The new VPC Subnet. default: content: application/json: schema: additionalProperties: false properties: errors: items: additionalProperties: false description: An object for describing a single error that occurred during the processing of a request. properties: field: description: 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. example: fieldname type: string reason: description: 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](https://techdocs.akamai.com/linode-api/reference/post-ticket) or perform some other action before you can complete the request successfully. example: fieldname must be a valid value type: string type: object x-akamai: file-path: schemas/error-object.yaml type: array type: object description: See [Errors](https://techdocs.akamai.com/linode-api/reference/errors) for the range of possible error response codes. security: - personalAccessToken: [] - oauth: - vpc:read_write summary: Create a VPC subnet tags: - VPC subnets x-akamai: tabs: - syntax: "linode-cli vpcs subnet-create $vpcId \\\n --label cool-vpc-subnet \\\n --ipv4 10.0.1.0/24" title: CLI url: https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli - syntax: vpc:read_write title: OAuth scopes url: https://techdocs.akamai.com/linode-api/reference/get-started#oauth x-linode-cli-action: subnet-create x-linode-grant: read_write get: description: 'Get information about all VPC Subnets associated with a VPC. > --- - __CLI__. ``` linode-cli vpcs subnets-list $vpcId ``` Learn more...' externalDocs: description: See documentation for this operation in Akamai's Linode API url: https://techdocs.akamai.com/linode-api/reference/get-vpc-subnets operationId: get-vpc-subnets parameters: - description: The page of a collection to return. example: '{{page}}' in: query name: page required: false schema: default: 1 example: 6 minimum: 1 type: integer x-akamai: file-path: parameters/page-offset.yaml - description: The number of items to return per page. example: '{{page_size}}' in: query name: page_size schema: default: 100 example: 50 maximum: 500 minimum: 25 type: integer x-akamai: file-path: parameters/page-size.yaml responses: '200': content: application/json: example: data: - created: '2023-07-11T00:00:00' id: 456 ipv4: 10.1.0.0/24 label: cool-vpc-subnet linodes: - id: 111 interfaces: - active: true config_id: null id: 421 updated: '2023-09-11T00:00:00' page: 1 pages: 1 results: 1 schema: allOf: - additionalProperties: false description: An envelope for paginated response. When accessing a collection through a GET endpoint, the results are wrapped in this envelope which includes metadata about those results. Results are presented within a `data` array. See [Pagination](https://techdocs.akamai.com/linode-api/reference/pagination) for more information. properties: page: description: __Read-only__ The current [page](https://techdocs.akamai.com/linode-api/reference/pagination). example: 1 readOnly: true type: integer pages: description: __Read-only__ The total number of [pages](https://techdocs.akamai.com/linode-api/reference/pagination). example: 1 readOnly: true type: integer results: description: __Read-only__ The total number of results. example: 1 readOnly: true type: integer type: object x-akamai: file-path: schemas/pagination-envelope.yaml - properties: data: items: additionalProperties: false description: An object describing a VPC Subnet. properties: created: description: __Filterable__, __Read-only__ The date-time of VPC Subnet creation. example: '2023-07-11T00:00:00' format: date-time readOnly: true type: string x-akamai: labels: - Filterable x-linode-filterable: true id: description: __Filterable__, __Read-only__ The unique ID of the VPC Subnet. example: 456 readOnly: true type: integer x-akamai: labels: - Filterable x-linode-cli-display: 1 x-linode-filterable: true ipv4: description: 'IPv4 range in CIDR canonical form. - The range must belong to a private address space as defined in [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918). - Allowed prefix lengths: 1-29. - The range must not overlap with 192.168.128.0/17. - The range must not overlap with other Subnets on the same VPC.' example: 10.0.1.0/24 format: ip type: string x-linode-cli-display: 3 label: description: '__Filterable__ The VPC Subnet''s label, for display purposes only. - Must be unique among the VPC''s Subnets. - Can only contain ASCII letters, numbers, and hyphens (`-`). You can''t use two consecutive hyphens (`--`).' example: cool-vpc-subnet maxLength: 64 minLength: 1 type: string x-akamai: labels: - Filterable x-linode-cli-display: 2 x-linode-filterable: true linodes: description: '__Read-only__ An array of Linode IDs assigned to the VPC Subnet. A Linode is assigned to a VPC Subnet if it has a Configuration Profile with a `vpc` purpose interface with the subnet''s `subnet_id`. Even if the Configuration Profile is not active, meaning the Linode does not have access to the Subnet, the Linode still appears in this array.' items: additionalProperties: false properties: id: description: ID of a Linode assigned to the VPC Subnet. example: 111 type: integer interfaces: description: VPC purpose interfaces with the subnet's `subnet_id` assigned to the Linode. items: additionalProperties: false properties: active: description: Returns `true` if the Interface is in use, meaning that the Linode was powered on using the Configuration Profile to which the Interface belongs. Otherwise returns `false`. example: true type: boolean config_id: description: The globally general entity identifier for the Linode configuration profile that includes the VPC. If this is a VPC Linode interface, the value is `null`. example: 4567 type: - integer - 'null' id: description: ID of the interface. example: 421 type: integer type: object type: array type: object readOnly: true type: array x-linode-cli-display: 5 updated: description: __Filterable__, __Read-only__ The date-time of the most recent VPC Subnet update. example: '2023-09-11T00:00:00' format: date-time readOnly: true type: - string - 'null' x-akamai: labels: - Filterable x-linode-filterable: true type: object x-akamai: file-path: schemas/vpc-subnet.yaml type: array x-akamai: file-path: schemas/added-get-vpc-subnets-200.yaml description: A paginated list of VPC Subnet objects. default: content: application/json: schema: additionalProperties: false properties: errors: items: additionalProperties: false description: An object for describing a single error that occurred during the processing of a request. properties: field: description: 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. example: fieldname type: string reason: description: 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](https://techdocs.akamai.com/linode-api/reference/post-ticket) or perform some other action before you can complete the request successfully. example: fieldname must be a valid value type: string type: object x-akamai: file-path: schemas/error-object.yaml type: array type: object description: See [Errors](https://techdocs.akamai.com/linode-api/reference/errors) for the range of possible error response codes. security: - personalAccessToken: [] - oauth: [] summary: List VPC subnets tags: - VPC subnets x-akamai: tabs: - syntax: linode-cli vpcs subnets-list $vpcId title: CLI url: https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli x-linode-cli-action: - subnets-list - subnets-ls /{apiVersion}/vpcs/{vpcId}/subnets/{vpcSubnetId}: parameters: - description: __Enum__ Call either the `v4` URL, or `v4beta` for operations still in Beta. example: '{{apiVersion}}' in: path name: apiVersion required: true schema: enum: - v4 - v4beta type: string x-akamai: file-path: parameters/api-version-path.yaml - description: The `id` of the VPC. example: '{{vpcId}}' in: path name: vpcId required: true schema: example: 527 type: integer x-akamai: file-path: parameters/vpc-id.yaml - description: The `id` of the VPC Subnet. example: '{{vpcSubnetId}}' in: path name: vpcSubnetId required: true schema: example: 627 type: integer x-akamai: file-path: parameters/vpc-subnet-id.yaml x-akamai: file-path: paths/vpc-subnet.yaml path-info: /{apiVersion}/vpcs/{vpcId}/subnets/{vpcSubnetId} x-linode-cli-command: vpcs get: description: 'Get information about a single VPC Subnet. > --- - __CLI__. ``` linode-cli vpcs subnet-view $vpcId $vpcSubnetId ``` Learn more...' externalDocs: description: See documentation for this operation in Akamai's Linode API url: https://techdocs.akamai.com/linode-api/reference/get-vpc-subnet operationId: get-vpc-subnet responses: '200': content: application/json: schema: additionalProperties: false description: An object describing a VPC Subnet. properties: created: description: __Filterable__, __Read-only__ The date-time of VPC Subnet creation. example: '2023-07-11T00:00:00' format: date-time readOnly: true type: string x-akamai: labels: - Filterable x-linode-filterable: true id: description: __Filterable__, __Read-only__ The unique ID of the VPC Subnet. example: 456 readOnly: true type: integer x-akamai: labels: - Filterable x-linode-cli-display: 1 x-linode-filterable: true ipv4: description: 'IPv4 range in CIDR canonical form. - The range must belong to a private address space as defined in [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918). - Allowed prefix lengths: 1-29. - The range must not overlap with 192.168.128.0/17. - The range must not overlap with other Subnets on the same VPC.' example: 10.0.1.0/24 format: ip type: string x-linode-cli-display: 3 label: description: '__Filterable__ The VPC Subnet''s label, for display purposes only. - Must be unique among the VPC''s Subnets. - Can only contain ASCII letters, numbers, and hyphens (`-`). You can''t use two consecutive hyphens (`--`).' example: cool-vpc-subnet maxLength: 64 minLength: 1 type: string x-akamai: labels: - Filterable x-linode-cli-display: 2 x-linode-filterable: true linodes: description: '__Read-only__ An array of Linode IDs assigned to the VPC Subnet. A Linode is assigned to a VPC Subnet if it has a Configuration Profile with a `vpc` purpose interface with the subnet''s `subnet_id`. Even if the Configuration Profile is not active, meaning the Linode does not have access to the Subnet, the Linode still appears in this array.' items: additionalProperties: false properties: id: description: ID of a Linode assigned to the VPC Subnet. example: 111 type: integer interfaces: description: VPC purpose interfaces with the subnet's `subnet_id` assigned to the Linode. items: additionalProperties: false properties: active: description: Returns `true` if the Interface is in use, meaning that the Linode was powered on using the Configuration Profile to which the Interface belongs. Otherwise returns `false`. example: true type: boolean config_id: description: The globally general entity identifier for the Linode configuration profile that includes the VPC. If this is a VPC Linode interface, the value is `null`. example: 4567 type: - integer - 'null' id: description: ID of the interface. example: 421 type: integer type: object type: array type: object readOnly: true type: array x-linode-cli-display: 5 updated: description: __Filterable__, __Read-only__ The date-time of the most recent VPC Subnet update. example: '2023-09-11T00:00:00' format: date-time readOnly: true type: - string - 'null' x-akamai: labels: - Filterable x-linode-filterable: true type: object x-akamai: file-path: schemas/vpc-subnet.yaml x-example: x-ref: ../examples/get-vpc-subnet-200.json description: A VPC Subnet object. default: content: application/json: schema: additionalProperties: false properties: errors: items: additionalProperties: false description: An object for describing a single error that occurred during the processing of a request. properties: field: description: 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. example: fieldname type: string reason: description: 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](https://techdocs.akamai.com/linode-api/reference/post-ticket) or perform some other action before you can complete the request successfully. example: fieldname must be a valid value type: string type: object x-akamai: file-path: schemas/error-object.yaml type: array type: object description: See [Errors](https://techdocs.akamai.com/linode-api/reference/errors) for the range of possible error response codes. security: - personalAccessToken: [] - oauth: [] summary: Get a VPC subnet tags: - VPC subnets x-akamai: tabs: - syntax: linode-cli vpcs subnet-view $vpcId $vpcSubnetId title: CLI url: https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli x-linode-cli-action: subnet-view put: description: 'Update a VPC Subnet. - The User accessing this operation must have `read_write` grants to the VPC. - A successful request triggers a `subnet_update` event. > --- - __CLI__. ``` linode-cli vpcs subnet-update $vpcId \ --label cool-vpc-subnet ``` Learn more... - __OAuth scopes__. ``` vpc:read_write ``` Learn more...' externalDocs: description: See documentation for this operation in Akamai's Linode API url: https://techdocs.akamai.com/linode-api/reference/put-vpc-subnet operationId: put-vpc-subnet requestBody: content: application/json: schema: additionalProperties: false description: A VPC Subnet Update request object. properties: label: description: '__Filterable__ The VPC Subnet''s label, for display purposes only. - Must be unique among the VPC''s Subnets. - Can only contain ASCII letters, numbers, and hyphens (`-`). You can''t use two consecutive hyphens (`--`).' example: '{{label}}' maxLength: 64 minLength: 1 type: string x-akamai: labels: - Filterable x-linode-cli-display: 2 x-linode-filterable: true type: object x-akamai: file-path: schemas/added-put-vpc-subnet.yaml x-example: x-ref: ../examples/put-vpc-subnet.json description: VPC Update request object. required: true responses: '200': content: application/json: schema: additionalProperties: false description: An object describing a VPC Subnet. properties: created: description: __Filterable__, __Read-only__ The date-time of VPC Subnet creation. example: '2023-07-11T00:00:00' format: date-time readOnly: true type: string x-akamai: labels: - Filterable x-linode-filterable: true id: description: __Filterable__, __Read-only__ The unique ID of the VPC Subnet. example: 456 readOnly: true type: integer x-akamai: labels: - Filterable x-linode-cli-display: 1 x-linode-filterable: true ipv4: description: 'IPv4 range in CIDR canonical form. - The range must belong to a private address space as defined in [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918). - Allowed prefix lengths: 1-29. - The range must not overlap with 192.168.128.0/17. - The range must not overlap with other Subnets on the same VPC.' example: 10.0.1.0/24 format: ip type: string x-linode-cli-display: 3 label: description: '__Filterable__ The VPC Subnet''s label, for display purposes only. - Must be unique among the VPC''s Subnets. - Can only contain ASCII letters, numbers, and hyphens (`-`). You can''t use two consecutive hyphens (`--`).' example: cool-vpc-subnet maxLength: 64 minLength: 1 type: string x-akamai: labels: - Filterable x-linode-cli-display: 2 x-linode-filterable: true linodes: description: '__Read-only__ An array of Linode IDs assigned to the VPC Subnet. A Linode is assigned to a VPC Subnet if it has a Configuration Profile with a `vpc` purpose interface with the subnet''s `subnet_id`. Even if the Configuration Profile is not active, meaning the Linode does not have access to the Subnet, the Linode still appears in this array.' items: additionalProperties: false properties: id: description: ID of a Linode assigned to the VPC Subnet. example: 111 type: integer interfaces: description: VPC purpose interfaces with the subnet's `subnet_id` assigned to the Linode. items: additionalProperties: false properties: active: description: Returns `true` if the Interface is in use, meaning that the Linode was powered on using the Configuration Profile to which the Interface belongs. Otherwise returns `false`. example: true type: boolean config_id: description: The globally general entity identifier for the Linode configuration profile that includes the VPC. If this is a VPC Linode interface, the value is `null`. example: 4567 type: - integer - 'null' id: description: ID of the interface. example: 421 type: integer type: object type: array type: object readOnly: true type: array x-linode-cli-display: 5 updated: description: __Filterable__, __Read-only__ The date-time of the most recent VPC Subnet update. example: '2023-09-11T00:00:00' format: date-time readOnly: true type: - string - 'null' x-akamai: labels: - Filterable x-linode-filterable: true type: object x-akamai: file-path: schemas/vpc-subnet.yaml x-example: x-ref: ../examples/get-vpc-subnet-200.json description: The updated VPC Subnet. default: content: application/json: schema: additionalProperties: false properties: errors: items: additionalProperties: false description: An object for describing a single error that occurred during the processing of a request. properties: field: description: 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. example: fieldname type: string reason: description: 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](https://techdocs.akamai.com/linode-api/reference/post-ticket) or perform some other action before you can complete the request successfully. example: fieldname must be a valid value type: string type: object x-akamai: file-path: schemas/error-object.yaml type: array type: object description: See [Errors](https://techdocs.akamai.com/linode-api/reference/errors) for the range of possible error response codes. security: - personalAccessToken: [] - oauth: - vpc:read_write summary: Update a VPC subnet tags: - VPC subnets x-akamai: tabs: - syntax: "linode-cli vpcs subnet-update $vpcId \\\n --label cool-vpc-subnet" title: CLI url: https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli - syntax: vpc:read_write title: OAuth scopes url: https://techdocs.akamai.com/linode-api/reference/get-started#oauth x-linode-cli-action: subnet-update x-linode-grant: read_write delete: description: 'Delete a single VPC subnet. The user accessing this operation must have `read_write` grants to the VPC. A successful request triggers a `subnet_delete` event. > 📘 > > You need to delete all the Configuration Profile Interfaces that this subnet is assigned to before you can delete it. If those interfaces are active, the associated Linode needs to be shut down before they can be removed. > --- - __CLI__. ``` linode-cli vpcs subnet-delete $vpcId $vpcSubnetId ``` Learn more... - __OAuth scopes__. ``` vpc:read_write ``` Learn more...' externalDocs: description: See documentation for this operation in Akamai's Linode API url: https://techdocs.akamai.com/linode-api/reference/delete-vpc-subnet operationId: delete-vpc-subnet responses: '200': content: application/json: schema: description: The API responds with an empty object. maxProperties: 0 type: object x-akamai: file-path: schemas/added-empty-obj.yaml x-example: x-ref: ../examples/delete-vpc-subnet-200.json description: Delete request successful. default: content: application/json: schema: additionalProperties: false properties: errors: items: additionalProperties: false description: An object for describing a single error that occurred during the processing of a request. properties: field: description: 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. example: fieldname type: string reason: description: 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](https://techdocs.akamai.com/linode-api/reference/post-ticket) or perform some other action before you can complete the request successfully. example: fieldname must be a valid value type: string type: object x-akamai: file-path: schemas/error-object.yaml type: array type: object description: See [Errors](https://techdocs.akamai.com/linode-api/reference/errors) for the range of possible error response codes. security: - personalAccessToken: [] - oauth: - vpc:read_write summary: Delete a VPC subnet tags: - VPC subnets x-akamai: tabs: - syntax: linode-cli vpcs subnet-delete $vpcId $vpcSubnetId title: CLI url: https://techdocs.akamai.com/cloud-computing/docs/getting-started-with-the-linode-cli - syntax: vpc:read_write title: OAuth scopes url: https://techdocs.akamai.com/linode-api/reference/get-started#oauth x-linode-cli-action: subnet-delete x-linode-grant: read_write components: securitySchemes: oauth: flows: authorizationCode: authorizationUrl: https://login.linode.com/oauth/authorize scopes: account:read_only: Allows access to GET information about your account. account:read_write: Allows access to all endpoints related to your account. domains:read_only: Allows access to GET Domains on your account. domains:read_write: Allows access to all Domain endpoints. events:read_only: Allows access to GET your Events. events:read_write: Allows access to all endpoints related to your Events. firewall:read_only: Allows access to GET information about your Firewalls. firewall:read_write: Allows access to all Firewall endpoints. images:read_only: Allows access to GET your Images. images:read_write: Allows access to all endpoints related to your Images. ips:read_only: Allows access to GET your ips. ips:read_write: Allows access to all endpoints related to your ips. linodes:read_only: Allows access to GET Linodes on your account. linodes:read_write: Allow access to all endpoints related to your Linodes. lke:read_only: Allows access to GET LKE Clusters on your account. lke:read_write: Allows access to all endpoints related to LKE Clusters on your account. longview:read_only: Allows access to GET your Longview Clients. longview:read_write: Allows access to all endpoints related to your Longview Clients. monitor:read-write: Allows access to all Monitor (Akamai Cloud Pulse) endpoints. monitor:read_only: Allows access to Monitor (Akamai Cloud Pulse) data. nodebalancers:read_only: Allows access to GET NodeBalancers on your account. nodebalancers:read_write: Allows access to all NodeBalancer endpoints. object_storage:read_only: Allows access to GET information related to your Object Storage. object_storage:read_write: Allows access to all Object Storage endpoints. stackscripts:read_only: Allows access to GET your StackScripts. stackscripts:read_write: Allows access to all endpoints related to your StackScripts. volumes:read_only: Allows access to GET your Volumes. volumes:read_write: Allows access to all endpoints related to your Volumes. vpc:read_write: Allows access to all endpoints related to VPC and Subnet creation, updating, and deletion. tokenUrl: https://login.linode.com/oauth/token type: oauth2 personalAccessToken: scheme: bearer type: http externalDocs: description: See documentation for Akamai's Linode API url: https://techdocs.akamai.com/linode-api/reference x-readme: samples-languages: - curl - python - node