POST · SSL / TLS
Issue a Let's Encrypt certificate
Issue a Let's Encrypt certificate
POST
/api/v1/ssl/actions/request-letsencrypt
Description
Requests issuance for the domain and, when asked, www. and mail.. Returns the requested hostname set and DirectAdmin's acknowledgement; a hostname that does not resolve to this server makes DirectAdmin reject the whole request.
Body
Send as application/json.
| Name | Type | Description |
|---|---|---|
input
required
|
string |
A domain, email address, website URL, or Inleed service id — for example example.se, [email protected] or 42976. Resolved to the owning account automatically, and the resolved target is echoed back in the response. Up to 255 characters.
|
include_www
|
boolean |
Also cover www.<domain>. Only add it if www resolves to this server, or issuance fails.
|
include_mail
|
boolean |
Also cover mail.<domain>. Only add it if mail resolves to this server, or issuance fails.
|
Responses
A 200 response returns the shape shown in the rail.
Every non-2xx response is an RFC 7807 problem with a stable
code.
Commonly returned errors
The codes this operation reaches on its own path: the auth stack, its own validation and
ownership checks, and the transport. Not a closed set — a shared code from the
full registry can still surface. Each links to the code’s own page,
the same URL its type dereferences to.
400
401
No token was presented, or the token is revoked, expired or unknown.
403
The token lacks a required scope, or this account does not own the resource.
404
No such resource for this account.
422
Validation error
429
The rate limit for this token is exhausted. See `Retry-After`.
500
Something went wrong on our side. The failure is logged against `requestId`.