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 |
| keystoreName | string | Yes | Name of the keystore to delete |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| jwkDeleteAction | string | No | Action to take on referenced JWKs: NULLIFY (clear references) or DELETE (delete JWKs completely). Defaults to NULLIFY if not provided. |
Response
Success Response (200 OK)
cURL Example
Example 1: Delete Keystore (Default: Clear JWK References)
Example 2: Delete Keystore and Clear JWK References
Example 3: Delete Keystore and Delete Related JWKs
Notes and Warnings
-
Permanent Deletion:
- Keystore is permanently deleted
- This action cannot be undone
-
Automatic Undeployment:
- Keystore is automatically undeployed from all environments
- Undeployment results are returned in the response
-
Referenced JWKs:
- If
jwkDeleteAction=NULLIFYor not provided (default), JWK references will be cleared - If
jwkDeleteAction=DELETE, all JWKs created from this keystore will be permanently deleted - Default behavior (
NULLIFY) preserves JWKs but removes their reference to the deleted keystore
- If
Permissions
User must haveSECRETS + MANAGE permission in the project. For undeployment operations (when undeploying keystores from environments), user must also have SECRETS + DEPLOY_UNDEPLOY permission.
Related Documentation
- List Keystores - List all keystores
- Create Keystore - Create a new keystore

