regfish
Domini, DNS, hosting ed e-mail da un unico fornitore.
Strumenti DNS gratuiti
Verifica SPF, DMARC, DNSSEC e altro su dns-doctor.com
Caratteristiche
Membro diretto di
© 2002-2026 regfish GmbH. Tutti i diritti riservati.
POST
/tls/certificate/{certificate_id}/reissue
TLSCertificatesByID
Authentication
Parameters
Name
Type
Format
Required
Description
certificate_id
string
-
Required
Public TLS certificate ID
Request body
Reissue request payload
tlsCertificateReissueRequesttlsCertificateReissueRequest
{
"csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIC...\n-----END CERTIFICATE REQUEST-----",
"dcv_method": "dns-cname-token"
}Fields
Name
Type
Format
Required
Description
csr
string
-
Required
PEM encoded certificate signing request (CSR).
common_name
string
-
Optional
Fully Qualified Domain Name.
dns_names
array<string>
-
Optional
Optional. If provided, the SAN list must match the current order exactly.
dcv_method
string
-
Required
-
comments
string
-
Optional
Optional provider comment stored with the reissue request.
validity_days
integer
-
Optional
Optional requested certificate lifetime in days for the replacement certificate. The CA only honors this for eligible multi-year plan orders and never beyond the remaining order contract.
Request example
POST
curl --request POST \
--url 'https://api.regfish.com/tls/certificate/7K9QW3M2ZT8HJ/reissue' \
--header 'x-api-key: YOUR_API_KEY' \
--header 'content-type: application/json' \
--data '{
"csr": "-----BEGIN CERTIFICATE REQUEST-----\nMIIC...\n-----END CERTIFICATE REQUEST-----",
"dcv_method": "dns-cname-token"
}'Responses
200
TLS certificate reissue accepted
Response example 200
{
"success": true,
"code": 0,
"response": {
"id": "7K9QW3M2ZT8HJ",
"status": "pending",
"common_name": "example",
"product": "example",
"provider": "digicert",
"dns_names": [
"example"
],
"action_required": false,
"pending_reason": "validation_pending",
"pending_message": "The TLS certificate order is waiting for domain validation.",
"completion_url": "",
"organization_id": null,
"certificate_pem_available": false
}
}400
Invalid request payload or CSR
Response example 400
{
"success": false,
"message": "Invalid request payload or CSR",
"error": "Invalid request payload or CSR"
}401
Unauthorized
Response example 401
{
"success": false,
"message": "Unauthorized",
"error": "Unauthorized"
}404
TLS certificate not found
Response example 404
{
"success": false,
"message": "TLS certificate not found",
"error": "TLS certificate not found"
}409
The TLS certificate cannot be reissued in its current state
Response example 409
{
"success": false,
"message": "The TLS certificate cannot be reissued in its current state",
"error": "The TLS certificate cannot be reissued in its current state"
}500
Unexpected error
Response example 500
{
"success": false,
"message": "Unexpected error",
"error": "Unexpected error"
}502
Upstream TLS provider error
Response example 502
{
"success": false,
"message": "Upstream TLS provider error",
"error": "Upstream TLS provider error"
}