OV/EV certificate lifecycle

The OV/EV certificate lifecycle consists of these main steps:

• Prepare certificate request
• Submit certificate order
• (Optional) Cancel certificate order
• Complete domain control validation (DCV)
• Complete organization validation
• Check order status
• Download issued certificate

Once a certificate has been issued, you can perform any of these actions:

• Reissue a certificate
• Renew an order
• Revoke a certificate

Prepare certificate request

To construct your request body and submit an order request, you need to collect some key pieces of information:

• Domain names to secure with the certificate.
• Certificate signing request (CSR) generated on the server where the certificate will be installed.
• Validity period of the certificate (amount of time the certificate should be valid).
• DCV method to use when demonstrating control over the domains.
• The legal name and registration information for the Organization being validated.

Domain names

Once you’ve collected the domain names to secure with the certificate, enter them in one of two request body parameters:

Certificate signing request (CSR)

The CSR should be generated on the server where the certificate will be installed. Once generated, enter the PEM formatted CSR in the csr parameter of the request body. See Create a CSR (Certificate Signing Request) for additional information.

Validity periods

When you submit an order request, you set a validity period for the certificate and for the order. The validity period of the certificate determines when the certificate expires. The validity period of the order determines how long you can reissue the certificate without additional costs.

Order validity period

Use the order_validity object in your request body to customize the number of years or days the order is valid, or to set a custom expiration date for the order. Orders for Multi-year Plans can be valid for up to three years.

Order validity can be greater than certificate validity. If you do not specify a custom certificate validity period, we issue the certificate using the validity period of the order or the maximum certificate validity period defined in the CA/B Forum baseline requirements, whichever is shorter.

For example:

• order_validity.years
• order_validity.days
• order_validity.custom_expiration_date

...
  "order_validity": {
    "years": 1
  },
...

...
  "order_validity": {
    "days": 199
  },
...

...
  "order_validity": {
    "custom_expiration_date": "2026-12-26"
  },
...

(Optional) Certificate validity period

Use the optional certificate.cert_validity object in your request body to customize the number of years or days the certificate is valid, or to set a custom expiration date for the certificate.

For example:

• certificate.cert_validity.days
• certificate.cert_validity.custom_expiration_date

...
  "certificate": {
    ...
      "cert_validity": {
      "days": 199
    }
  },
...

...
  "certificate": {
    ...
      "cert_validity": {
      "custom_expiration_date": "2026-12-26"
    }
  },
...

Choose a DCV method

Email DCV is the default DCV method used for public TLS/SSL certificate orders. To use a different DCV method, it is recommended to include the dcv_method parameter in your order request. To check the DCV methods available to your account, see List DCV methods.

Use the table below to compare the available DCV methods and determine the right value for the dcv_method parameter:

Organization details

Each OV/EV certificate order must include information about the organization that will receive the certificate. Before DigiCert can issue the certificate, industry standards require us to validate the organization you include in the request. For more information about organization validation, see TLS certificate organization validation process.

Use the organization object in the body of your request to submit the details of an organization with your order. You can use this object to create a new organization, or you can associate the certificate with an organization that already exists in your account.

• To create a new organization, use the organization object to provide the name, address, and contact information for individuals associated with the organization. For details about the structure and required parameters of the organization object, see the documentation for the Create organization endpoint. This example shows the organization object for a request that creates a new organization:

  {
  ...
      "organization": {
          "name": "Epigyne Unwieldiness llc",
          "assumed_name": "Epigyne Unwieldiness",
          "country": "us",
          "address": "932 Prospect Street",
          "address2": "Floor 08",
          "city": "Minneapolis",
          "state": "Minnesota",
          "zip": "40849",
          "telephone": "666-186-6450",
          "container": {
              "id": 93288
          },
          "organization_contact": {
              "first_name": "Gia",
              "last_name": "Booth",
              "job_title": "Clinical Laboratory Technician",
              "email": "gia.booth@inbox.com",
              "telephone": "666-186-6450",
              "telephone_extension": "736"
          },
          "skip_duplicate_org_check": true
      },
  ...
  }
  

  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.

  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.

• To associate the request with an existing organization, pass the ID of the organization as the value of the organization.id parameter. To get ID values for organizations that already exist in your account, use the List organizations endpoint. This example shows the organization object from a request that associates the order with an existing organization:

  {
  ...
      "organization": {
          "id": 112236
      },
  ...
  }
  

