Apply for physical dedicated line
Updated at：2025-11-11
Description
Apply for physical dedicated line
Request structure
Plain Text
1POST /v{version}/et/init?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "name": {name},
6 "description": {description},
7 "isp": {isp},
8 "intfType": {intfType},
9 "apType": {apType},
10 "apAddr": {apAddr},
11 "userName": {userName},
12 "userPhone": {userPhone},
13 "userEmail": {userEmail},
14 "userIdc": {userIdc},
15 "billing": {
16 "paymentTiming": {paymentTiming},
17 "reservation": {
18 "reservationLength": {reservationLength},
19 "reservationTimeUnit": {reservationTimeUnit}
20 }
21 },
22 "tags": {tags}
23}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). |
| name | String | Yes | RequestBody | Dedicated line name, which supports uppercase and lowercase letters, numbers, and special characters such as -, _, / and ., starting with a letter and a length of 1-65 |
| description | String | No | RequestBody | Description |
| isp | String | Yes | RequestBody | Carrier options, with value range being SP_CMCC/ISP_CUCC/ISP_CYC/ISP_OTHER, respectively corresponding to China Mobile/China Unicom/China Telecom/domestic others |
| intfType | String | Yes | RequestBody | Physical port specifications, with value range being 1G/10G/100G/40G/400G |
| apType | String | Yes | RequestBody | Internet connection type: BAIDU for Baidu internal users, SINGLE for external users |
| apAddr | String | Yes | RequestBody | Access points, with value range being BB/BJYZ/M3A/M3B/M2A/M2B/HKG03/WHGG/SHWGQ/BDBL, respectively corresponding to Beijing Haidian/Beijing Yizhuang/Guangzhou Nansha/Shenzhen/Nanjing/Suzhou/Hong Kong/Wuhan Optical Valley/Shanghai/Baoding |
| userName | String | Yes | RequestBody | Username |
| userPhone | String | Yes | RequestBody | User Mobile Phone Number |
| userEmail | String | Yes | RequestBody | User Email |
| userIdc | String | Yes | RequestBody | Peer address, with the format being Province |
| billing | [Billing](VPC/API Reference/Appendix.md#Billing) | No | RequestBody | Billing information: Currently, only prepay is supported |
| tags | List<[TagModel](ET/API Reference/Appendix.md#TagModel)> | No | RequestBody | List of tag key-value pairs to be created |
Response headers
No special headers are required beyond the standard ones.
Response parameters
| Parameter name | Types | Description |
|---|---|---|
| id | String | Dedicated line ID |
Request example
Plain Text
1POST /v1/et?clientToken=1849ef6b-f73c-4f5d-b88b-259ca47af849 HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2015-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4{
5 "name": "et_18",
6 "description": "Description",
7 "isp": "ISP_CMCC",
8 "intfType": "1G",
9 "apType": "SINGLE",
10 "apAddr": "BJYZ",
11 "userName": "Zhang San",
12 "userPhone": "13333333333",
13 "userEmail": "123@123.com",
14 "userIdc": "Beijing|Municipal District|Dongcheng District|Baidu Technology Park K2",
15 "billing":{
16 "paymentTiming":"Prepaid",
17 "reservation":{
18 "reservationLength":1,
19 "reservationTimeUnit":"month"
20 }
21 },
22 "tags":[
23 {
24 "tagKey": "tagKey",
25 "tagValue": "tagValue"
26 }
27 ]
28}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Thu, 16 Mar 2017 06:29:48 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS
6 {
7 "id": "dcphy-gq65bz9ip712"
8 }