Selective release of EIP
Updated at：2025-10-16
Selective release of EIP
Description
- Choose to either directly release the specified EIP or move it to the bucket trash. The default option is direct release.
- EIP instances with expired prepay, postpay-by-traffic, or postpay-by-bandwidth statuses can either be moved to the bucket trash or directly released.
- Once a specified EIP is released, it cannot be recovered.
- EIP instances in the bucket trash are retained for 7 days. After this period, they are automatically released and irreversible. During the 7 days, you can manually choose to restore or delete a specific EIP.
- If an EIP instance is bound to another instance, it must first be unbound before it can be released directly.
- When an EIP instance enters the bucket trash, all binding relationships are forcibly removed and need to be reconfigured if restored.
- EIPs in the bucket trash are subject to a quota of 10 per region, retained in reverse chronological order by default. If the number of EIPs in the bucket trash reaches 10, new entries will displace the oldest ones.
- If the EIP instance in postpay mode incurs debt, the system will automatically release it, regardless of the selected option.
Request structure
Plain Text
1DELETE /v{version}/eip/{eip}?releaseToRecycle={releaseToRecycle}&clientToken={clientToken} HTTP/1.1
2Host: eip.bj.baidubce.com
3Authorization: authorization stringRequest headers
No special headers beyond common headers.
Request parameters
| Parameter name | Types | Required or not | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | The current API version number is 1. |
| eip | String | Yes | URL parameter | Selected EIP addresses for release include both IPv4 and IPv6 EIPs. |
| releaseToRecycle | Boolean | No | Query | Determines whether the specified EIP should be moved to the bucket trash. The default is false, meaning the EIP will be directly released. |
| clientToken | String | No | Query | Idempotence Token, an ASCII string with a maximum length of 64 characters. For further details, refer to the Idempotence documentation. |
Response Status Code
Respond with 200 after successful operation, and respond with error codes after failed operation, as shown in [Error Codes](EIP/API Reference/Error code.md)
Response headers
No special headers beyond common headers.
Response parameters
There are no special response parameters
IPv4 EIP request example
Plain Text
1DELETE /v1/eip/180.181.3.133?releaseToRecycle=true&clientToken=be31b98c-5e41-4838-9830-9be700de5a20 HTTP/1.1
2HOST: eip.bj.baidubce.com
3Authorization: bce-auth-v1/5e5a8adf11ae475ba95f1bd38228b44f/2022-02-14T02:14:00Z/1800/host;x-bce-date/ec3c0069f9abb1e247773a62707224124b2b31b4c171133677f9042969791f02IPv6 EIP request example
Plain Text
1DELETE /v1/eip/240c:4082:ffff:ff01:0:4:0:12a?releaseToRecycle=true&clientToken=910ba8a8-fa0e-4cd5-a0b9-f0c7a89ccb82 HTTP/1.1
2HOST: eip.bj.baidubce.com
3Authorization: bce-auth-v1/5e5a8adf11ae475ba95f1bd38228b44f/2022-02-14T02:14:00Z/1800/host;x-bce-date/ec3c0069f9abb1e247773a62707224124b2b31b4c171133677f9042969791f02Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 946002ee-cb4f-4aad-b686-5be55df27f09
3Date: Tue, 14 Feb 2022 02:14:03 GMT
4Transfer-Encoding: chunked
5Content-Type: application/json;charset=UTF-8
6Server: BWS