Rename a key pair
Updated at：2025-10-20
This API allows users to rename key pairs.
Request structure
Plain Text
1PUT /v{version}/keypair/{keypairId}?{action} HTTP/1.1
2Host: bcc.bj.baidubce.com
3Authorization: authorization string
4{
5 "name" : keypairName
6}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 |
| keypairId | String | Yes | URL parameter | ID of the key pair to be renamed |
| action | String | Yes | Query | Operation executed on the key pair, current value: rename |
| name | String | Yes | RequestBody | The new key pair name can include uppercase and lowercase letters, numbers, Chinese characters, and -_/ special characters. The name must start with a letter and be 1-65 characters long. |
Response headers
No special headers are required beyond the standard ones.
Response parameters
None
Error codes
| Error code | Error description | HTTP status code | Chinese explanation |
|---|---|---|---|
| Keypair.KeypairNotExist | Keypair not exist. | 404 | Key pair does not exist |
| Keypair.KeypairNameInvalid | Keypair name is invalid. | 400 | Invalid key pair name |
Request example
Plain Text
1PUT /v2/keypair/k-h4NDJPhY?rename HTTP/1.1
2Host: bcc.bj.baidubce.com
3ContentType: application/json
4Authorization: bce-auth-v1/f81d3b34e48048fbb2634dc7882d7e21/2015-08-11T04:17:29Z/3600/host/74c506f68c65e26c633bfa104c863fffac5190fdec1ec24b7c03eb5d67d2e1de
5{
6 "name": "newName"
7}Response example
Plain Text
1HTTP/1.1 200 OK
2x-bce-request-id: 1214cca7-4ad5-451d-9215-71cb844c0a50
3Date: Wed, 03 Dec 2014 06:42:19 GMT
4Content-Type: application/json;charset=UTF-8
5Server: BWS