Rename a user API key
PATCH
/v1/api-keys/{apiKeyId}Update the display name of an active API key owned by the authenticated user without changing its credential or permissions.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| apiKeyId | path | string | Yes | — |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Human-readable name. |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200API key renamedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | Unique identifier. |
| name | string | Yes | Human-readable name. |
| keyPrefix | string | Yes | — |
| permissions | string[] | Yes | — |
400Invalid API key name
None.
404API key not found
None.
409API key update failed
None.