(Optional) dcv_emails array

When using the email DCV method, it’s possible to specify the email addresses that should be used when sending the DCV emails. To do this, include the dcv_emails array in the request body and add an entry for each domain on the order.

Each email address specified in dcv_emails must be an allowed DCV email address for the domain: either a DNS-based contact address configured in a DNS TXT record at _validation-contactemail.[domain_name] or a DNS CAA record using the contactemail property, or one of the five constructed addresses: admin@[domain_name], administrator@[domain_name], webmaster@[domain_name], hostmaster@[domain_name], or postmaster@[domain_name]. DigiCert sends DCV emails only to the addresses specified for that domain.

For example, if john.doe@[domain_name] is configured as a DNS TXT or DNS CAA email contact for the domain, you can specify it in dcv_emails. If it is the only address specified for that domain, DigiCert sends the DCV email only to that address. Similarly, if you specify only admin@[domain_name], DigiCert sends the DCV email only to that address.

Example dcv_emails array

"dcv_emails": [
  { 
    "dns_name": "example.com",
    "email_domain": "example.com",
    "email": "hostname@example.com"
  },
  { 
    "dns_name": "my.example.com",
    "email_domain": "example.com",
    "email": "admin@example.com"
  },
  { 
    "dns_name": "another.example.com",
    "email_domain": "example.com",
    "email": "admin@example.com"
  }
]

(Optional) ICA selection

With ICA selection, you can choose which ICA certificate chain should issue your end-entity certificate.

To use ICA selection:

• ICA selection must be enabled for your account. To enable ICA selection, contact your account manager or the Support team. For more information, see ICA certificate chain option for public TLS certificates.
• You must know the ca_cert_id of the ICA that you want to issue your certificate. To find the ca_cert_id for an ICA certificate chain, use the Product list endpoint.

To select an ICA certificate chain, include the certificate.ca_cert_id parameter in your certificate request. The value of this parameter is the ID of the ICA certificate chain that should issue your end-entity certificate.

For example:

{
  "certificate": {
    "common_name": "example.test.com",
    "csr": {{csr}},
    "signature_hash": "sha256",
    "ca_cert_id": "4A7259E3E5D112A"
  },
  "order_validity": {
    "years": 1
  },
  "locale": "en",
  "skip_approval": true,
  "organization": {
    "id": {{organization_id}}
  },
  "payment_method": "profile"
}

Submit certificate order

After you collect the above information, you’re ready to construct your request body and submit your order request. To do this, submit a POST request to the order endpoint for the type of certificate you want to buy.

The following table lists the endpoints for ordering different OV/EV SSL products:

A successful POST to an order endpoint returns a 201 Created HTTP response code. The response body includes information that you can use to check the status of the order and to download the certificate when it is issued, including:

• id: The ID of the order in your account. Use this ID with the Order info endpoint to check the details of the order.
• certificate_id: The ID of the certificate. Use this ID to perform operations such as downloading or revoking the certificate.
• dcv_random_value: Random value used for dns-txt-token, dns-cname-token, and http-token DCV methods. Not used for persistent-txt, which uses a persistent URI. This random value expires after 30 days.

The example below shows the entire request and response bodies for a sample request to the Order OV/EV SSL endpoint:

Request OV/EV SSL certificate (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",
      "cert_validity": {
        "days": 199
      }
    },
    "order_validity": {
      "years": 1
    },
    "disable_renewal_notifications": true,
    "locale": "en",
    "skip_approval": true,
    "payment_method": "balance",
    "organization": {
      "id": 123456
    },
    "container": {
      "id": 93288
    },
    "custom_fields": [
      {
        "metadata_id": 11,
        "value": "Invoice #00001"
      }
    ]
  }'

• 201 Created (skip approval step, email DCV)
• 201 Created (skip approval step, dns-txt-token DCV)

{
  "id": 12345,
  "domains": [
    {
      "id": 12345,
      "name": "example.com",
      "dns_name": "example.com"
    },
    {
      "id": 12345,
      "name": "example.com",
      "dns_name": "sub.example.com"
    },
    {
      "id": 12345,
      "name": "example.com",
      "dns_name": "app.example.com"
    }
  ],
  "certificate_id": 123456
}

{
  "id": 12345,
  "dcv_random_value": {{token}},
  "domains": [
    {
      "id": 12345,
      "name": "example.com",
      "dns_name": "example.com",
      "dcv_token": {
        "token": {{token}},
        "status": "pending",
        "expiration_date": "2021-08-16T01:16:29+00:00"
      }
    },
    {
      "id": 12345,
      "name": "example.com",
      "dns_name": "sub.example.com"
      "dcv_token": {
        "token": {{token}},
        "status": "pending",
        "expiration_date": "2021-08-16T01:16:29+00:00"
    },
    {
      "id": 12345,
      "name": "example.com",
      "dns_name": "app.example.com"
      "dcv_token": {
        "token": {{token}},
        "status": "pending",
        "expiration_date": "2021-08-16T01:16:29+00:00"
    }
  ],
  "certificate_id": 123456
}

(Optional) Cancel certificate order

After placing an order, there may be times when you need to cancel it. To cancel an order, you need to change the status from pending to canceled. This is done with a PUT to the Update order status endpoint.

A successful PUT to this endpoint returns a 204 No Content HTTP response.

Cancel certificate order (cURL)

curl -X PUT \
  'https://www.digicert.com/services/v2/order/certificate/{{order_id}}/status' \
  -H 'Content-Type: application/json' \
  -H 'X-DC-DEVKEY: {{api_key}}' \
  -d '{
    "status": "CANCELED",
    "note": "Message about the cancellation."
}'

204 No Content (Order canceled)

// empty

Complete domain control validation (DCV)

After submitting the OV/EV certificate order, complete DCV for each domain on the order or any domain that does not have a current validation. The DCV method you selected when creating the order determines how you demonstrate control over each domain.

Complete DCV for the domain(s) that still require validation using the method selected when preparing the request. A domain with an active validation may not need another DCV check. To review a domain’s validation status, see Validation details.

For guidance on completing the domain control validation, see DCV Methods.

Choose a DCV method (email, DNS, or HTTP) and then complete validation by responding to the email, updating DNS records, or updating the host validation file accordingly. For the persistent-txt DCV method, keep the persistent DNS TXT record and URI in your domain’s DNS configuration so DigiCert can reuse them for future domain validations. Validating a domain using the email, dns-txt-token, dns-cname-token, or persistent-txt DCV method demonstrates control over the domain and its subdomains. Using only the file-based (http-token or http-token-dynamic) DCV method demonstrates control over the exact FQDN in your request.

Key DCV related tasks you can perform with CertCentral APIs:

• For viewing the available DCV methods for a domain, see List DCV methods.
• For checking DCV status, see Validation details.
• To retrieve the existing DCV random value or generate a replacement if it has expired, using the Order ID, see Generate DCV token.
• For generating a new random value for an individual domain using the Domain ID, see OV/EV SSL: Generate DCV token. To retrieve an existing random value instead of generating a new one, see Domain info endpoint.
• For completing http-token or http-token-dynamic DCV, see File-based domain control validation (http-token).
• For certificate renewals or reissuances, domain revalidation may be necessary if the prior validation period has lapsed. See Submit domain for validation.
• To resend an email validation request, use Resend DCV email with the domain ID.

Key DCV related tasks you can perform with the CertCentral UI:

• For completing DCV through the CertCentral UI, see Domain Control Validation using CertCentral platform documentation.

Perform DCV check

When you submit your certificate order, DigiCert automatically checks the domain for the required DCV information. For more information about automatic DCV polling, see Automatic domain control validation checks.

In addition to automatic DCV polling, you can perform a DCV check by calling the Check order DCV API endpoint, which also supports OV/EV orders. Alternatively, you can perform a DCV check from your CertCentral account by following these steps:

1. For each domain on the order, add the random value to the DNS TXT record (DNS TXT method), DNS CNAME record (DNS CNAME method), or to the fileauth.txt uploaded to the specified location (HTTP TXT DCV method).
2. Sign in to CertCentral.
3. Navigate to the Order Detail page for the new order.
4. In the Order status section of the page, click on each domain listed as pending DCV, and then click Check to have the DCV method checked and confirmed.

Organization validation

In addition to domain validation, all OV/EV orders also require organization validation. Once an order is submitted, DigiCert’s validation team will begin working on the OV/EV organization validation process.

Check validation status

You can check the current validation status for an organization with a GET to the Organization Validation details endpoint.

A successful GET to this endpoint returns a 200 OK HTTP response.

Check validation status (cURL)

curl -X GET \
  'https://www.digicert.com/services/v2/organization/{{organization_id}}/validation' \
  -H 'Content-Type: application/json' \
  -H 'X-DC-DEVKEY: {{api_key}}'

200 OK (Validation status)

{
  "validations": [
    {
      "type": "ov",
      "name": "OV",
      "description": "Normal Organization Validation",
      "status": "pending"
    },
    {
      "type": "ev",
      "name": "EV",
      "description": "Extended Organization Validation (EV)",
      "status": "pending",
      "verified_users": [
        {
          "id": 12,
          "first_name": "John",
          "last_name": "Smith"
        }
      ]
    }
  ]
}

Check order status

After submitting your order and completing the DCV for each domain, you’ll want to know when the order status changes and whether DigiCert has issued the certificate.

To check the status of your order, use the GET /order/certificate/{order_id} endpoint. Check the value of the Status response parameter to get the current status of the order. For more information about retrieving order information, see Order info. For more information about types of order status, see Glossary - Order Status.

The best way to determine when an order’s status changes is to send a GET request to the Status change list endpoint. A GET to this endpoint returns three possible responses:

• 200 OK (orders array): The orders array lists all orders that have changed status in the specified timeframe. When your order’s status changes from pending to issued, it will appear in the list. If multiple orders are returned, use either the order ID or certificate ID to locate the order.
• 200 OK (empty object): A response with an empty object ({}) means no orders have had a status change in the specified timeframe. Either increase the timeframe or wait to send another request.
• 400 Bad Request : A response with the time_frame_too_long error code means the timeframe specified in the URL query string exceeds the maximum value. Reduce the timeframe to a value less than 10080 minutes (7 days).

Check order status (cURL)

curl -X GET \
  'https://www.digicert.com/services/v2/order/certificate/status-changes?minutes=10' \
  -H 'Content-Type: application/json' \
  -H 'X-DC-DEVKEY: {{api_key}}'

• 200 OK (Order issued)
• 200 OK (No orders found)
• 400 Bad Request (Time frame too long)

{
  "orders": [
    {
      "order_id": 112233,
      "certificate_id": 123456,
      "status": "issued"
    }
  ]
}

{}

{
  "errors": [
    {
      "code": "time_frame_too_long",
      "message": "An error occurred while processing your request."
    }
  ]
}

Download certificate

Once the order status changes from pending to issued, your certificate is ready to be downloaded. Depending on your needs, you can use any of the following endpoints to download your certificate.

To download a certificate, use the GET /certificate/{certificate_id}/download/ endpoint after the certificate is issued. You can download certificates for a specific platform, in a supported format or by order ID.

For more information about downloading the certificate for a platform, see Download certificate for a platform.

For more information about downloading the certificate in a specific format, see Download certificate by format.

For more information about downloading the certificate based on the order ID, see Download certificate (order_id).

For more information about downloading the certificate using its order ID in a specific format, see Download certificate by format (order_id).

Reissue certificate

Reissuing a certificate allows you to add, remove, or swap domain names, update the CSR, or change the signature hash of a certificate without submitting a new order. Additionally, if a certificate expires before the end of an order, you can reissue the certificate to receive a new certificate with a new expiration date.

A reissued certificate has a new certificate ID but the same order ID. After a reissue is approved, a new certificate is issued and needs to be reinstalled.

When reissuing a certificate, you need to provide this information:

• Common name
• SANs (include both the current SANs in the dns_names parameter as well as any additional SANs to be secured)
• CSR (to get and reuse the current CSR, use the Request info endpoint)
• Server platform ID (options listed here)

Even if some of the above details are staying the same, you still need to include it in the reissue request.

The Reissue certificate endpoint accepts the following optional parameters:

• skip_approval: Allows the request to be immediately submitted for validation, bypassing the need to approve the reissue request.
• certificate.cert_validity (Multi-year Plans): Allows you to customize the validity period for the reissued certificate. For more information about the parameters in this object, see (Optional) Certificate validity period.

The following example shows the full request and response bodies for a request to the reissue certificate endpoint:

Reissue certificate (cURL)

curl -X POST \
  'https://www.digicert.com/services/v2/order/certificate/{{order_id}}/reissue' \
  -H 'Content-Type: application/json' \
  -H 'X-DC-DEVKEY: {{api_key}}' \
  -d '{
  "certificate": {
    "common_name": "example.com",
    "dns_names": [
        "sub.example.com"
    ],
    "csr": "<csr>",
    "server_platform": {
      "id": 2
    },
    "signature_hash": "sha256"
    "skip_approval": true
  }
}'

• 201 Created (Reissued, skip_approval)
• 201 Created (Reissue request created)

{
  "id": 112233,
  "dcv_random_value": {{token}},
  "certificate_id": 111112
}

{
  "id": 112233,
  "requests": [
    {
      "id": 332211
    }
  ]
}

After a reissue is complete, download the new certificate (see Download certificate).

You can get a complete reissue history for an order by using the List reissues endpoint.

Renew order

Renewing an order allows you to link a new order to an expiring order such that you can track the history of your certificates using CertCentral and the Services API. When you renew an order, you receive a new certificate and a new order ID.

To renew, send a request to the endpoint for the certificate you want to buy. Follow the instructions to prepare the certificate request, and include a value for one of the following parameters:

For example, a request to renew the order with ID 123456 looks like this:

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",
        "cert_validity": {
            "days": 199
        }
    },
    "order_validity": {
        "years": 1
    },
    "disable_renewal_notifications": true,
    "locale": "en",
    "renewal_of_order_id": 123456,
    "payment_method": "balance",
    "skip_approval": true,
    "organization": {
        "id": 123456
    },
    "custom_fields": [
        {
            "metadata_id": 11,
            "value": "Invoice #00001"
        }
    ]
}'

For renewal orders, the Order info response includes a true value for the is_renewal parameter. The value of the renewed_order_id parameter is the order ID for the previous order:

