Create service network interface card
Updated at：2025-10-16
Description
Create service network interface card
Request structure
Plain Text
1POST /v{version}/endpoint?clientToken={clientToken} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4 {
5 "vpcId": vpcId,
6 "name": name,
7 "subnetId": subnetId,
8 "service":service,
9 "description": description,
10 "ipAddress": ipAddress,
11 "bandwidth": 20,
12 "billing": {
13 "paymentTiming": "Postpaid"
14 },
15 "tags": [
16 {
17 "tagKey": "tagkey",
18 "tagValue": "tagvalue"
19 }
20 ],
21 "resourceGroupId": "RESG-UoMgbkuLNjj"
22 }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 |
| clientToken | String | No | Query | Idempotence token, which is an ASCII string with a length not exceeding 64 bits, see details in ClientToken Idempotence Support |
| vpcId | String | Yes | RequestBody | ID of the VPC to which it belongs |
| name | String | Yes | RequestBody | Name of service network interface card, which supports uppercase and lowercase letters, numbers, and special characters such as -, / and ., and Chinese, starting with a letter, with a length of 1-65. |
| subnetId | String | Yes | RequestBody | ID of the subnet to which it belongs |
| service | String | Yes | RequestBody | Mounted service domain name |
| description | String | No | RequestBody | Service network interface card description |
| ipAddress | String | No | RequestBody | Specify service network interface card IP address. If not provided, an IP address will be automatically assigned |
| bandwidth | Integer | Yes | RequestBody | Specify service network interface card bandwidth |
| billing | [Billing](VPC/API Reference/Appendix.md#billing) | Yes | RequestBody | Billing information |
| tags | List<[TagModel](VPC/API Reference/Appendix.md#TagModel)> | No | RequestBody | Tag |
| resourceGroupId | String | No | RequestBody | Resource group |
Response headers
No special headers are required beyond the standard ones.
Response parameters
| Parameter name | Types | Description |
|---|---|---|
| id | String | Service network interface card ID |
| ipAddress | String | ID address |
Request example
Plain Text
1POST /v1/endpoint?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{
6 "vpcId": "vpc-IyWRtII7",
7 "name": "name",
8 "subnetId": "sbn-1A09ef6b",
9 "service": "www.test.com",
10 "description": "",
11 "ipAddress": "192.168.0.1",
12 "bandwidth": 20,
13 "billing": {
14 "paymentTiming": "Postpaid"
15 },
16 "tags": [
17 {
18 "tagKey": "tagkey",
19 "tagValue": "tagvalue"
20 }
21 ],
22 "resourceGroupId": "RESG-UoMgbkuLNjj"
23 } 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 {
8 "id": "endpoint-11b09ce6",
9 "ipAddress": "192.168.0.1"
10 }