Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| username | string | Yes | Username of the credential |
| secretKeyName | string | Yes | Name of the secret key to assign |
Notes
- Secret key must exist in the project or in the admin project
- Secret key must be of type
SECRET_KEY - Credential must exist
- Only one secret key can be assigned to a credential at a time
- Assigning a new secret key replaces the existing one if present
Response
Success Response (200 OK)
Error Response (400 Bad Request)
Error Response (401 Unauthorized)
Error Response (404 Not Found)
cURL Example
Notes and Warnings
-
Secret Key Requirements:
- Secret key must exist in the project or admin project
- Secret key must be of type
SECRET_KEY - Secret key name is case-sensitive
-
Credential Requirements:
- Credential must exist
- Credential must be in the same project or accessible from the project
-
Replacement Behavior:
- Assigning a new secret key replaces any existing secret key
- Previous secret key assignment is automatically removed
-
Automatic Deployment:
- Credential is automatically deployed to all environments after secret key assignment
- Deployment results are returned in the response
Permissions
- User must have
IDENTITY+MANAGEpermission in the project - For automatic deployment, user must also have
IDENTITY+DEPLOY_UNDEPLOYpermission
Related Documentation
- Remove Secret Key - Remove secret key from credential
- Set Certificate - Assign certificate to credential
- List Credentials - List all credentials

