The POST /CertificateStores/Schedule operation creates and assigns a schedule to one or more certificate stores in Keyfactor Command. The POST request must contain an array of certificate store GUIDs and the properties that make up the schedule to attach to the stores. On success, the operation returns 204 with no content.
Permissions for certificate stores can be set at the system-wide level or certificate store application level. See Application Permissions for more information.
In permission strings, # represents a specific resource identifier. In /certificate_stores/ permission strings it refers to a certificate store application ID (for example, containerId).
Table 443: POST Certificate Stores Schedule Input Parameters
| Name | In | Description |
|---|---|---|
| StoreIds | Body | Required. An array of strings providing the certificate store GUIDs to schedule. |
| Schedule | Body |
Required. An object indicating the inventory schedule for the certificate stores. |
An API is a set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command. Reference and Utility, which allows you to call API operations and view results. It is primarily intended for validation, testing, and workflow A workflow is a series of steps necessary to complete a process. In Keyfactor Command, it refers to the workflow builder, which allows you to automate event-driven tasks such as when a certificate is requested, revoked or found in a certificate store. development, and also serves as an interactive supplement to this API documentation. You can access it from the help menu (
) in the Management Portal.Was this page helpful? Provide Feedback