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

​
Overview

The Get Client Certificate endpoint retrieves detailed information about a specific client certificate, including metadata, expiration dates, and usage information. Common Use Cases:
  • Certificate Detail Inspection
  • Expiration Monitoring
  • Usage Verification
  • Certificate Management
This endpoint returns certificate metadata and usage information but does not expose private key material for security reasons.

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

Path Parameters

​
id
string
required

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>