Deployment dependency diagnostics
GET/api/v1/health/diagnostics
Run the on-demand deployment preflight diagnostic.
This is intentionally separate from /health/ready: readiness gates only
the database and the cache so transient optional-service outages do not pull a live
API out of rotation. Diagnostics are authenticated and admin-only.
Responses
- 200
- 400
- 404
- 409
- 422
- 429
- 500
- 503
Every required diagnostic check passed.
Bad request — malformed input or failed validation.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.
One or more required diagnostic checks failed.