Service health

Check service liveness

The application exposes a GET health check. It performs no account mutation and does not require a token.

curl --fail --silent --show-error \
  https://app.usenugget.app/api/healthz

Read the response

Treat this as a liveness signal. It does not verify sign-in, a particular customer operation or every external integration.

{
  "status": "ok"
}

Choose the right monitoring scope

Use a modest check frequency and respect rate-limit responses. A dedicated incident-history page is not published yet. This liveness check does not provide incident history.

Authenticated acceptance checks should use an explicitly authorized environment and account. A public documentation example should never ask someone to paste a live session cookie.