Readiness Check
Deep readiness probe for deploy gates and manual diagnostics. Runs a `SELECT 1` against PostgreSQL and a `PING` against Redis, and returns `503` if either is unreachable. Because it wakes database compute on every call, prefer `GET /api/v1/health` for routine uptime monitoring. Like the liveness probe, it requires no authentication.
Response Body
application/json
application/json
curl -X GET "https://example.com/api/v1/health/ready"{ "success": true, "message": "Server is healthy", "data": { "status": "ok", "database": "connected", "redis": "connected", "timestamp": "2026-04-26T10:00:00.000Z" }}Liveness CheckGET
Lightweight liveness probe. Confirms the API process is up and responding. It deliberately touches **no** external dependency — no database query, no Redis command — so that frequent uptime polling does not keep database compute awake. It therefore cannot report on PostgreSQL or Redis, and never returns `503`. For dependency health use `GET /api/v1/health/ready`. This is the only truly public endpoint on the API: it requires no session, no API key, and no first-party origin.
Authentication Module
Identity management and session control via Email OTP and secure cookies.