> For the complete documentation index, see [llms.txt](https://emca.emudhra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emca.emudhra.com/integrating-emca/rest-api-support/certificate-management.md).

# Certificate Management

## Prerequisites

Register your application with emCA and obtain credentials. Provide:

* **Username (appCode)**
* **Password**
* **Source IP address** for allowlisting

All API traffic must use HTTPS (TLS 1.2+).

##  Registration

1. Submit **appCode**, **password**, and **IP address**.
2. emCA issues a **ClientID** for your application.
3. Use the ClientID for all subsequent API requests.

## Authentication (JWT)

Certificate Management APIs use a short-lived **JWT** for authentication. To obtain a token, call the token endpoint with your **appCode**, **password**, and **ClientID**. The response returns a JWT and its expiry (`exp`). Include the token in each request header:

```
makefile

Authorization: Bearer <JWT>
```

Renew the token before expiry and discard expired tokens. Use one unique token per application context; do not share tokens across tenants or environments.

## Certificate Management APIs documentation

All APIs related to certificate issuance, management, and lifecycle operations:

* createCertificates
* createCustomCertificate
* createKeyStore
* getCAs
* getCertInfo
* getCertificate
* getCertificateChain
* getCertInfo
* getProfileInfo
* getProfiles
* reinstate
* rekey
* revoke
* suspend
* verifySignature

## emCA Version-Based Postman Links:

* [V5.0.0](https://documenter.getpostman.com/view/40123569/2sBXqDuPtp#261138d1-c52a-40d8-89b0-67a0ce078115)

{% hint style="info" %}
Please refer in the respective version sections for older API Postman Collections.
{% endhint %}


---

# 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://emca.emudhra.com/integrating-emca/rest-api-support/certificate-management.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.