Order a certificate from your own CSR

Only for hostnames registered with certificate: "csr". You generate the keypair and sign a PKCS#10 request over the hostname; we place the ACME order, answer the DNS-01 challenge in our zone, and store the issued chain for you to fetch. We never see the private key.

First issuance and every renewal arrive the same way - there is no difference between them from here. Renewal is yours to schedule. We hold no key for this hostname, so we cannot build a replacement request and nothing renews it automatically. Watch expires_at on the GET.

The request must name exactly the hostname you registered, and nothing else. Returns 202: the order is queued, not issued. Poll the GET.

post/v1/hostnames/{id}/certificate

Request

  • Base URL: https://dnsmint.com/api
  • URL: https://dnsmint.com/api/v1/hostnames/{id}/certificate
  • Auth: HTTP bearer

Path parameters

idstring required

Request body

csrstring required

A PKCS#10 certificate request, PEM or bare base64. Must name exactly the hostname (and its wildcard when wildcard is true) in subjectAltName, and be signed by its own key. ECDSA, or RSA of at least 2048 bits, with SHA-256, SHA-384 or SHA-512.

wildcardboolean

Cover *.hostname as well. The csr must name both.

ca'letsencrypt' | 'google'

Which authority issues. Omitted, we pick. See https://dnsmint.com/ca

Response

The order was accepted and queued

idstring

The order id.

statestring

Where the order is. pending on acceptance; it advances in the background.

namesstring[]

Every name the certificate will cover.

castring

Which authority is issuing.

issuerstring

That authority's name.

Changes

No recorded changes to this operation across all 1 revision of this API.