Release Postpay Instances (Release via POST Request)
Updated at:2025-10-20
This API releases a single pay-as-you-go (post-paid) cloud server instance. Once released, the physical resources used by the instance are reclaimed, and all related data is permanently lost and cannot be recovered.
Request structure
Plain Text
1 POST /v{version}/instance/{instanceId} HTTP/1.1
2 Host: bcc.bj.baidubce.com
3 Authorization: authorization string
4 {
5 "relatedReleaseFlag": relatedReleaseFlag,
6 "deleteCdsSnapshotFlag":deleteCdsSnapshotFlag,
7 "bccRecycleFlag" : bccRecycleFlag,
8 "deleteRelatedEnisFlag" : deleteRelatedEnisFlag,
9 "cdsAttributeActive" : cdsAttributeActive
10 }
Request headers
There are no special headers required beyond the common headers.
Request parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number |
| instanceId | String | Yes | URL parameter | Instance ID |
| relatedReleaseFlag | boolean | Yes | RequestBody | Whether to release all EIPs and cloud disk server data disks attached on the instance at the current moment in an associated manner. When the value is true and the cdsAttributeActive parameter value is true, only disks with associated release attributes are released. When cdsAttributeActive is false, all disks are released |
| deleteCdsSnapshotFlag | boolean | Yes | RequestBody | Specifies whether to release all snapshots of the cloud disk server when releasing the server. If the cdsAttributeActive parameter is set to true, this value is ignored, and automatic snapshots are managed based on associated release attributes. By default, manual snapshots are retained. |
| deleteRelatedEnisFlag | boolean | No | RequestBody | Whether to delete the associated ENI upon instance release |
| bccRecycleFlag | boolean | No | RequestBody | Whether to move the instance to the recycle bin upon release |
| cdsAttributeActive | boolean | No | RequestBody | Whether to release resources based on disk-associated release attributes, defaulting to false. When this parameter is true, resource release will be determined based on the associated release attributes configured for the disks, with priority over the relatedReleaseFlag and deleteCdsSnapshotFlag options |
Response headers
There are no special headers required beyond the common headers.
Response parameters
There are no special response parameters
| Error code | Error description | HTTP status code | Chinese explanation |
|---|---|---|---|
| Instance.ReleaseWhileCreating | Instance can not release during creating. | 403 | Instances in the process of creation cannot be released |
| Instance.ReleaseNotPrepay | Instance can not release if not prepay. | 403 | Non-subscribed (non-prepaid) instances cannot be released |
Request example
Plain Text
1POST /v2/instance/i-YufwpQAe HTTP/1.1
2Host: bcc.bj.baidubce.com
3ContentType: application/json
4Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2015-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
5{
6 "relatedReleaseFlag": true,
7 "deleteCdsSnapshotFlag":true
8}
Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Wed, 03 Dec 2014 06:42:19 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS
