DeleteSubnet

DeleteSubnet

1. API Description

This API is used to delete a subnet.

Note

• This API is an async API. A subnet ID list is returned after the deletion request is sent. However, it does not mean the deletion has been completed. The status of the subnet will be DELETING during the deletion. You can use DescribeSubnets to query the status of the subnet. If this subnet does not exist in the subnet list, it means that the subnet has been deleted successfully. Any operations on the subnets are not allowed while deleting.

• Operations on subnets with instances in it are not supported. You can use DescribeSubnets to query the status of the subnet.

• Only operations on subnets in the status of AVAILABLE or CREATE_FAILED are supported.

2. Input Parameters

The following request parameter list only provides API request parameters.

Parameter Name	Required	Type	Description
subnetId	Yes	String	Subnet ID.

3. Output Parameters

Parameter Name	Type	Description
requestId	String	The unique request ID, which is returned for each request. RequestId is required for locating a problem.

4. Code Example

Example

Delete a subnet.

POST /api/v2/bmc HTTP/1.1
Host: console.zenlayer.com
Content-Type: application/json
X-ZC-Action: DeleteSubnet
<Common Request Params>

Request:
{
  "subnetId": "833032938374308056"
}

Response:
{
  "requestId": "TA8D35A96-1BCC-4D10-96CB-CCB7600C1428",
  "response": {
    "requestId": "TA8D35A96-1BCC-4D10-96CB-CCB7600C1428"
  }
}

5. Developer Resources

Zenlayer Cloud API 2.0 integrates SDKs to make it easier for you to call APIs. More programming languages will be supported.

6. Error Codes

The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.​

HTTP Status Code	Error Code	Description
400	OPERATION_FAILED_RESOURCE_NOT_FOUND	Subnet not found.
403	OPERATION_DENIED_SUBNET_EXIST_INSTANCE	Operations on subnets with instances in it are not supported.
403	OPERATION_DENIED_SUBNET_STATUS_NOT_SUPPORT	Subnet status not supported.