Skip to content
cresvaDevelopers

Liveness of the storefront surface

GET/api/storefront/health
No keyCallable anonymously. Rate limited by IP.10 requests a minute

Request

bash
curl "https://cresva.ai/api/storefront/health"

Response

Captured from production on 2026-09-16: 200 in 1053ms. This is what the endpoint returned, not an example of what it might.

JSON
{
  "status": "healthy",
  "version": "1.0",
  "uptime_seconds": 285,
  "checks": {
    "database": {
      "status": "healthy",
      "latency_ms": 35
    },
    "redis": {
      "status": "healthy",
      "latency_ms": 225
    },
    "circuit_breaker": {
      "status": "closed",
      "latency_ms": 0
    }
  },
  "active_brands": 2,
  "timestamp": "2026-09-16T04:50:37.124Z"
}

Response codes

200The surface is up.
object
401The key does not match any active key.
erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.
403The key is valid but belongs to a different brand than the one in the path. Keys are scoped to one brand and do not travel.
erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.
404No such brand.
erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.
429Over the rate limit.
erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.
503The rate limiter could not be reached, so the request was refused rather than served unmetered. Deliberately not a 429: the caller has done nothing wrong and the fault is ours.
erroranyTwo shapes exist across this API and that is deliberate rather than untidy. Each route kept the error shape it already used, so an existing client's error handling keeps working. See x-cresva-error-shapes.

Generated from the storefront OpenAPI document at growthagents 269d7898b, sha256 047fe4d301258100. Nothing on this page was typed by hand.