Bind physical dedicated line
Updated at：2025-10-16
Description
When binding a physical dedicated line to a dedicated gateway, cloud network parameters can be configured simultaneously.
Request structure
Plain Text
1PUT /v{version}/etGateway/{etGatewayId}?{action}&clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "etId": "dcphy-478px3km77dh",
6 "channelId": "dedicatedconn-i7c1skfd0djs",
7 "localCidrs": ["192.168.0.0/20"]
8}Request 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 bind |
| clientToken | String | No | Query | Idempotence Token, which is an ASCII string with a length not exceeding 64 bits, for details, refer to ClientToken Idempotence. |
| etId | String | Yes | RequestBody | ID of the bound physical dedicated line. Both etid and channelId must exist simultaneously |
| channelId | String | Yes | RequestBody | ID of the bound dedicated channel. Both etid and channelId must exist simultaneously |
| localCidrs | List<String> | No | RequestBody | Cloud network of dedicated gateway. Users can select this VPC segment or customize one or more segments |
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?bind&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/e84ee938f6466428ff5c16b3562a1cbf3db5928e7f863cedec8820b5d98aa474
4{
5 "etId": "dcphy-478px3km77dh",
6 "channelId": "dedicatedconn-i7c1skfd0djs",
7 "localCidrs": ["192.168.0.0/20"]
8}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: cb337890-fda4-4de7-ae5c-6af8ade82281
3Date: Mon, 09 Jul 2018 02:11:01 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS