Use this endpoint to request or renew a Basic OV SSL certificate. To renew a certificate, you must place the request from the same account used to order the original certificate.
Public TLS/SSL certificates support Multi-year Plans. With Multi-year Plans, you pick the SSL/TLS certificate, the certificate validity period, and the duration of coverage you want. To order a Multi-year Plan with this endpoint, use the order_validity object to set the validity period of the order (up to three years). Optionally, use the certificate.cert_validity parameter to customize the validity of the first certificate issued for the order. For more information, see Multi-year Plans.
End of 4- to 6-year Multi-year Plans
On October 31, 2023 , DigiCert will no longer sell 4- to 6-year Multi-year Plans for TLS and VMC certificates. We will continue to offer 1, 2, and 3-year Multi-year Plans. For more information, see End of 4- to 6-year Multi-year Plans.
Enterprise License Agreement (ELA) and Flat Fee contracts only support 1- and 2-year Multi-year Plans.
This more flexible Basic OV SSL certificate makes it easier to get the Basic OV certificate to fit your needs. This certificate replaces the Basic Standard SSL, SSL Multi Domain, and Wildcard products.
curl -X POST \ https://www.digicert.com/services/v2/order/certificate/ssl_basic \ -H 'Content-Type: application/json' \ -H 'X-DC-DEVKEY: >' \ -d '< "certificate": < "common_name": "example.com", "dns_names": [ "sub.example.com", "app.example.com" ], "csr": "", "signature_hash": "sha256", "server_platform": < "id": 2 >>, "comments": "Certificate for app server.", "container": < "id": 334455 >, "auto_renew": 1, "custom_renewal_message": "Keep this renewed.", "organization": < "id": 123456, "contacts": [ < "contact_type": "organization_contact", "user_id": 565611 >, < "contact_type": "technical_contact", "first_name": "Jill", "last_name": "Valentine", "job_title": "STAR Member", "telephone": "8017019600", "email": "jill.valentine@digicert.com" >] >, "order_validity": < "years": 1 >, "payment_method": "balance" >'Example 2 . Python
import requests url = "https://www.digicert.com/services/v2/order/certificate/ssl_basic" payload = "\",\n \"signature_hash\": \"sha256\",\n \"server_platform\": \n >,\n \"comments\": \"Certificate for app server.\",\n \"container\": ,\n \"auto_renew\": 1,\n \"custom_renewal_message\": \"Keep this renewed.\",\n \"organization\": ,\n ,\n \n ]\n >,\n \"order_validity\": ,\n \"payment_method\": \"balance\"\n>" headers = < 'X-DC-DEVKEY': ">", 'Content-Type': "application/json" > response = requests.request("POST", url, data=payload, headers=headers) print(response.text)
Example 3 . Go
package main import ( "fmt" "strings" "net/http" "io/ioutil" ) func main() < url := "https://www.digicert.com/services/v2/order/certificate/ssl_basic" payload := strings.NewReader("\",\n \"signature_hash\": \"sha256\",\n \"server_platform\": \n >,\n \"comments\": \"Certificate for app server.\",\n \"container\": ,\n \"auto_renew\": 1,\n \"custom_renewal_message\": \"Keep this renewed.\",\n \"organization\": ,\n ,\n \n ]\n >,\n \"order_validity\": ,\n \"payment_method\": \"balance\"\n>") req, _ := http.NewRequest("POST", url, payload) req.Header.Add("X-DC-DEVKEY", ">") req.Header.Add("Content-Type", "application/json") res, _ := http.DefaultClient.Do(req) defer res.Body.Close() body, _ := ioutil.ReadAll(res.Body) fmt.Println(res) fmt.Println(string(body)) >
Example 4 . NodeJS
var request = require("request"); var options = < method: 'POST', url: 'https://www.digicert.com/services/v2/order/certificate/ssl_basic', headers: < 'Content-Type': 'application/json', 'X-DC-DEVKEY': '>' >, body: < certificate: < common_name: 'example.com', dns_names: [ 'example2.com', 'example3.com' ], csr: '', signature_hash: 'sha256', server_platform: < id: 45 >>, comments: 'Certificate for app server.', container: < id: 334455 >, auto_renew: 1, custom_renewal_message: 'Keep this renewed.', organization: < id: 123456, contacts: [ < contact_type: 'organization_contact', user_id: 565611 >, < contact_type: 'technical_contact', user_id: 565615 >, < contact_type: 'ev_approver', first_name: 'Jill', last_name: 'Valentine', job_title: 'STAR Member', telephone: '8017019600', email: 'jill.valentine@digicert.com' >] >, order_validity: < years: 1 >, payment_method: 'balance' >, json: true >; request(options, function (error, response, body) < if (error) throw new Error(error); console.log(body); >);
Example 5 . 201 Created (one-step)
Example 6 . 201 Created (two-step)
Example 7 . 201 Created (auto)
< "id": 112233, "requests": [ < "id": 113, "status": "approved" >], "domains": [ < "id": 1469, "name": "example.com", "dns_name": "example.com" >, < "id": 1469, "name": "example.com", "dns_name": "sub.example.com" >, < "id": 1469, "name": "example.com", "dns_name": "app.example.com" >], "certificate_id": 113 >Example 8 . 201 Created (skip)
< "id": 112233, "domains": [ < "id": 1469, "name": "example.com", "dns_name": "example.com" >, < "id": 1469, "name": "example.com", "dns_name": "sub.example.com" >, < "id": 1469, "name": "example.com", "dns_name": "app.example.com" >], "certificate_id": 113 >Example 9 . 201 Created (immediate)
< "id": 112233, "domains": [ < "id": 1469, "name": "example.com", "dns_name": "example.com" >, < "id": 1469, "name": "example.com", "dns_name": "sub.example.com" >, < "id": 1469, "name": "example.com", "dns_name": "app.example.com" >], "certificate_id": 113, "certificate_chain": [ < "subject_common_name": "example.com", "pem": "" >, < "subject_common_name": "DigiCert SHA2 Secure Server CA", "pem": "" >, < "subject_common_name": "DigiCert Global Root CA", "pem": "" > ] >
Domain to be secured.
Additional domains to be secured. Can result in additional costs. (See Best practices – Get both versions of a domain for free.)
Certificate signing request (CSR).
Note: The Services API does not extract information from the CSR to fill in the details of a certificate request. You must provide values for all relevant request parameters, including certificate.common_name , certificate.dns_names , and organization.id . If you are requesting a certificate for an organization without an existing ID, you must provide values for all required parameters of the organization object.
Hash algorithm used to signing the certificate.
Note: Code signing certificates support only SHA-256.
Department in your organization the certificate is for.
Deprecated . This field is ignored for public TLS/SSL certificate requests. See our knowledge base article.
Server platform type.
Default: -1 (other)
Defines the validity period of certificates issued for this order. Cannot exceed order validity period.
If not provided, or if the cert_validity date is less than 365 days from the current date, the certificate's validity period defaults to the validity period of the order or the maximum certificate validity period defined by CA/B Forum baseline requirements, whichever is shorter.
This object is not used for requests from accounts that do not have Multi-year Plans enabled.
Number of years the certificate is valid after it is issued.
Can be replaced with cert_validity.days or cert_validity.custom_expiration_date .
Allowed value : 1
Number of days the certificate is valid after it is issued. Overrides cert_validity.years .
Max : 397
A custom expiration date for the certificate. Overrides cert_validity.days and cert_validity.years .
Format : dd MMM YYYY (for example, "09 JUN 2021" )
Range : Must be within 397 days of the date you request the certificate.
If using custom certificate profiles, specify the profile name.
ID of the intermediate certificate authority (ICA) certificate to select as the issuing certificate. To get the ca_cert_id value for an ICA, use the Product list endpoint.
Account administrators can customize the default and allowed ICAs for each product at the container or user role level. If you do not provide a value for this parameter, we issue the certificate using the default ICA. If you provide the ca_cert_id value for an ICA that is not allowed, the request returns an error * . To see the custom ICA settings for each product, use the Product limits endpoint.
* This parameter is ignored if the option for ICA selection is not enabled for your account. Learn more about the ICA certificate chain feature for your public TLS certificates.
If order is a renewal, enter the SHA-1 thumbprint of the previous order's primary certificate. For more information, see How to check a certificate's thumbprint.
* Renewal orders must include either a renewed_thumbprint or renewal_of_order_id value.
Defines the validity period of the order. Order validity determines the length of a Multi-year Plan.
Number of years the order is valid.
* Can be replaced by order_validity.days or order_validity.custom_expiration_date .
Range : 1 - 3
Number of days the order is valid. Overrides order_validity.years .
Max : 1095
Custom expiration date for the order. Overrides order_validity.days and order_validity.years .
Format : dd MMM YYYY (for example, "09 JUN 2025" )
Range : Must be within three years of the date you request the order.
Number of years the order is valid.
Deprecated . Use the order_validity object to set the validity period of the order. Use the cert_validity object to set the validity period of the certificate.
Range : 1 - 3
Custom expiration date for the order. Overrides validity_years .
Deprecated . Use the order_validity object to set the validity period of the order. Use the cert_validity object to set the validity period of the certificate.
Format : yyyy-MM-dd
Range : Must be within three years of the date you request the order.
Comments about the order for the administrator reviewing the order request. The comments value is stored on the order request . If the order skips the approval step ( skip_approval is set to true ), any provided comments value is ignored since CertCentral creates the order directly without creating a corresponding request .
When true , applies any competitive replacement discounts that are available for the domains on the order. To calculate competitive replacement discounts before you place an order, use the List replacement benefits endpoint.
Default : false
Serial number of the non-DigiCert certificate for which you expect to receive a competitive replacement discount when you place the order. If not provided, we use the information from your order request to look for a match among certificates on the CT log servers, and we apply a discount based on the best match we can find.
Specify if the certificate should automatically renew.
Allowed values: 0 (disabled), 1 (enabled)
Default: 0
Auto-reissue setting for the order. When auto-reissue is enabled for a Multi-year Plan, DigiCert automatically creates a reissue request for the most recently issued certificate when that certificate is within 30 days of expiring. Auto-reissue repeats until the order expires. To learn more about reissuing certificates in a Multi-year Plan, see Multi-year Plans.
Allowed values: 0 (disabled) or 1 (enabled)
Default: 0 (disabled)
Note: We ignore the auto_reissue request parameter if:
Custom message to be included in renewal notifications.
Specify if renewal notification emails should be disabled.
Default: false
Additional email addresses to receive certificate notification emails (e.g., certificate issuance, duplicate certificate, certificate renewals, etc.).
Language that the DCV email should use. See Glossary – Locale codes.
If order is a renewal, enter the previous order's ID.
* Renewal orders must include either a renewed_thumbprint or renewal_of_order_id value.
Payment method for the order. Allowed values:
Object with information about the credit card charged for the order. Required if payment_method is card .
Credit card number.
Credit card expiration month. Format as a two-digit number between 01 (Jan) and 12 (Dec).
Credit card expiration year. Format as a four-digit number. For example: 2026
Card verification value (CVV). Format as a three- or four-digit number. For example: 333 or 4444
Cardholder’s first and last name.
Object with information about the billing address. Required if payment_method is card .
Billing street address.
Continuation of street address.
Billing state or province. Optional for some countries.
Billing zip or postal code. Optional for some countries.
If the payment method is card (new credit card) or profile (default credit card), use the vat_number request parameter to set a value-added tax (VAT) or goods and services tax (GST) identification number for the order transaction. DigiCert includes this number on the transaction receipt as a reference for your financial records.
If omitted, DigiCert uses the VAT/GST number from the finance settings for the CertCentral account. If the VAT/GST number is absent from both the order request and account settings, DigiCert doesn't store a VAT/GST number for the transaction.
Note
DCV method to use when verifying domain control. See Glossary – DCV methods.
Specify if the order should skip the approval step and be immediately submitted for validation and issued when complete.
Default: false
Specify if CT logging for the certificate should be disabled. Order-specific CT logging must be enabled or this will be ignored. See Allow users to keep certificates out of CT logs .
Default: false
Organization contact for the order.
Include this object at the root of the request body to create the order with a different organization contact than the one assigned to the organization on the request. If omitted, the order uses the same organization contact assigned to the organization .
Note: The order-level organization_contact is only used on the order. It does not replace the organization contact assigned to the organization on the request.
Contact first name.
Contact last name.
Contact email address.
Contact job title.
Contact telephone number.
Technical contact for the order.
Include this object at the root of the request body to create the order with a different technical contact than the one assigned to the organization on the request. If omitted, the order uses the same technical contact assigned to the organization .
Note: The order-level technical_contact is only used on the order. It does not replace the technical contact assigned to the organization on the request.
Contact first name.
Contact last name.
Contact email address.
Contact job title.
Contact telephone number.
Object with information about the organization to associate with the request. You can associate the request with an existing organization, or you can create a new organization when you submit the order request.
To associate the request with an existing organization, pass the ID of the organization as the value of organization.id in the body of your request. To create a new organization, include the details of the organization in the organization object. For more information about the structure and required parameters of the organization object, see the Create organization documentation.
Note : When you submit an order with organization details instead of providing an organization ID, we check the organizations that already exist in your account to avoid creating a duplicate.
To override this behavior and force the request to create a new organization, set the organization.skip_duplicate_org_check parameter to true in the body of your request.
Important : When you want to associate an order with an existing organization, we recommend always using the ID of the organization instead of the organization's details in the body of your request. To get the ID values for organizations in your account, use the List organizations endpoint. Additionally, we recommend deactivating unused organizations to ensure they are never accidentally assigned to a new order request. To deactivate an organization, use the Deactivate organization endpoint.
The ID of an existing organization to associate with the order. To get the ID of organizations in your account, use the List organizations endpoint.
* Not required if you are creating a new organization with your request.
Use true to skip the check for duplicate organizations in your account. When you skip this check, you force the request to create a new organization, regardless of whether the details you provide in the request match the details of an organization that already exists in your account.
Default : false
List of contacts for the organization.
When creating a new organization:
When using an existing organization ID:
Note: By default, DigiCert creates the order with the organization contact and technical contact (if one exists) assigned to the organization on the request. To create the order with a different organization or technical contact than those assigned to the organization , include the organization_contact or technical_contact object the root of the request payload.
Allowed values: organization_contact , technical_contact
ID of existing user or contact for the account.
* Can be omitted if adding a new contact.
First name of the new contact.
Note: Required when omitting user_id . If user_id is not omitted, the specified user's information will be updated with the new value.
Last name of the new contact.
Note: Required when omitting user_id . If user_id is not omitted, the specified user's information will be updated with the new value.
Job title of the new contact.
Note: Required when omitting user_id . If user_id is not omitted, the specified user's information will be updated with the new value.
Telephone number of the new contact.
Note: Required when omitting user_id . If user_id is not omitted, the specified user's information will be updated with the new value.
Email address of the new contact.
Note: Required when omitting user_id . If user_id is not omitted, the specified user's information will be updated with the new value.
If needed, specify the container the order should be placed under.
Account-specific custom fields.
* Whether or not these fields are required depends on your custom field settings.
Custom field ID.
Value for the custom field. Data validation type depends on your custom field settings.
A custom alphanumeric ID to assign the order. To see the alternative_order_id assigned to an order, use the Order info endpoint.
Alternative order IDs do not replace the unique order ID that DigiCert assigns each order request. You cannot use alternative order IDs to search for or identify orders in API calls that require an order_id parameter in the URL path or request body.
If the Require unique alternative order IDs option is enabled in your account settings, you cannot submit order requests with an alternative order ID that is already assigned to an order in your account. Use this feature to enable nonce order requests, or to prevent your integration from creating duplicate orders in cases where you do not receive a response from the API. Account administrators can toggle this option from the CertCentral console. From the Settings > Preferences page, open the Advanced Settings menu, and look for the Alternative order ID option.
This parameter is always optional, even if the Require unique alternative order IDs option is enabled in your account. If a request does not use this parameter, no alternative_order_id value is assigned to the order.
Maximum length : 64 characters
Note : The Require unique alternative order IDs option may not appear in the advanced settings menu for all CertCentral accounts. To enable this option for your account, contact your account manager or our Support team.
Whether to enable guest access for the order. This parameter is not allowed if guest access is disabled in your account settings.
Allowed values: 1 (enabled) or 0 (disabled)
Default: The default configuration for new orders is determined by your account settings. Account administrators can change these settings from the Guest Access page in the CertCentral console.
Domain validation scope for domains on the order. Domain validation scope determines the specific domains that you must validate before DigiCert can issue your certificate.
Allowed values:
Default: This parameter overrides the domain validation scope settings for your CertCentral account. If you omit this parameter, the account setting is used.