{
  "is_renewal": true,
  "renewed_order_id": 123456
}

After the status of the order renewal changes from pending to issued, you can download the new certificate (see Download certificate) and install it on your server. For more information about installing your certificate, see our SSL Certificate Installation Instructions & Tutorials page.

Revoke certificate

Once your order is issued, you can submit a revoke request if needed. You can revoke a certificate using one of two endpoints. Both endpoints use the same request body parameters.

• Revoke certificate – Use this endpoint to revoke a specific certificate using the certificate ID or serial number.
• Revoke order certificate – Use this endpoint to revoke all certificates associated with an order ID.

After submitting the request, an administrator must approve it before DigiCert can revoke the certificate.

To skip the approval step and submit the request directly to DigiCert for revocation, include "skip_approval": true in the body of your request. To skip the approval step, the API key must have admin privileges. See Authentication.

• Skip approval step (cURL)
• Create revocation request (cURL)
• Include revocation reason (cURL)

curl --request PUT 'https://www.digicert.com/services/v2/certificate/{{certificate_identifier}}/revoke' \
--header 'Content-Type: application/json' \
--header 'X-DC-DEVKEY: {{api_key}}' \
--data-raw '{
  "skip_approval": true
}'

curl --request PUT 'https://www.digicert.com/services/v2/certificate/{{certificate_identifier}}/revoke' \
--header 'Content-Type: application/json' \
--header 'X-DC-DEVKEY: {{api_key}}' \
--data-raw '{
  "comments": "I no longer need this certificate."
}'

curl --request PUT 'https://www.digicert.com/services/v2/certificate/{{certificate_identifier}}/revoke' \
--header 'Content-Type: application/json' \
--header 'X-DC-DEVKEY: {{api_key}}' \
--data-raw '{
  "revocation_reason": "superseded",
  "skip_approval": true
}'

• 204 No Content (Skip approval step)
• 201 Created (Create revocation request)

// empty

{
  "id": 1,
  "date": "2016-02-10T17:06:15+00:00",
  "type": "revoke",
  "status": "pending",
  "requester": {
    "id": 242140,
    "first_name": "Jack",
    "last_name": "White",
    "email": "j.white@fakeaddy.com"
  },
  "comments": "Revoked via API!"
}