API Documentation – Certificate Endpoints

Base URL
POST /api/v1/cert
POST /api/v1/pem

Authentication
All requests require the header:

X-Api-Key: <your-guid-api-key>

The API key must be associated with all requested domains and must be enabled.


POST /api/v1/cert

Obtain a multi-domain (SAN) certificate in .pfx format (PKCS#12)

Request Body

{
  "staging": false,
  "domains": "example.com,www.example.com,blog.example.com",
  "profile": "classic"
}
Field Type Required Description Possible values
staging boolean yes Use Let's Encrypt staging environment (for testing) true, false
domains string yes Comma, semicolon or space separated list of domains e.g. "example.com,www.example.com"
profile string no Certificate profile to request "classic", "tlsserver", "shortlived" (default: "classic")

Response


POST /api/v1/pem

Obtain certificates in PEM format (certificate + private key + chain)

Request Body

Same as /cert endpoint:

{
  "staging": false,
  "domains": "example.com,www.example.com",
  "profile": "tlsserver"
}

Response

[
  {
    "Domain": "example.com",
    "Certificate": "-----BEGIN CERTIFICATE-----\n...\n-----END CERTIFICATE-----",
    "PrivateKey": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----",
    "Chain": "-----BEGIN CERTIFICATE-----\n...\n-----END CERTIFICATE-----"
  },
  {
    "Domain": "www.example.com",
    ...
  }
]

Important Notes