Update the service network interface card
Updated at:2025-10-16
Description
Update service network interface card. The name and description shall not be empty at the same time.
Request structure
Plain Text
1PUT /v{version}/endpoint/{endpointId}?clientToken=1849ef6b-f73c-4f5d-b88b-259ca47af849
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4
5{
6 "name":name,
7 "description":description
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 | 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. |
| endpointId | String | Yes | URL parameter | Service network interface card ID |
| name | String | No | RequestBody | Name of the service network interface card, with a maximum length of 65 characters; available to consist of numbers, letters, underscores, and Chinese characters |
| description | String | No | RequestBody | Service network interface card description, no more than 200 characters |
Response headers
No special headers are required beyond the standard ones.
Response parameters
No response parameters
Request example
Plain Text
1PUT /v1/endpoint/endpoint-11b09ce6?clientToken=1849ef6b-f73c-4f5d-b88b-259ca47af849
2Host: bcc.bj.baidubce.com
3Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2017-03-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
4
5{
6 "name":"test",
7 "description":""
8}
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
