Release EIP
Last Updated：2020-10-21
- Release the specified EIP, and the released EIP cannot be recovered.
- If EIP is bound to any instance, it can be released before unbinding.
- If you want to release the prepaid EIP in advance, please proceed with the ticket.
Request structure
DELETE /v{version}/eip/{eip}?clientToken={clientToken} HTTP/1.1
Host: eip.bj.baidubce.com
Authorization: authorization stringRequest header
There are no other special headers except the public headers.
Request parameter
| Parameter name | Type | Required or not | Parameter position | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number (the current value is 1) |
| eip | String | Yes | URL parameter | Released EIP, expressed with dotted decimal notation |
| clientToken | String | Yes | Query parameter | Idempotence, for details, please see Idempotence |
Return status code
200 is returned successfully, for the failed return, please see Error Code.
Return header
There are no other special headers except the public headers.
Return parameter
No special return parameters
Request example
DELETE /v1/eip/180.76.122.3?clientToken=be31b98c-5e41-4838-9830-9be700de5a20 HTTP/1.1
HOST eip.bj.baidubce.com
Authorization bce-auth-v1/5e5a8adf11ae475ba95f1bd38228b44f/2016-04-10T08:26:52Z/1800/host;x-bce-date/ec3c0069f9abb1e247773a62707224124b2b31b4c171133677f9042969791f02Response example
HTTP/1.1 200 OK
x-bce-request-id: 946002ee-cb4f-4aad-b686-5be55df27f09
Date: Wed, 10 Apr 2016 08:26:52 GMT
Transfer-Encoding: chunked
Content-Type: application/json;charset=UTF-8
Server: BWS