Skip to main content
Monitor Truthlocks API health, check readiness for dependencies, and integrate with your observability stack.

Health Endpoints

Liveness Probe

Check if the API is running. Use for Kubernetes liveness probes:

Readiness Probe

Check if the API is ready to serve traffic (all dependencies healthy):

Kubernetes Configuration

If you’re building applications that depend on Truthlocks, configure your probes to check both your app and the Truthlocks API:

Example Readiness Check (App)

Status page

Check real-time service health and uptime at status.truthlocks.com. The status page auto-refreshes every 60 seconds and requires no authentication.

Monitored services

The status page tracks health for each core service independently: Each service reports one of four statuses: operational, degraded, outage, or unknown. The page displays a per-service response time and an overall system health banner.

Uptime history

A 90-day uptime bar shows daily availability for each service. Hover over any day to see the date and uptime percentage. An overall uptime percentage is displayed alongside each service.

Incident history

Visit the Incident History page to see past incidents in a timeline format. Each entry includes the severity level, affected services, and timestamped updates from investigation through resolution.

Subscribe to notifications

Enter your email at the bottom of the status page to receive incident notifications. You will be notified when incidents are created, updated, or resolved. Enterprise customers can also configure webhook callbacks to receive status change events automatically.

Programmatic status API

Query the status API for machine-readable service health. Use this to integrate Truthlocks availability into your own dashboards, alerting pipelines, or pre-flight checks. No authentication is required.
The endpoint returns the overall system status, a timestamp, and an array of per-service health checks:
Response fields: The overall status is outage if any service is down, degraded if any service is slow or returning errors, and operational when all services are healthy. Example: poll status from your app
Example: pre-flight check before minting Check that the signing and attestation services are healthy before attempting a mint operation. This avoids unnecessary retries when you already know the required services are down.
The status API is rate-limited to prevent abuse. For continuous monitoring, poll no more frequently than once every 30 seconds.
For the full response schema, monitored service IDs, and additional examples, see the status API reference.

Status page

Real-time service health and incident history.

Webhook notifications

Enterprise customers can configure webhook callbacks for status changes.

Status API reference

Full API reference for the programmatic status endpoint.

Email alerts

Subscribe on the status page for incident notifications.

Service Level Agreement

Credits: If we miss SLA targets, you’re entitled to service credits. See your contract or contact support for details.

Monitoring Integration

Integrate Truthlocks health checks with your observability tools:
Prometheus
Datadog
Custom Dashboard Metrics

Gateway resilience

The API gateway includes automatic panic recovery and zero-downtime deployment support:
  • Panic recovery — If the gateway encounters an unexpected internal error, it recovers automatically and returns a structured error response instead of dropping your connection. You do not need to handle dropped connections caused by gateway-level panics.
  • Graceful shutdown — During deployments, the gateway and signing service drain in-flight requests over a 15-second window instead of terminating them immediately. If you previously experienced occasional request failures during maintenance windows, those should no longer occur.
These protections work automatically and require no changes to your integration.

Incident response

If Truthlocks is experiencing issues:
  1. Check status page: status.truthlocks.com
  2. Enable circuit breaker: Fail gracefully in your app
  3. Queue operations: Retry attestation minting later
  4. Contact support: For Enterprise SLA escalation

Circuit Breaker Pattern

Next steps

Observability dashboard

Monitor service health, latency, and usage from the console.

Error reference

Complete list of error codes and handling.

Rate limits

Handle rate limiting gracefully.