Liveness probe

GET 
/api/v1/health/live

Liveness probe — is the process alive?

Always returns 200 as long as the event loop is running. Does not touch any downstream (the database / the cache / the feature flag service / the billing provider).

• Public endpoint (no auth required).
• Intended for the container orchestrator / the load balancer liveness checks.

Responses

200

Process is alive.

400

Bad request — malformed input or failed validation.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.