Update Keystore

​

Endpoint

PUT /apiops/projects/{projectName}/keystores/{keystoreName}/

​

Authentication

​

Header

Authorization: Bearer YOUR_TOKEN

​

Request

​

Headers

​

Path Parameters

​

Query Parameters

​

Request Body

{
  "name": "updated-keystore",
  "description": "Updated keystore description",
  "keyStoreEnvironmentList": [
    {
      "environmentName": "production",
      "file": "base64-encoded-updated-keystore-file-content",
      "password": "updated-password",
      "alias": "updated-alias",
      "keyStoreType": "JKS"
    }
  ]
}

​

Request Body Fields

​

Keystore Environment Object

​

Notes

• Request Format: This API uses application/json content type. Keystore file content must be base64-encoded and included in the JSON body (not uploaded as a file).
• All fields are optional - only provided fields will be updated
• name can be changed, but must remain unique within the project
• environmentName is used to identify the environment (not environmentId)
• Keystore file content must be base64-encoded if provided

​

Response

​

cURL Example

​

Example 1: Update Keystore with JWK Updates

curl -X PUT \
  "https://demo.apinizer.com/apiops/projects/MyProject/keystores/my-keystore/?jwkUpdateAction=UPDATE&updateScope=SAME_PROJECT" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "updated-keystore",
    "description": "Updated keystore description",
    "keyStoreEnvironmentList": [
      {
        "environmentName": "production",
        "file": "base64-encoded-updated-keystore-file-content",
        "password": "updated-password",
        "alias": "updated-alias",
        "keyStoreType": "JKS"
      }
    ]
  }'

​

Example 2: Update Keystore and Clear JWK References

curl -X PUT \
  "https://demo.apinizer.com/apiops/projects/MyProject/keystores/my-keystore/?jwkUpdateAction=NULLIFY" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Updated description only",
    "keyStoreEnvironmentList": [
      {
        "environmentName": "production",
        "file": "base64-encoded-updated-keystore-file-content",
        "password": "updated-password",
        "alias": "updated-alias",
        "keyStoreType": "PKCS12"
      }
    ]
  }'

​

Example 3: Update Keystore Name Only

curl -X PUT \
  "https://demo.apinizer.com/apiops/projects/MyProject/keystores/my-keystore/" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "new-keystore-name"
  }'

​

Notes and Warnings

• Keystore Name:
  • Can be changed during update
  • New name must be unique within the project
  • If name is changed, the keystore will be accessible by the new name
• Referenced JWKs:
  • If jwkUpdateAction=UPDATE, JWKs created from this keystore will be re-parsed and updated
  • If jwkUpdateAction=NULLIFY or not provided (default), JWK references will be cleared
  • updateScope determines which JWKs to update when jwkUpdateAction=UPDATE: SAME_PROJECT or ALL_PROJECTS
  • Default behavior (NULLIFY) ensures JWKs don’t reference deleted or updated keystores
• Environment Name:
  • Use environmentName (not environmentId) to specify the environment
  • Environment name must exist and be accessible
• Keystore Type:
  • keyStoreType must match the actual keystore file format
  • JKS: Java KeyStore format
  • PKCS12: PKCS#12 format (also known as .p12 or .pfx)
• Partial Updates:
  • Only provided fields will be updated
  • Omitted fields will remain unchanged
• Automatic Deployment:
  • Keystore is automatically deployed to all specified environments after update
  • Deployment results are returned in the response

​

Permissions

​

Related Documentation

• List Keystores - List all keystores
• Create Keystore - Create a new keystore