> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/api-reference/network-services/certificate-manager.md).

# Certificate Manager

Use the Certificate Manager API to provision and manage TLS certificates for IONOS CLOUD resources.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Get started</strong></mark></td><td>Authentication, base URL, and a working API example.</td><td><a href="/cloud/api-reference/readme/getting-started.md">Getting Started</a></td></tr><tr><td><mark style="color:blue;"><strong>API Status</strong></mark></td><td>Check service availability and current incidents.</td><td><a href="https://status.ionos.cloud/">https://status.ionos.cloud/</a></td></tr></tbody></table>

## Base URL

```
https://certificate-manager.de-fra.ionos.com
```

## Authorization

Certificate Manager uses Bearer token authentication. Pass your access token in the `Authorization` header:

```
Authorization: Bearer <access_token>
```

## Version

`2.0`

## HTTP Status Codes

| Status Code                 | Message                | Description                                                             |
| --------------------------- | ---------------------- | ----------------------------------------------------------------------- |
| `200 OK`                    | Request succeeds.      | The request was successful.                                             |
| `201 Created`               | Resource created.      | The resource was successfully created.                                  |
| `202 Accepted`              | Request accepted.      | The request has been accepted for processing.                           |
| `204 No Content`            | Success, no content.   | The request was successful, but there is no content to return.          |
| `400 Bad Request`           | Invalid request.       | The request is malformed or contains invalid parameters.                |
| `401 Unauthorized`          | Authentication failed. | Authentication credentials are missing or invalid.                      |
| `403 Forbidden`             | Access denied.         | The authenticated user does not have permission to access the resource. |
| `404 Not Found`             | Resource not found.    | The requested resource does not exist.                                  |
| `409 Conflict`              | Resource conflict.     | The request conflicts with the current state of the resource.           |
| `429 Too Many Requests`     | Rate limit exceeded.   | Too many requests have been sent in a given time.                       |
| `500 Internal Server Error` | Server error.          | An unexpected error occurred on the server.                             |
| `503 Service Unavailable`   | Service unavailable.   | The service is temporarily unavailable.                                 |


---

# 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.ionos.com/cloud/api-reference/network-services/certificate-manager.md?ask=<question>&goal=<user_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.