List Keystores

Retrieves all keystores for a specified project. Keystores are containers for cryptographic keys and certificates used for secure communication and authentication.

​

Endpoint

GET /apiops/projects/{projectName}/keystores/

​

Authentication

Requires a Personal API Access Token.

​

Header

Authorization: Bearer YOUR_TOKEN

​

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)

{
  "success": true,
  "resultList": [
    {
      "name": "my-keystore",
      "description": "Keystore for API security",
      "projectId": "project-id",
      "keyStoreEnvironmentList": [
        {
          "environmentId": "env-id-123",
          "file": "encrypted-keystore-file-content",
          "password": "encrypted-password",
          "alias": "my-alias",
          "keyStoreType": "JKS"
        }
      ]
    }
  ]
}

​

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

Note: Response contains environmentId (not environmentName). To get environment names, use the Get Keystore endpoint or refer to environment management APIs.

​

cURL Example

curl -X GET \
  "https://demo.apinizer.com/apiops/projects/MyProject/keystores/" \
  -H "Authorization: Bearer YOUR_TOKEN"

​

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

​

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