Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer {token} | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
Query Parameters
None.Response
Success Response (200 OK)
Response Fields
| Field | Type | Description |
|---|---|---|
| success | boolean | Indicates if the request was successful |
| resultList | array[object] | List of keys |
Key Object
| Field | Type | Description |
|---|---|---|
| name | string | Key name |
| description | string | Key description |
| projectId | string | Project ID where key belongs |
| keyType | string | Key type: SECRET_KEY, PRIVATE_KEY, or PUBLIC_KEY |
| cryptoKeyInfoEnvironmentList | array[object] | List of key environments |
Key Environment Object
| Field | Type | Description |
|---|---|---|
| environmentId | string | Environment ID (internal identifier) |
| content | string | Encrypted key content (base64-encoded) |
| alias | string | Key alias (optional identifier) |
environmentId (not environmentName). To get environment names, use the Get Key endpoint or refer to environment management APIs.
cURL Example
Notes and Warnings
-
Key Content:
- Key content is encrypted and included in the response
- Handle key data securely
- Content is base64-encoded and encrypted
-
Multiple Environments:
- Each key can be deployed to multiple environments
- Each environment has separate key configuration
-
Environment ID:
- Response contains
environmentId(internal identifier) - To get environment names, use the Get Key endpoint
- Response contains
Permissions
User must have any permission in the project (read access).Related Documentation
- Get Key - Get a specific key
- Create Key - Create a new key

