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 |
| certificateName | string | Yes | Certificate name |
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. |
Request Body
None.Response
Success Response (200 OK)
Error Response (400 Bad Request)
cURL Example
Example 1: Delete Certificate (Default: Clear JWK References)
Example 2: Delete Certificate and Clear JWK References
Example 3: Delete Certificate and Delete Related JWKs
Permissions
User must haveSECRETS + MANAGE permission in the project. For undeployment operations (when undeploying certificates from environments), user must also have SECRETS + DEPLOY_UNDEPLOY permission.
Notes and Warnings
-
Permanent Deletion:
- Certificate is permanently deleted
- This action cannot be undone
-
Automatic Undeployment:
- Certificate 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 certificate will be permanently deleted - Default behavior (
NULLIFY) preserves JWKs but removes their reference to the deleted certificate
- If
Related Documentation
- List Certificates - List all certificates
- Create Certificate - Create a new certificate

