GET
/
v1
/
client-certificates
Lists all client certificates.
curl --request GET \
  --url https://api.checklyhq.com/v1/client-certificates \
  --header 'Authorization: <api-key>'
[
  {
    "host": "www.acme.com",
    "cert": "<string>",
    "ca": "<string>",
    "id": "<string>",
    "created_at": "2023-11-07T05:31:56Z"
  }
]

​
Overview

The List Client Certificates endpoint returns all client certificates configured in your Checkly account. Client certificates enable mutual TLS authentication for monitoring services that require certificate-based authentication. Common Use Cases:
  • Certificate Management
  • mTLS Configuration
  • Security Auditing
  • Certificate Inventory
Client certificates are used for mutual TLS authentication when monitoring services that require certificate-based client authentication. Manage certificates securely and monitor expiration dates.

Authorizations

​
Authorization
string
header
required

The Checkly Public API uses API keys to authenticate requests. You can get the API Key here.

Your API key is like a password: keep it secure!

Authentication to the API is performed using the Bearer auth method in the Authorization header and using the account ID.

For example, set Authorization header while using cURL:

curl -H "Authorization: Bearer [apiKey]" "X-Checkly-Account: [accountId]"

Headers

​
x-checkly-account
string

Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general

Response

Successful

​
host
string
required

The host domain for the certificate without https://. You can use wildcards to match domains, e.g. "*.acme.com"

Example:

"www.acme.com"

​
cert
string
required

The client certificate in PEM format as a string. This string should retain any line breaks, e.g. it should start similar to this "-----BEGIN CERTIFICATE-----\nMIIEnTCCAoWgAwIBAgIJAL+WugL...

​
id
string
required
​
ca
string

An optional CA certificate in PEM format as a string.

​
created_at
string<date-time>