Delete reserved network segment
Updated at：2025-10-16
Description
Remove the reserved network segment.
Request structure
Plain Text
1DELETE /v{version}/subnet/ipreserve/{ipReserveId}?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization stringRequest 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 | For API version No., the current value is 1 |
| ipReserveId | String | Yes | URL parameter | ID of reserved network segment |
| clientToken | String | No | Query | Idempotence Token, which is an ASCII string with a length not exceeding 64 bits. See details in [ClientToken Idempotence Support](VPC/API Reference/General Description.md#Idempotence). |
Response headers
No special headers are required beyond the standard ones.
Response parameters
There are no special response parameters
Request example
Plain Text
1DELETE /v1/subnet/ipreserve/ipr-te2pa9cv4ikk?clientToken=3fcf57c1-73c7-42c9-8075-6dda96c06f6b HTTP/1.1
2Host: bcc.bj.baidubce.com
3Content-Type: application/json;charset=UTF-8
4Authorization: bce-auth-v1/69ce105be4b111edada7e5a923788a49/2023-04-27T04:21:39Z/3600/host;x-bce-accesskey;x-bce-account;x-bce-client-ip;x-bce-date;x-bce-gateway-count;x-bce-request-id;x-bce-user-agent/1c00a1a4540c5279d9f99da5fe5dfac6ebf5bb86cfad874fc4afe7dd60c08131Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 81c86a9c-ca0f-4289-82b3-d02b4510f692
3Date: Thu, 27 Apr 2023 04:21:39 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS