Filtro por: API documentation x borrar

CertCentral Orders page: Improved load times

In CertCentral, we updated the Orders page to improve load times for those managing high volumes of certificate orders. The next time you visit the Orders page, it will open much quicker (in the left main menu go to Certificates > Orders).

To improve load times, we changed the way we filter your certificate orders upon initial page view. Previously, we filtered the page to show only Active certificate orders. However, this was problematic for those with high volumes of certificate orders. The more orders you have in your account, the longer the Orders page took to open.

Now, when you visit the page, we return all your certificates, unfiltered, in descending order with the most recently created certificate orders appearing first in the list. To see only your active certificates, in the Status dropdown, select Active and click Go.


CertCentral Services API: Purchase units for subaccounts and view unit orders

In the CertCentral Services API, we've added new endpoints for purchasing units and viewing unit orders. Now, if you manage subaccounts that use units as the payment method for certificate requests, you can use the Services API to buy more units for a subaccount and to get information about your unit order history.

For more information, see the reference documentation for the new endpoints:


CertCentral Services API: Documentation updates

We're pleased to announce the following updates to the documentation for the CertCentral Services API:

  • New Voucher price estimate API
    We published a new reference topic for the Voucher price estimate endpoint. Customers who use vouchers can use this endpoint to estimate the cost (including tax) of an order for specific voucher configurations.
  • Updated API Glossary
    We updated the Glossary with a new table to define the different organization validation status values. See Glossary – Organization validation statuses.
  • Added request parameter to Update account emails documentation
    We added the emergency_emails request parameter to the documentation for the Update account emails endpoint. Use this parameter to update the email addresses that receive emergency notifications from DigiCert.

Example Update account emails request body:

  • Added response parameters to the Product info documentation
    We added the validation_type, allowed_ca_certs, and default_intermediate response parameters to the documentation for the Product info endpoint.
    • Use the validation_type parameter to get the validation type for a given product.
    • Use the allowed_ca_certs parameter to get information about the ICA certificates you can select when you order a given product. *
    • Use the default_intermediate parameter to get the ID of the default ICA for a given product. *

Example Product info response data:

Product info response.png

* Note: The Product info endpoint only returns the allowed_ca_certs and default_intermediates parameters for products that support ICA selection. For public SSL certificates that support ICA selection (OV and EV flex certificates), these parameters are only returned if ICA selection is enabled for the account. Additionally, the default_intermediates parameter is only returned if an administrator has customized a product setting for a division or user role in the account. For more information, see ICA certificate chain option for public OV and EV flex certificates.


CertCentral Services API: Documentation updates

We added a new request parameter to the CertCentral Services API documentation for DV certificate orders: use_auth_key. In accounts with an existing AuthKey, this parameter allows you to choose whether to check your DNS records for an AuthKey request token when you place a DV certificate order.

By default, if an AuthKey exists for your account, you must add an AuthKey request token to your DNS records before ordering a DV certificate. AuthKey request tokens enable immediate certificate issuance, decreasing the time you spend on certificate lifecycle management. However, there may be times you need to verify control over domains using email validation or a DigiCert generated token. In these cases, the use_auth_key parameter allows you to disable the check for an AuthKey request token at the order level, so you can use another method to prove control over the domain. For more information about domain control validation (DCV), see Domain control validation (DCV) methods.

To disable the AuthKey verification method for a DV certificate order, include the use_auth_key parameter in the JSON payload of the request. For example:

use_auth_key sample

The following endpoints support the use_auth_key parameter:

For information about using an AuthKey for immediate DV certificate issuance, see DV certificate immediate issuance.

Note: The use_auth_key parameter is ignored in requests for Encryption Everywhere DV certificates. All requests for Encryption Everywhere DV certificates require an AuthKey request token for DCV. Additionally, OV and EV SSL products do not support the use_auth_key request parameter.