Unbind physical dedicated line
Updated at：2025-10-16
Description
Unlink a physical dedicated line from a dedicated gateway.
Request structure
Plain Text
1PUT /v{version}/etGateway/{etGatewayId}?{action}&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. |
| etGatewayId | String | Yes | URL parameter | ID of the dedicated gateway |
| action | String | Yes | Query | Action executed on the dedicated gateway instance. In this API, the value of this parameter is unbind |
| 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). |
Description: Physical dedicated line can only be unbound when the dedicated gateway is in the running state. Unbinding physical dedicated line from dedicated gateway will simultaneously clear cloud network parameters.
Response headers
No additional headers beyond standard ones.
Response parameters
No special response parameters are available.
Request example
Plain Text
1PUT /v1/etGateway/dcgw-4ds9x3kmds88?unbind&clientToken=ac31ef8c-5e41-4k38-9ds0-9de700ds5b20 HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/bf427691810a11e8a106475a8496ca04/2018-07-06T11:02:49Z/3600/host;x-bce-date/e84ee938f6466428ff5c16b3562a1cbf3db5928e7f863cedec8820b5d98aa474Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: f76a08db-59dc-4d6e-841d-b36989d75d15
3Date: Mon, 09 Jul 2018 02:18:41 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS