Order OV/EV SSL

POST https://www.digicert.com/services/v2/order/certificate/{{ssl_certificate_id}}

Use this endpoint to request or renew an OV/EV SSL certificate. To renew a certificate, you must place the request from the same account used to order the original certificate.

Replace {{ssl_certificate_id}} in the URL with the product identifier for the type of certificate to order:

ssl_plus: Standard SSL Certificate
ssl_multi_domain: SSL Multi Domain Certificate
ssl_wildcard: Wildcard Certificate
ssl_ev_plus: EV SSL Certificate
ssl_ev_multi_domain: SSL EV Multi Domain Certificate
ssl_cloud_wildcard: SSL Cloud 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.

Warning

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.

Notice

Enterprise License Agreement (ELA) and Flat Fee contracts only support 1- and 2-year Multi-year Plans.

Notice

In addition to these products, DigiCert offers flexible certificates that support any type of domain configuration. You can order flexible OV and EV certificates with the Order Basic OV and Order Basic EV endpoints. To activate these certificates for your CertCentral account, contact your account manager or our Support team. For more information, see Flex certificates.

You can only order certificates that are enabled for your account. Use the Product list endpoint to get the list of products available for your account.

Example requests and responses

Example 1. cURL

curl -X POST \
  'https://www.digicert.com/services/v2/order/certificate/{{ssl_certificate_id}}' \
  -H 'Content-Type: application/json' \
  -H 'X-DC-DEVKEY: {{api_key}}' \
  -d '{
    "certificate": {
        "common_name": "example.com",
        "dns_names": [
            "sub.example.com",
            "app.example.com"
        ],
        "csr": "<csr>",
        "server_platform": {
            "id": 45
        },
        "signature_hash": "sha256"
    },
    "order_validity": {
      "years": 1
    },
    "disable_renewal_notifications": true,
    "locale": "en",
    "payment_method": "balance",
    "skip_approval": true,
    "organization": {
        "id": 123456
    },
    "custom_fields": [
        {
            "metadata_id": 11,
            "value": "Invoice #00001"
        }
    ]
}'

Example 2. Python

import requests

url = "https://www.digicert.com/services/v2/order/certificate/{{ssl_certificate_id}}"

payload = "{\n    \"certificate\": {\n        \"common_name\": \"example.com\",\n        \"dns_names\": [\n            \"sub.example.com\",\n            \"app.example.com\"\n        ],\n        \"csr\": \"<csr>\",\n        \"server_platform\": {\n            \"id\": 45\n        },\n        \"signature_hash\": \"sha256\"\n    },\n    \"order_validity\": {\n            \"years\": 1\n        },\n    \"disable_renewal_notifications\": true,\n    \"locale\": \"en\",\n    \"payment_method\": \"balance\",\n    \"skip_approval\": true,\n    \"organization\": {\n        \"id\": 123456\n    },\n    \"custom_fields\": [\n        {\n            \"metadata_id\": 11,\n            \"value\": \"Invoice #00001\"\n        }\n    ]\n}"
headers = {
    'X-DC-DEVKEY': "{{api_key}}",
    '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_certificate_id}}"

	payload := strings.NewReader("{\n    \"certificate\": {\n        \"common_name\": \"example.com\",\n        \"dns_names\": [\n            \"sub.example.com\",\n            \"app.example.com\"\n        ],\n        \"csr\": \"<csr>\",\n        \"server_platform\": {\n            \"id\": 45\n        },\n        \"signature_hash\": \"sha256\",\n    },\n    \"order_validity\": {\n            \"years\": 1\n        },\n    \"disable_renewal_notifications\": true,\n   \"locale\": \"en\",\n    \"payment_method\": \"balance\",\n    \"skip_approval\": true,\n    \"organization\": {\n        \"id\": 123456\n    },\n    \"custom_fields\": [\n        {\n            \"metadata_id\": 11,\n            \"value\": \"Invoice #00001\"\n        }\n    ]\n}")

	req, _ := http.NewRequest("POST", url, payload)

	req.Header.Add("X-DC-DEVKEY", "{{api_key}}")
	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_certificate_id}}',
  headers: 
   { 'Content-Type': 'application/json',
     'X-DC-DEVKEY': '{{api_key}}' },
  body: 
   { certificate: 
      { common_name: 'example.com',
        dns_names: [ 'sub.example.com', 'app.example.com' ],
        csr: '<csr>',
        server_platform: { id: 45 },
        signature_hash: 'sha256' },
     order_validity: { years: 1 },
     disable_renewal_notifications: true,
     locale: 'en',
     payment_method: 'balance',
     skip_approval: true,
     organization: { id: 123456 },
     custom_fields: [ { metadata_id: 11, value: 'Invoice #00001' } ] },
  json: true };

request(options, function (error, response, body) {
  if (error) throw new Error(error);

  console.log(body);
});

Example 5. 201 Created (one-step)

{
  "id": 112233,
  "requests": [
    {
      "id": 113,
      "status": "pending"
    }
  ]
}

Example 6. 201 Created (two-step)

{
  "id": 112233,
  "requests": [
    {
      "id": 113,
      "status": "submitted"
    }
  ]
}

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,
  "certificate_id": 113,
  "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_chain": [
    {
      "subject_common_name": "example.com",
      "pem": "<pem_certificate>"
    },
    {
      "subject_common_name": "DigiCert SHA2 Secure Server CA",
      "pem": "<pem_certificate>"
    },
    {
      "subject_common_name": "DigiCert Global Root CA",
      "pem": "<pem_certificate>"
    }
  ]
}

Request parameters

Notice

For information about allowed values for certificate fields, see Publicly Trusted Certificates – Data Entries that Violate Industry Standards.

Name	Req/Opt	Type	Description
certificate	required	object	Certificate details.
.. common_name	required	string	Domain to be secured.
.. dns_names	optional	array	Additional domains to be secured. Can result in additional costs. (See Best practices – Get both versions of a domain for free.)
.. csr	required	string	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.
.. signature_hash	required	string	Hash algorithm used to sign the certificate.
.. organization_units	optional	array	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	optional	object	Server platform type. Default:`-1` (other)
.. .. id	required	int	Server platform ID. See Glossary – Server platforms.
.. cert_validity	optional	object	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.
.. .. years	optional	int	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`
.. .. days	optional	int	Number of days the certificate is valid after it is issued. Overrides `cert_validity.years`. Max: `397`
.. .. custom_expiration_date	optional	string	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.
.. profile_option	optional	string	If using custom certificate profiles, specify the profile name. Allowed values: See Glossary – Certificate profile options.
renewed_thumbprint	optional^*	string	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.
order_validity	required	object	Defines the validity period of the order. Order validity determines the length of a Multi-year Plan.
.. years	required^*	int	Number of years the order is valid. ^Can be replaced by `order_validity.days` or `order_validity.custom_expiration_date`. Range*: `1`-`3`
.. days	optional	int	Number of days the order is valid. Overrides `order_validity.years`. Max: `1095`
.. custom_expiration_date	optional	string	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.
validity_years	optional	int	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. Can be replaced by `validity_days` or `custom_expiration_date`. Range: `1`-`3`
validity_days	optional	int	Number of days the order is valid. 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. Max: `1095`
custom_expiration_date	optional	string	Custom expiration date for the order. Overrides `validity_days` and `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	optional	string	Comments about the order for the administrator or approver 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`.
apply_cr_discount	optional	bool	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	optional	string	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.
auto_renew	optional	int	Specify if the certificate should automatically renew. Allowed values:`0` (disabled) or `1` (enabled) Default: `0`
auto_reissue	optional	int	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: The product does not support Multi-year Plans. Multi-year Plans are disabled for the account.
custom_renewal_message	optional	string	Custom message to be included in renewal notifications.
disable_renewal_notifications	optional	bool	Specify if renewal notification emails should be disabled. Default: `false`
additional_emails	optional	array	Additional email addresses to receive certificate notification emails (e.g., certificate issuance, duplicate certificate, certificate renewals, etc.).
renewal_of_order_id	optional^*	int	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	optional	string	Payment method for the order. Allowed values: `balance` (default): Pay with account balance. Returns an error if the option to bill to account balance is disabled for the account, or if the account balance has insufficient funds. Learn how to debit purchases against your CertCentral account balance. `profile`: Pay with the account’s default credit card. Returns an error if no default credit card is configured for the account. Learn how to set up a default credit card. `card`: Pay with a new credit card. Requests that use `card` as the payment method must include a `credit_card` and `billing_address` object. Returns an error if the option to pay with a credit card is disabled for the account.
credit_card	conditional	object	Object with information about the credit card charged for the order. Required if `payment_method` is `card`.
.. number	required	string	Credit card number.
.. expiration_month	required	integer	Credit card expiration month. Format as a two-digit number between `01` (Jan) and `12` (Dec).
.. expiration_year	required	integer	Credit card expiration year. Format as a four-digit number. For example: `2026`
.. cvv	required	integer	Card verification value (CVV). Format as a three- or four-digit number. For example: `333` or `4444`
.. cardholder_name	required	string	Cardholder’s first and last name.
billing_address	conditional	object	Object with information about the billing address. Required if `payment_method` is `card`.
.. address	required	string	Billing street address.
.. address2	optional	string	Continuation of street address.
.. city	required	string	Billing city.
.. state	conditional	string	Billing state or province. Optional for some countries.
.. country	required	string	Billing country.
.. zip	conditional	string	Billing zip or postal code. Optional for some countries.
vat_number	optional	string	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 DigiCert only stores a VAT/GST number for credit card transactions. For orders using other payment methods, the `vat_number` request parameter is ignored. VAT/GST numbers are not supported for DigiCert USA and DigiCert Japan billing entities. If the billing entity for the account is DigiCert, Inc. (US) or DigiCert Japan G.K. (Japan), the `vat_number` parameter is ignored, and DigiCert doesn't store a VAT/GST number for the transaction. To learn more about your account's billing entity, contact your account manager.
dcv_method	optional	string	DCV method to use when verifying domain control. See Glossary – DCV methods.
skip_approval	optional	bool	Specify if the order should skip the approval step and be immediately submitted for validation and issued when complete. Default: `false`
disable_ct	optional	bool	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	optional	object	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.
.. first_name	required	string	Contact first name.
.. last_name	required	string	Contact last name.
.. email	required	string	Contact email address.
.. job_title	optional	string	Contact job title.
.. telephone	optional	string	Contact telephone number.
.. telephone_extension	optional	string	Telephone extension.
technical_contact	optional	object	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.
.. first_name	required	string	Contact first name.
.. last_name	required	string	Contact last name.
.. email	required	string	Contact email address.
.. job_title	optional	string	Contact job title.
.. telephone	optional	string	Contact telephone number.
.. telephone_extension	optional	string	Telephone extension.
organization	required	object	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. If we find one matching organization, we automatically associate the order with that organization instead of creating a new one. If we find two or more matching organizations, we automatically associate the order with the oldest matching organization in your account instead of creating a new one. 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.
.. id	required^*	int	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.
.. skip_duplicate_org_check	optional	bool	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`
.. contacts	conditional	array	List of contacts for the organization. When creating a new organization: For EV TLS certificates, providing a `verified_contact` is required. Providing an `organization_contact` is conditional. An `organization_contact` is required if the request is from a service user. If omitted, the organization is created and the authenticated user is used as the organization contact. Providing a `technical_contact` is optional. If omitted, the organization is created with no technical contact. When using an existing organization ID: Providing an `organization_contact` and `technical_contact` is optional. If provided, the new organization and technical contact replace the existing contacts stored on the organization. For EV TLS certificates, providing a `verified_contact` is optional if the organization has already been submitted for EV validation. For EV TLS certificates, providing a `verified_contact` is required if the organization has never been submitted for EV validation. 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 at the root of the request payload.
.. .. contact_type	required	string	Contact type. Allowed values:`organization_contact`, `technical_contact`, `verified_contact` (formerly `ev_approver`^) ^Note: To identify a verified contact for the organization, use `verified_contact` instead of `ev_approver`. While the API still accepts order requests that use `ev_approver` to identify verified contacts, `ev_approver` is a legacy label chosen when the only DigiCert products that required verified contacts were EV TLS/SSL certificates. Both contact type labels (`verified_contact` and `ev_approver`) have the same meaning, but `verified_contact` uses generalized terminology applicable to every product that requires a verified contact.
.. .. user_id	required^*	int	ID of existing user or contact for the account. ^*Can be omitted if adding a new contact.
.. .. first_name	optional	string	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	optional	string	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	optional	string	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	optional	string	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	optional	string	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.
container	optional	object	If needed, specify the container the order should be placed under.
.. id	required	int	Container ID.
custom_fields	optional^*	array	Account-specific custom fields. ^*Whether or not these fields are required depends on your custom field settings.
.. metadata_id	required	int	Custom field ID.
.. value	required	string	Value for the custom field. Data validation type depends on your custom field settings.
alternative_order_id	optional	string	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.
enable_guest_access	optional	int	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.
certificate_dcv_scope	optional	string	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: `base_domain`: Validate each domain and subdomain in the request at the base domain level (for example, example.com). `fqdn`: Validate each domain and subdomain included in the order exactly as named in the request. When using `fqdn`: If a domain is a subdomain of another domain included on the order, complete the DCV check for the higher-level domain. For OV and EV certificates only, if a higher-level domain exists in the account with an active validation, we validate the domain under the scope of the existing domain. Default: This parameter overrides the domain validation scope settings for your CertCentral account. If you omit this parameter, the account setting is used.

Response parameters

Name	Type	Description
id	int	Order ID.
dcv_random_value	string	Random value used for domain control validation (DCV). Only returned when using `dns-txt-token`, `dns-cname-token`, or `http-token` as the DCV method.
organization	object	Container for new organization details. Only returned if a new organization was created with the order.
.. id	int	Organization ID for the new organization.
domains	array	List of objects with details about the domains that are submitted for validation with the certificate order request. You must validate these domains to prove you control the common name and each SAN on the order.
.. id	int	Domain ID of the domain in your account.
.. name	int	Name of the domain in your account.
.. dns_name	string	Common name or SAN on the order. To prove you control this common name or SAN, you must validate the domain associated with the `domains[].name` and `domains[].id` key/value pairs.
.. dcv_token	object	Object with details about the DCV random value. Each domain returns the same order random value, and you can use this value to complete the DCV check for any domain submitted for validation with the order. Only returned when using a DCV method of `dns-txt-token`, `dns-cname-token`, or `http-token`.
.. .. token	string	DCV random value.
.. .. status	string	Status of the domain validation process.
.. .. expiration_date	string	Timestamp of when the token will expire. Format: UTC timezone and ISO 8601 date
.. .. verification_value	string	Value for the DNS record target host field. Only returned if the DCV method is `dns-cname-token`.
.. .. http_token_url	string	Filename and location for the .txt file. Only returned if the DCV method is `http-token`.
requests	array	Contains information about the request.
.. id	int	Request ID.
.. status	string	Request status. Possible values: `pending`, `submitted`, `approved`, `rejected`
certificate_id	int	Certificate ID. Returned if request status is `approved`.
certificate_chain	array	Ordered list of objects with information about each certificate in the certificate chain (for example, SSL certificate, intermediate CA certificate, and root certificate). The first object in the array contains the end-entity certificate. The next objects contain the intermediate CA certificates. The final object contains the root certificate. Each certificate is signed by the certificate in the object that follows it. For example, the end-entity certificate is signed by the intermediate CA certificate. Note: This endpoint only returns the `certificate_chain` array for TLS certificates that DigiCert issues immediately. To get the certificate chain after DigiCert issues a certificate, use the Certificate chain endpoint.
.. subject_common_name	string	Common name on the certificate.
.. pem	string	PEM-encoded certificate data. Note: The `pem` response parameter includes newline characters `\r\n`, which are an inherent part of PEM-encoded certificates.

In this section: