Skip to main content

2.12 Replace SSL Subscription Information

2.12.1 API Information

Test Environment
Production Environmenthttps://portal.racent.com/ssl/replace
Request MethodPOST
content-typemultipart/form-data
DescriptionThis interface is used to replace SSL subscription information. It is only related to SSL certificates. Replacing SSL subscription information is only allowed when the SSL subscription status is issued.

2.12.2 Parameter Definition

Parameter NameParameter TypeRequiredDescription
api_tokenStringYIdentity credential. Please contact Racent technical support to generate the token.
certIdStringYracent certificate ID
refIdStringNThe unique customer order number provided by the customer.
domainVerificationPicFileNThis field is required (Y) when the domain validation method is VERIFY_DOCUMENT. It is used for Domain Control Validation (DCV) (currently only supported by CFCA).
paramsStringYReplacement information, described in detail as follows.
csrStringYNote: The domain name in the CSR information must be consistent with the domain name in the CSR from the original SSL subscription.
uniqueValueStringNRelevant only for Sectigo products. 1–20 characters (a-z, A-Z, 0-9) used by resellers to independently generate validation values.
dcvMethodStringNSet the application domain validation method uniformly.
Must be one of the following four methods:
EMAIL (email validation)
HTTP_CSR_HASH (file validation)
CNAME_CSR_HASH (DNS validation)
HTTPS_CSR_HASH (HTTPS file validation)
VERIFY_DOCUMENT (domain certificate proof, only supported by CFCA)
This field is required (Y) for CFCA.
domainInfoStringYDomain information.
Example:
[
{ "dcvEmail": "admin@xxx.com",
"dcvMethod": "EMAIL",
"domainName": "www.xxx.com"
},
{
"dcvEmail": "admin@aaa.com",
"dcvMethod": "EMAIL",
"domainName": "aaa.com"
},
"dcvEmail": "admin@racent.com",
"dcvMethod": "EMAIL",
"domainName": "racent.com"
}
]
Detailed description as follows:
dcvMethodStringYDomain Control Validation (DCV) method.
Must be one of the following four methods:
EMAIL(Email validation)
HTTP_CSR_HASH(File validation)
CNAME_CSR_HASH(DNS validation)
HTTPS_CSR_HASH(HTTPS file validation)
When the upper-level dcvMethod does not exist, this field is required (Y).
When the upper-level dcvMethod exists and this field is also set, the upper-level dcvMethod will take precedence.
dcvEmailStringNDomain Control Validation (DCV) email address.
When this field is set to N, the default values are as follows
racent.com : admin@racent.com
www.racent.com : admin@racent.com
*.racent.com : admin@racent.com
domainNameStringYDomain name
organizationInfoStringNThis parameter is required (Y) when you need to change the organization information.
organizationCityStringNCity where the company is located.
organizationNameStringNCompany name.
organizationMobileStringNCompany phone number.
organizationAddressStringNCompany address.
organizationCountryStringNCountry where the company is located (two-letter code as defined in the ISO 3166-1 standard).
organizationPostCodeStringNPostal code of the company's location.

Function Response

Parameter NameParameter TypeRequiredDescription
codeIntYReturn status; for detailed explanations, see Appendix 3.1
errorsObject or StringNSpecific error information when the return status is an error.
dataObjectNThis parameter is present (Y) when the return status is success. Detailed description is as follows:
certIdStringNRacent certificate ID. Please keep it properly; this parameter is the unique credential for the Racent instance.
vendorIdStringNCA order number.
vendorCertIdStringNCA certificate number.
DCVfileNameStringNFile validation filename
DCVfileContentStringNContent of the file validation file
DCVdnsHostStringNDNS validation host value
DCVdnsValueStringNDNS validation record value
DCVdnsTypeStringNDNS validation record type
DCVfilePathStringNPath of the file validation file
dcvInfoObjectNWhen the validation value for each domain name in the certificate request is different, this field is Y.
Each entry is of Object type, with the requested domain name as the object name, for example: racent.com. Details of each entry are as follows:
DCVfileNameStringNContent of the file for file-based validation
DCVfileContentStringNContent of the file for file-based validation
DCVdnsHostStringNHost value for DNS validation
DCVdnsValueStringNRecord value for DNS validation
DCVdnsTypeStringNRecord type for DNS validation
DCVfilePathStringNFile path for file-based validation