Release peering connections
Updated at：2025-10-16
Description
Release peering connections.
- Cross-account release can only be initiated by the originating end;
- Peering connections with prepay available without being expired cannot be released;
- Peering connections with prepay negotiation failed can be released;
Request structure
Plain Text
1DELETE /v{version}/peerconn/{peerConnId}?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization stringRequest parameters
| Parameter name | Types | Whether required | Parameter location | Description |
|---|---|---|---|---|
| version | String | Yes | URL parameter | API version number, current value is 1. |
| peerConnId | String | Yes | URL parameter | ID of peering connection |
| 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 additional headers beyond standard ones.
Response parameters
No special response parameters are available.
Request example
Plain Text
1DELETE /v1/peerconn/peerconn-9td54fmx143e?clientToken=fc31ef8c-5e41-4k38-9ds0-9def00ds5b60 HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/2830b179831d11e8be57233b1de1e808/2018-07-09T02:38:52Z/3600/host;x-bce-account;x-bce-client-ip;x-bce-date;x-bce-request-id;x-bce-security-token/9c4e21651b58c9d37c5c475f82eeea0ee5c209cfbd25d3638b94ce33ed98125bResponse example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: f7302165-756d-4c83-bb7a-1d4548fbba8c
3Cache-Control: no-cache
4Server: BWS