Documentation
Guides for issuing, validating, renewing, and integrating TLS certificates through the sslcertificates.io API.
Documentation
Guides for issuing, validating, renewing, and integrating TLS certificates through the sslcertificates.io API.
API reference
REST resources under /api/v1: domains, certificates, orders, keys, webhooks, and DNS integrations.
Quickstart: issue a certificate
Create an account, mint an API key, and issue a sandbox certificate in a few requests.
API authentication
Organization-scoped Sanctum bearer tokens with abilities. Send Authorization: Bearer and optional X-Organization-Id.
Domain validation
HTTP-01 and DNS-01 flows, including manual records and Cloudflare automation.
Certificate renewals
Automatic scheduling plus a forced renewal endpoint for tests and operations.
Webhooks
HMAC-SHA256 signed JSON events with retries for failed deliveries.
API error codes
Stable error codes for clients. HTTP status is separate from the machine code.
ACME driver notes
How the platform talks to Let’s Encrypt staging and why production is locked.
Certificate objects
Metadata fields stored after X.509 parsing, download rules, and key modes.
Plesk operations
Document root, PHP 8.4, scheduler, queue worker, and backups for the Plesk host.
API changelog policy
Additive changes stay on /api/v1. Breaking changes require a new version path.
Official SDKs
PHP, TypeScript, Python and Go clients generated from the OpenAPI document.
OpenAPI document
The authoritative HTTP contract is served at /openapi.yaml and /openapi.json.
API explorer
Browser console for the sandbox API. Tokens are not stored.