The Strapi health check endpoint: /_health

Strapi provides an unauthenticated `GET /_health` endpoint that returns HTTP 204 with no body, offering a lightweight liveness signal that confirms the Node process and HTTP server are running but does not verify ongoing database availability, migrations, upload providers, or admin-panel readiness. It can be used for Docker health checks, Kubernetes startup, liveness, and readiness probes, AWS ALB or NLB target-group checks, Nginx upstream monitoring, and external uptime services, though configurations must explicitly accept status 204 rather than the commonly expected 200. Slow Strapi startup due to schema loading, migrations, or database synchronization requires sufficiently long grace periods or Kubernetes startup probes to avoid restart loops. For dependency-aware monitoring, a separate public deep-health route can query the database and return 200 or 503, but it should not replace liveness checks because transient dependency failures could remove all instances from service. A small public content API endpoint is another option for monitors requiring 200 responses and for testing more of the application stack, although it creates database load with each poll.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.