POST /certificates
Creates a new Certificate.
The default type uploaded allows for uploading your existing certificate and private_key in PEM format. You have to monitor its expiration date and handle renewal yourself.
In contrast, type managed requests a new Certificate from Let's Encrypt for the specified domain_names. Only domains managed by Hetzner DNS are supported. We handle renewal and timely alert the project owner via email if problems occur.
For type managed Certificates the action key of the response contains the Action that allows for tracking the issuance process. For type uploaded Certificates the action is always null.
Servers
- https://api.hetzner.cloud/v1
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
domain_names[] |
Array | No |
Domains and subdomains that should be contained in the Certificate issued by Let's Encrypt. Required for type |
private_key |
String | No |
Certificate key in PEM format. Required for type |
name |
String | Yes |
Name of the Certificate |
certificate |
String | No |
Certificate and chain in PEM format, in order so that each record directly certifies the one preceding. Required for type |
labels |
Object | No |
User-defined labels ( |
type |
String | No |
Choose between uploading a Certificate in PEM format or requesting a managed Let's Encrypt Certificate. Possible values:
Default value: "uploaded" |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.