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 keystores |
Keystore Object
| Field | Type | Description |
|---|---|---|
| name | string | Keystore name |
| description | string | Keystore description |
| projectId | string | Project ID where keystore belongs |
| keyStoreEnvironmentList | array[object] | List of keystore environments |
Keystore Environment Object
| Field | Type | Description |
|---|---|---|
| environmentId | string | Environment ID (internal identifier) |
| file | string | Encrypted keystore file content (base64-encoded) |
| password | string | Encrypted keystore password |
| alias | string | Default alias for the keystore |
| keyStoreType | string | Keystore type: JKS or PKCS12 |
environmentId (not environmentName). To get environment names, use the Get Keystore endpoint or refer to environment management APIs.
cURL Example
Notes and Warnings
-
Keystore Content:
- Keystore file content is encrypted and included in the response
- Handle keystore data securely
- File content is base64-encoded and encrypted
-
Multiple Environments:
- Each keystore can be deployed to multiple environments
- Each environment has separate keystore configuration
- Different environments can have different passwords and file content
-
Environment ID:
- Response contains
environmentId(internal identifier) - To get environment names, use the Get Keystore endpoint
- Response contains
Permissions
User must have any permission in the project (read access).Related Documentation
- Get Keystore - Get a specific keystore
- Create Keystore - Create a new keystore

