Overview

To authenticate with an API key, include the custom HTTP header x‑api‑key in your request. Provide your own API key as the value for this header when you submit your request.

For example, here's a request to the endpoint for creating a new device:

curl -X POST \
  'https://one.digicert.com/iot/api/v1/device' \
  -H 'x-api-key: {{api_key}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "division_id": {{division_id}},
    "device_identifier": "MyDevice",
    "device_profile_id": {{device_profile_id}}
  }'

To create a new API key:

The following operations in the DigiCert​​®​​ IoT Trust Manager API support the option to authenticate with an enrollment passcode instead of an API key:

To authenticate with an enrollment passcode, use the custom HTTP header x-passcode. The value of the x-passcode header is the passcode associated with the enrollment profile you specify in the body of the request. Requests that use enrollment passcode authentication do not include the x-api-key header.

For example, here’s a call to the endpoint for requesting a new certificate:

curl --request POST 'https://one.digicert.com/iot/api/v1/certificate' \
--header 'x-passcode: {{enrollment_passcode}}' \
--header 'Content-Type: application/json' \
--data-raw '{
  "csr": {{csr}},
  "enrollment_profile_id": {{enrollment_profile_id}},
  ...
}'

Many endpoints in the DigiCert​​®​​ IoT Trust Manager API support the option for mutual TLS authentication. With mutual TLS authentication, a client can access the endpoint by presenting a trusted certificate in the request.

To use mutual TLS authentication:

Supported endpoints

Clients can authenticate to the following operations by presenting a certificate associated with the device:

Clients can authenticate to the following operations by presenting a certificate that is registered to the enrollment profile specified in the request payload: