Certificate Status

The certificates endpoint returns certificate lifecycle information for your Deepgram self-hosted deployment. Use it to track certificate creation, end-of-support, and end-of-life dates.

This endpoint is available on all self-hosted container images:

{
  "beginning_of_support": "2025-11-13 15:25:28.0 +00:00:00",
  "end_of_support": "2027-05-15 03:25:28.0 +00:00:00",
  "end_of_life": "2028-11-12 15:25:58.0 +00:00:00",
  "instance_id": "235c0e16-c791-45b8-bf41-757ca11ac2b9"
}

cURL (API)

curl http://localhost:8080/v1/certificates

cURL (Engine)

curl http://localhost:9991/v1/certificates

Python

import requests

response = requests.get("http://localhost:8080/v1/certificates")
cert = response.json()
print(f"Certificate created: {cert['beginning_of_support']}")
print(f"End of support: {cert['end_of_support']}")
print(f"End of life: {cert['end_of_life']}")
print(f"Instance ID: {cert['instance_id']}")

JavaScript

const response = await fetch('http://localhost:8080/v1/certificates');
const cert = await response.json();
console.log(`Certificate created: ${cert.beginning_of_support}`);
console.log(`End of support: ${cert.end_of_support}`);
console.log(`End of life: ${cert.end_of_life}`);
console.log(`Instance ID: ${cert.instance_id}`);

Deepgram self-hosted certificates follow a fixed lifecycle:

1. Active (0–18 months after creation) — Full support. Software updates and security patches are available.
2. End of Support (18–36 months after creation) — The deployment continues to function, but Deepgram no longer provides support or updates for this certificate version. Plan your renewal.
3. End of Life (36 months after creation) — The certificate expires. The deployment will no longer validate against the Deepgram license server.

All self-hosted containers log certificate information on startup. You can inspect this without querying an endpoint:

INFO impeller: Certificates information. beginning_of_support=2025-11-13 15:26:33.0 +00:00:00 end_of_support=2027-05-15 3:26:33.0 +00:00:00 end_of_life=2028-11-12 15:27:03.0 +00:00:00 instance_id=c32fb5ff-538c-4b93-b854-8c038a22c302

This message appears in the logs for API, Engine, License Proxy, and Billing containers. If a certificate has expired, the container will log an error and refuse to start.

Check the eol field periodically to ensure your deployment renews before certificate expiration. A recommended approach:

Python

from datetime import datetime, timezone
import requests

response = requests.get("http://localhost:8080/v1/certificates")
cert = response.json()

eol = datetime.fromisoformat(cert["end_of_life"])
days_remaining = (eol - datetime.now(timezone.utc)).days

if days_remaining < 90:
    print(f"WARNING: Certificate expires in {days_remaining} days")
elif days_remaining < 180:
    print(f"Certificate expires in {days_remaining} days — plan renewal")
else:
    print(f"Certificate valid for {days_remaining} more days")

The Billing container requires certificates_port in billing.toml to serve the certificates endpoint. Without this setting, the certificates server binds to an ephemeral port and is not reachable.

[server]
  host = "0.0.0.0"
  port = 8443
  base_url = "/"
  certificates_port = 8080

Expose this port in your Docker Compose or Kubernetes configuration to query /v1/certificates on the Billing container.

The /v1/certificates endpoint is available in release 260319 and later on all self-hosted container images.

• Status Endpoint - Monitor node health and readiness
• System Maintenance - Keeping your deployment healthy