curl "https://api.scanova.io/custom-domain/42/certificate-request/" \
-H "Authorization: YOUR_API_KEY"
{
"id": 5,
"organization": "Example Inc",
"organizational_unit": "IT",
"country": "US",
"state": "CA",
"locality": "San Francisco",
"email": "ssl@example.com",
"csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIC...\n-----END CERTIFICATE REQUEST-----",
"created": "2026-09-01T09:00:00Z"
}
Custom Domains
Get the latest SSL certificate request
GET /custom-domain//certificate-request/
GET
/
custom-domain
/
{pk}
/
certificate-request
/
curl "https://api.scanova.io/custom-domain/42/certificate-request/" \
-H "Authorization: YOUR_API_KEY"
{
"id": 5,
"organization": "Example Inc",
"organizational_unit": "IT",
"country": "US",
"state": "CA",
"locality": "San Francisco",
"email": "ssl@example.com",
"csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIC...\n-----END CERTIFICATE REQUEST-----",
"created": "2026-09-01T09:00:00Z"
}
Gets the most recent SSL certificate signing request (CSR) for a domain, on
Returns
api.scanova.io, authenticated with your raw API key.
GET https://api.scanova.io/custom-domain/{pk}/certificate-request/
Authorization: YOUR_API_KEY
Enterprise-only. Requires the
CUSTOM_DOMAIN_CUSTOM_SSL quota, which is granted manually — no self-serve plan includes it.integer
required
The domain’s
id.curl "https://api.scanova.io/custom-domain/42/certificate-request/" \
-H "Authorization: YOUR_API_KEY"
{
"id": 5,
"organization": "Example Inc",
"organizational_unit": "IT",
"country": "US",
"state": "CA",
"locality": "San Francisco",
"email": "ssl@example.com",
"csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIC...\n-----END CERTIFICATE REQUEST-----",
"created": "2026-09-01T09:00:00Z"
}
null if no CSR has been created yet. This lets a client resume an in-progress bring-your-own-certificate flow without tracking CSR state itself. 403 if the account lacks the CUSTOM_DOMAIN_CUSTOM_SSL quota; 404 if pk isn’t a domain owned by this account.
Related
- Create an SSL certificate request — generate a new CSR.
- Upload an SSL certificate — the next step once a CA has issued the certificate.
- API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: YOUR_API_KEY. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Path Parameters
Response
Most recent certificate request, or null if none exists.
Was this page helpful?