API reference
All operations are sourced from the contract and enriched with request and response examples.
Certificates
Organizations
curl --request POST \
--url 'https://api.regfish.com/tls/certificate' \
--header 'x-api-key: YOUR_API_KEY' \
--header 'content-type: application/json' \
--data '{
"sku": "RapidSSL",
"common_name": "www.example.com",
"csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIC...\n-----END CERTIFICATE REQUEST-----",
"dcv_method": "email",
"validity_days": 199
}'curl --request GET \
--url 'https://api.regfish.com/tls/certificate/1' \
--header 'x-api-key: YOUR_API_KEY'curl --request GET \
--url 'https://api.regfish.com/tls/certificate/1/download/pem' \
--header 'x-api-key: YOUR_API_KEY'curl --request POST \
--url 'https://api.regfish.com/tls/certificate/1/revoke' \
--header 'x-api-key: YOUR_API_KEY' \
--header 'content-type: application/json' \
--data '{
"comment": "key compromise confirmed",
"revocation_reason": "key_compromise"
}'certbro for Linux
If you want to move from the TLS API to operable Linux automation faster, certbro is the direct next step.
Open-source CLI for TLS automation, DNS DCV, and unattended renewals.
From order to revocation. The regfish TLS API covers common certificate workflows in a scriptable flow: ordering, status checks, downloads, and revocations can be integrated directly into internal processes and deployments.
The examples below show production-oriented calls for certificate lifecycle management so you can build repeatable operations for shorter lifetimes.