Start free

Data and trust

Status and TLS

Where to check Clive status and health, and the transport security (TLS) every connection uses.

Where to look

ProductionSandbox
Status pageclivehealth.app/statusUse the status API
Status APIGET https://api.clivehealth.app/api/v1/statusGET https://sandbox-api.clivehealth.app/api/v1/status
Health checkGET https://api.clivehealth.app/healthGET https://sandbox-api.clivehealth.app/health

Status and health checks

  • Status page. The public status page shows the current status of the API, the database, background jobs and webhook delivery, with open incidents and those resolved in the last 14 days. It refreshes every minute.
  • Status API. GET /api/v1/status on the API host returns the same information as JSON, without authentication (30 requests per minute per IP address). Poll it from your monitoring rather than scraping the page.
  • Health check. GET /health answers 200 with "status": "ok", or "degraded" when background work (such as webhook delivery) is running late, and 503 with "status": "down" when the API cannot reach its database. It also reports "env" (production or sandbox).
  • Component states are operational, degraded, partial outage and major outage. Incidents state their impact (minor, major or critical), which components they affect, and a timeline of updates from investigating to resolved.
  • The sandbox has its own GET /health and GET /api/v1/status; the status page covers production.

Transport security (TLS)

  • TLS 1.2 or newer on every connection; TLS 1.3 preferred. TLS 1.0 and 1.1, SSLv3 and plaintext HTTP are not accepted for API, web app or webhook traffic. Plain http:// requests are redirected to HTTPS.
  • HSTS. The API sends Strict-Transport-Security with includeSubDomains (180 days); the web apps send it for two years. Browsers never downgrade.
  • Forward secrecy and AEAD ciphers only. TLS 1.3 uses its standard suites (AES-128-GCM, AES-256-GCM, ChaCha20-Poly1305). TLS 1.2 uses ECDHE key exchange with AES-GCM or ChaCha20-Poly1305. No RC4, 3DES, export, NULL or anonymous suites.
  • Outbound connections are verified. Webhooks, partner feeds and every other call Clive makes use TLS 1.2 or newer with certificate and hostname verification. Webhook endpoints must be https:// URLs.
  • Certificates are managed and renewed automatically by our hosting edge.