POST Certificates Revoke
The POST /Certificates/Revoke method is used to revoke one or more certificates with the specified ID(s). This method returns HTTP 200 OK on a success with a list of the successfully revoked certificate IDs on a success or a list of the failed certificate IDs if any revocations fail.
Permissions for certificates can be configured at multiple levels. You can apply them system-wide—for all certificates The certificate search function allows you to query the Keyfactor Command database for certificates from any available source based on any criteria of the certificates and save the results as a collection that will be availble in other places in the Management Portal (e.g. expiration alerts and certain reports).




Table 311: POST Certificates Revoke Input Parameters
Name | In | Description |
---|---|---|
CertificateIDs | Body | Required. An array of integers containing the list of Keyfactor Command reference IDs for certificates that should be revoked. |
Reason | Body |
An integer containing the specific reason that the certificate is being revoked. The default is Unspecified. |
Comment | Body | Required. A string containing a freeform reason or comment on why the certificate is being revoked. |
EffectiveDate | Body | A string containing the date and time when the certificate will be revoked. The date and time should be given using the ISO 8601 UTC time format YYYY-MM-DDTHH:mm:ss.000Z (e.g., 2023-11-19T16:23:01Z). The default is the current date and time. |
CollectionId | Body |
An optional integer that specifies the certificate collection (CollectionId) to validate whether the user has sufficient permissions to perform the action. If a CollectionId is not provided, the user must have appropriate permissions granted system-wide or via certificate store containers. Providing a CollectionId allows the system to check the user's permissions at the certificate collection level. Permissions are evaluated in the following order:
Use either ContainerId or CollectionId, not both. If both are specified, CollectionId takes precedence, and the ContainerId is ignored (defaults to 0). See Certificate Collection Permissions for more information. |
ContainerId | Body |
An optional integer that specifies the certificate store container (ContainerId) to validate whether the user has sufficient permissions to perform the action. If a ContainerId is not provided, the user must have appropriate permissions granted system-wide or via certificate collections. Providing a ContainerId allows the system to check the user's permissions at the container level. Permissions are evaluated in the following order:
Use either ContainerId or CollectionId, not both. If both are specified, CollectionId takes precedence, and the ContainerId is ignored (defaults to 0). See Container Permissions for more information. |
PublishCRL | Body | A Boolean indicating whether a new CRL should be published following revocation (true) or not (false). The default is true. |


Was this page helpful? Provide Feedback