Get Health Status
Response
Overall service status. Always
"healthy" if the server is responding.Service name (“Nectr”).
Current API version (e.g.,
"0.2.0").Deployment environment (
"development" or "production").Seconds since server started.
PostgreSQL connection status:
"healthy" or "unhealthy: <error>".Neo4j graph database status:
"healthy": Connected and operational"not configured": Neo4j credentials not provided"unhealthy: <error>": Connection failed
Example Response
Use Cases
- Health probes: Use for Kubernetes liveness/readiness checks
- Monitoring: Track uptime and dependency health
- Debugging: Verify database and Neo4j connectivity
Notes
- This endpoint does not require authentication
- Returns 200 OK even if dependencies are unhealthy (check individual status fields)
- Uptime resets on server restart