Create routing rules of Dedicated channel
Updated at：2025-11-11
Description
Create routing rules for the dedicated channel.
Request structure
Plain Text
1POST /v{version}/et/{etId}/channel/{etChannelId}/route/rule?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4 {
5 "destAddress": {destAddress},
6 "nexthopType": {nexthopType},
7 "nexthopId": {nexthopId}
8 }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](VPC/API Reference/General Description.md#Idempotence). |
| etId | String | Yes | URL parameter | Dedicated line ID |
| etChannelId | String | Yes | URL parameter | Dedicated channel ID |
| ipVersion | Integer | No | RequestBody | IP protocol type, with value range being [4 |
| destAddress | String | Yes | RequestBody | Destination segment |
| nexthopType | String | Yes | RequestBody | Next hop type, with value range being ["etGateway" |
| nexthopId | String | Yes | RequestBody | Next-hop instance ID |
| description | String | No | RequestBody | Description |
Response headers
No special headers are required beyond the standard ones.
Response parameters
| Parameter name | Types | Description |
|---|---|---|
| routeRuleId | String | Routing rule ID |
Request example
Plain Text
1POST /v1/et/dcphy-gq65bz9ip712/channel/dedicatedconn-zy9t7n91k0iq/route/rule?clientToken=8257tf9d-b98n-3r6n-a93m-297ng49io149 HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2022-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4 {
5 "destAddress": "192.168.0.7",
6 "nexthopType": "etGateway",
7 "nexthopId": "dcgw-p5x55p77u8ah"
8 }Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Thu, 16 Mar 2022 08:11:48 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS
6{
7 "routeRuleId":"dcrr-5afcf643-94e"
8}