> 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/fr/gestion-des-certificats/api-certificates/api-enrollment.md).

# Inscription via l’API

{% hint style="info" %}
Cette fonctionnalité nécessite la version **2.3.689** ou supérieure.
{% endhint %}

{% hint style="warning" %}
Édition SCEPman Enterprise uniquement
{% endhint %}

SCEPman propose une API REST pour inscrire des certificats. Il s’agit d’une alternative aux points de terminaison SCEP qui nécessitent l’authentification de type SCEP, tandis que l’API REST utilise Microsoft Identities pour l’authentification. Le protocole est également beaucoup plus simple que SCEP.

## Prérequis

### 1. Service Principal

### 2. Paramètres de l’App Service

## Inscription des certificats

Après avoir préparé les prérequis, vous pouvez envoyer un POST d’un PKCS#10/CMS à votre SCEPman avec le chemin HTTP *api/csr*. La réponse HTTP sera le certificat fraîchement émis, encodé en DER.

SCEPman stockera automatiquement tous les certificats émis dans son Storage Account, afin que vous puissiez les lister et les révoquer facilement via le composant Certificate Master.

Une méthode pratique pour envoyer cette requête est notre module PowerShell SCEPmanClient :

{% content-ref url="/pages/e13dc3c6efc569a4b2dd87e2c564bb136d77c73e" %}
[SCEPmanClient](/fr/gestion-des-certificats/api-certificates/scepmanclient.md)
{% endcontent-ref %}

## Autres exemples

Consultez notre [Bibliothèque d’exemples open source sur GitHub](https://github.com/scepman/csr-request) pour découvrir comment utiliser l’API REST de SCEPman.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.scepman.com/fr/gestion-des-certificats/api-certificates/api-enrollment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.