Issue Let's Encrypt certificate

Issue free Let’s Encrypt certificate for the CDN resource. Before issuing the certificate, you need to:

• Delegate your domain to our name servers, if the CDN resource accelerates the entire site.
• Specify all CNAMEs in the personal zone, if the CDN resource accelerates only static resources.
• Create a Let’s Encrypt certificate as described [here][2]. Let’s Encrypt certificates will be issued for all CNAMEs of the CDN resource. Certificate issuing can take up to fifteen minutes. By default, we issue an ECDSA Let’s Encrypt certificate. If you need a RSA certificate, you can enable the “use_rsa_le_cert” option for your CDN resource. Notes:
• When a certificate is issued, it will be applied to the CDN resource and HTTPS will be enabled automatically.
• Let’s Encrypt certificate will be automatically renewed before the expiration date.
• Let’s Encrypt certificate will be automatically updated and applied when deleting or adding additional CNAMEs of the CDN resource. Challenge types: By default, we issue Let’s Encrypt certificates using the HTTP-01 challenge. If you prefer to use DNS-01 challenge, you can enable the “use_dns01_le_challenge” option for your CDN resource. Read more about [challenge types][1]. To issue Let’s Encrypt certificate using the DNS-01 challenge the steps below should be done before request issuance:

1. The DNS service is activated.
2. use_dns01_le_challenge option is enabled.
3. _acme-challenge subdomain or resource’s domain is delegated to our nameservers. To find out the nameservers for your account, use the GET request /dns/v2/platform/info. Use retrieved name_server_1 and name_server_2 values from the settings object to create NS records. [1]: https://letsencrypt.org/docs/challenge-types/ [2]: /docs/api-reference/ssl-certificates/add-ssl-certificate

Authorizations

Authorization · string · header · required

API key for authentication. Make sure to include the word apikey, followed by a single space and then your token. Example: apikey 1234$abcdef

Path Parameters

id · integer · required

CDN resource ID.

Body

application/json

sslData · integer · required

ID of Let's Encrypt certificate obtained [here][1]. It can be used only with "sslEnabled": true. [1]: /docs/api-reference/ssl-certificates/add-ssl-certificate

Example:

192

sslEnabled · boolean · required

Defines whether the HTTPS protocol is enabled for CDN resource. Possible values:

• true — HTTPS is enabled for the CDN resource. Certificate can be linked.
• false — HTTPS is disabled for the CDN resource. Certificate cannot be linked.

Example:

true

Response

200

Successful.