Health
Health
Operational health status for the current TattooAPI runtime.
GET
Health
Posture: Public no-auth read. This endpoint is part of the current promoted public surface.
https://api.tattooapi.com/api/v1/health.
GET /health/live, GET /health/ready, and legacy GET /health are public and return direct objects, not success wrappers.
Production operators should distinguish three health layers:
GET /api/v1/health/liveis the liveness check. It returns200when the API process is running.GET /api/v1/health/readyis the production readiness check. It reports configured and missing dependency groups for hosting, media staging, communications intake, identity evidence, private workers, approved portfolio storage, runtime mapping, partner auth, and observability. It does not expose secret values.GET /api/v1/healthis the deeper legacy/runtime compatibility report while Wave D cutover still contains older routes. It can report503while/liveand/readyare still green.
/api/v1/health/ready before treating api.tattooapi.com as production-ready for intake, private worker, or approved portfolio flows.
The legacy compatibility endpoint includes a runtime block derived from the internal data SDK. That block is useful for diagnosing fallback posture, but production release decisions should use /live and /ready.
Response Shape
Notes
200means healthy or degraded-but-operational.503means unhealthy.- The endpoint also returns system info, endpoint URLs, and feature flags for the local runtime.
services.configurationstill reports legacy environment readiness during the Wave D cutover.runtime.currentPersistenceis the field to use when checking TattooAPI runtime authority.
Production Readiness Shape
GET /api/v1/health/ready returns safety posture and flow status without secret values:
Ready response:
