Create dedicated gateway
Updated at：2025-10-16
Description
When creating a dedicated gateway, users can optionally bind both a physical dedicated line and a dedicated channel at the same time.
Request structure
Plain Text
1POST /v{version}/etGateway?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "name": "dcGateway",
6 "vpcId": "vpc-IyrqYIQ7",
7 "speed": 200,
8 "description": "",
9 "etId": "dcphy-478px3km77dh",
10 "channelId": "dedicatedconn-i7c1skfd0djs",
11 "localCidrs": ["192.168.0.0/20"],
12 "tags":[
13 {
14 "tagKey": "tagKey",
15 "tagValue": "tagValue"
16 }
17 ],
18 "resourceGroupId": "RESG-UoMgbkuLNjj"
19}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 | API version number, current value is 1. |
| clientToken | String | Yes | Query | Idempotence Token, which is an ASCII string with a length not exceeding 64 bits, for details, refer to ClientToken Idempotence. |
| name | String | Yes | RequestBody | Name of dedicated gateway, which supports uppercase and lowercase letters, numbers, and special characters such as-, _, / and., starting with a letter, with a length of 1-65. |
| vpcId | String | Yes | RequestBody | ID of VPC to which the dedicated gateway belongs |
| speed | Integer | Yes | RequestBody | Bandwidth limit for the dedicated gateway, measured in Mbps. Must be an integer between 2 and 10,000. |
| description | String | No | RequestBody | Description of dedicated gateway, with a maximum length of 200 characters |
| etId | String | No | RequestBody | ID of the bound physical dedicated line. Both etid and channelId must exist simultaneously |
| channelId | String | No | RequestBody | ID of the bound dedicated channel. Both etid and channelId must exist simultaneously |
| localCidrs | No | RequestBody | Cloud network of dedicated gateway: Users may select the current VPC segment or customize one or more segments. This is configurable only when parameters etId and channelId exist simultaneously | |
| tags | List<[TagModel](VPC/API Reference/Appendix.md#TagModel)> | No | RequestBody | List of tag key-value pairs to be created |
| resourceGroupId | String | No | RequestBody | Resource group |
Response headers
No special headers are required beyond the standard ones.
Response parameters
| Parameter name | Types | Description |
|---|---|---|
| etGatewayId | String | ID of created dedicated gateway |
Request example
Plain Text
1POST /v1/etGateway?clientToken=8257tf9d-b98n-3r6n-a93m-297ng49io149 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 "name": "dcGateway",
6 "vpcId": "vpc-IyrqYIQ7",
7 "speed": 200,
8 "description": "",
9 "etId": "dcphy-478px3km77dh",
10 "channelId": "dedicatedconn-i7c1skfd0djs",
11 "localCidrs": ["192.168.0.0/20"],
12 "tags":[
13 {
14 "tagKey": "tagKey",
15 "tagValue": "tagValue"
16 }
17 ],
18 "resourceGroupId": "RESG-UoMgbkuLNjj"
19}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Fri, 06 July 2018 07:06:06 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS
6{
7 "etGatewayId": "dcgw-4ds9x3kmds88"
8}