Skip to content

GET /api/ping

Cheap health endpoint. Returns 200 with a tiny JSON body when the Function App is up. No auth header required — use it for uptime monitors and CI smoke tests.

Request

Response

{
  "status": "ok",
  "service": "qr-branding",
  "version": "1.6.2",
  "now": "2026-05-24T08:14:31Z"
}
  • status — always "ok" when the function executes. If it didn't, you'd get a connection error, not a JSON body.
  • version — semver of the deployed engine.
  • now — server clock in UTC. Useful for verifying your X-Internal-Ts signature isn't drifting.

Use cases

  • Uptime monitor: hit /api/ping every 60s; alert on non-200.
  • CI smoke test: after each deploy, fail the pipeline if version doesn't match the tag you just pushed.
  • Clock skew check: compare now with your client clock when debugging 401 INVALID_SIGNATURE from the internal BFF (TTL is 60s; > 90s skew fails the HMAC).

What it does NOT check

The ping is intentionally cheap. It does not validate:

  • Whether the database is reachable.
  • Whether the LLM providers respond.
  • Whether your RapidAPI / internal auth headers are configured correctly.

For deeper checks, hit /api/qr/generate with a minimal payload (content only) and verify the QR comes back.