Skip to main content

Services API

The DigiCert Services API is a powerful API that allows you to automate typical certificate processes to save time and streamline certificate management. The Services API uses modern RESTful conventions and is simple to use.

Why use it?

  • Access all the features available in CertCentral without needing to log in to the platform.

  • Customize and automate virtually any workflow within the certificate management platform.

  • Create your own version of the platform with your organization's branding.

  • Seamlessly integrate with your existing tools.

Base URL

To construct API requests, use the base URL for your CertCentral instance .


Most accounts use the US instance of CertCentral. If your account uses the Europe instance, your CertCentral console displays CertCentral Europe in the top left corner.

CertCentral instance

Base URL

CertCentral US

CertCentral Europe

URL query strings

Some endpoints use URL query strings to filter results. URL query strings are appended to the endpoint URL using ?, with additional query strings appended using &.

This example uses the container_id query string to filter results to the specified container. It also uses the limit query string to return only ten results.


All API requests are submitted via RESTful URLs using REST features, including header-based authentication and JSON/XML request types.

The data character set encoding for requests is UTF-8. A well-formed request uses port 443 and has the user-agent and content-length headers specified.


DigiCert Services API uses these standard HTTP methods:

  • GET

  • POST

  • PUT



Most requests require passing either JSON or XML formatted data. If an endpoint supports or requires a different format, it will be noted for that endpoint.

Supported content-type values include:

  • application/json

  • application/xml

  • application/zip

  • image/jpeg

  • image/png

Filters, sorting, and pagination parameters

Some GET requests support the option to filter and sort response data by using the filters[], sort, offset, and limit query parameters in the request URL.

To use filter or sorting parameters in a request, append them to the request URL with a ?. To apply multiple filters, append each filter parameter with an &.

For example:[status]=pending&sort=date_created

To see which properties an endpoint supports for filtering, check the reference documentation for the endpoint. For general information and examples of the syntax to use when applying filters and sorting results, see the parameter descriptions in the table below.




Limits response to results where the chosen property_name contains a specific value. Replace {{property_name}} in your request with the property to use for filtering.

If the value of the property is a date, you can filter by date range. To filter by date range, separate the start date and end date with an ellipsis (...). To return all results before or after a specific date, prefix the date with a less than (<) or greater than (>) symbol, respectively.


  • filters[email]

    Limits response to results where the email address is

  • filters[common_name][product_name_id]=ssl_basic

    Limit response to results where the common name is and the product ID is ssl_basic.

  • filters[date_created]=2020-09-01T00:00:00

    Limits response to results with a date_created value of 2020-09-01T00:00:00.

  • filters[date_created]=2018-01-01T12:00:00...2020-12-31T23:59:59

    Limits response results with a date_created value between 2018-01-01T12:00:00 and 2020-12-31T23:59:59.

  • filters[date_created]=>2020-07-01

    Limits response to results with a date_created value after 2020-07-01.


Limits response to results where the value of a searched property matches or contains a specific string of characters. To see a list of the searched properties for an endpoint, check the reference documentation for the endpoint.

To search for values that contain a specific string of characters, prefix the string with a URL encoded (percent-encoded) % character: %25. To search for values that are an exact match for a string of characters, omit the %25 from the request.


  • filters[search]=%25gmail

    Limits response to results where the value of a searched property contains the string gmail.

  • filters[search]

    Limits response to results where the value of a searched property is an exact match for the string


Sorts results by the value of one or more properties.

By default, sorts results in ascending alphabetical order (0-9, A-Z). To sort in descending alphabetical order (9-0, Z-A), prefix the property name with a minus (-). To sort by multiple properties, separate the name of each property with a comma. Sort hierarchy matches the order of properties in this list.


  • sort=-common_name

    Sorts results in descending alphabetical order by the value of the common_name property.

  • sort=email,-last_invite_date

    Sorts results in ascending alphabetical order by the value of the email property first, then in descending alphabetical order by the value of the last_invite_date property.


Index of the first result to return.


Total number of results to include in the response.


Responses consist of headers and a body. The body is formatted based on the content-type specified in the request.

See Glossary - Headers for information about HTTP header response codes.

Working with API enhancements

The Services API is in active development. Most enhancements are additive. API consumers should build integrations that can safely handle the addition of new response parameters and new optional request parameters.

Whenever possible, we notify API consumers before we change or remove the behaviors described in this documentation. Undocumented API endpoints, response fields, and request parameters are not officially supported and may change without notice.

If the documentation is unclear or missing information you need to build your integration, send us your feedback at


Adding a note to an order


Retrieving all notes on an order


Deleting a note on an order