> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/certificate-management/api-certificates.md). # Enrollment REST API {% hint style="warning" %} SCEPman Enterprise Edition only {% endhint %} SCEPman features a REST API to enroll certificates using the *Enrollment over Secure Transport* (EST) protocol. This is an alternative to the SCEP endpoints that require the SCEP-style of authentication, while the REST API uses Microsoft Identities for authentication. The protocol is also much simpler than SCEP. The REST API features two different authentication models. ### Self Service Enrollment As a user, you can interactively authenticate if you have the CSR.SelfService role. This allows you to request certificates for yourself and your devices. See [Self Service Enrollment](/certificate-management/api-certificates/self-service-enrollment.md) for more details. ### API Enrollment You can also authenticate as a service principal that has the CSR.Request.Db role. This allows you to automate certificate enrollment to servers, IoT devices, or in other use cases. See [API Enrollment](/certificate-management/api-certificates/api-enrollment.md) for details. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.scepman.com/certificate-management/api-certificates.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.