Associate dedicated channel
Updated at：2025-11-11
Description
Associate the dedicated channel.
Request structure
Plain Text
1PUT /v{version}/et/{etId}/channel/{etChannelId}?{action}&clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "extraChannelId": {extraChannelId}
6}Request 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 |
| clientToken | String | No | Query | Idempotence Token, which is an ASCII string with a length not exceeding 64 bits, see details in [ClientToken Idempotence Support](ET/API Reference/General Description.md#Idempotence). |
| action | String | Yes | Query | The value for this API is "associate" |
| etId | String | Yes | URL parameter | Dedicated line ID |
| etChannelId | String | Yes | URL parameter | Dedicated channel ID |
| extraChannelId | String | Yes | RequestBody | Associated dedicated channel ID |
Response headers
No special headers are required beyond the standard ones.
Response parameters
No special response parameters are available.
Request example
Plain Text
1PUT /v1/et/dcphy-gq65bz9ip712/channel/dedicatedconn-zy9t7n91k0iq?associate&clientToken=8257tf9d-b98n-3r6n-a93m-297ng49io149 HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2023-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4{
5 "extraChannelId": "dedicatedconn-rn0yzti2gn1f"
6}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1eb0c3ee-60bb-eeaf-4446-72208ae8bf40
3Date: Wed, 24 Jul 2024 07:17:24 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS