Observability
Endpoints
GET /api/v1/error-codes
GET /api/v1/error-codesStable error code catalog. Returns every error code the v1 API can return, its HTTP status, description, and whether the error is retryable.
Complete error code catalog
Catalog of all stable v1 API error codes. Every error response from /api/v1 includes a code field that matches one of these entries. Use retryable to decide whether to back off and retry.
Complete error code catalog
GET /api/v1/status
GET /api/v1/statusComponent-level health status suitable for status-page consumption. No auth required. Cached for 30 seconds.
Component health status (may be operational, degraded, or incident)
Worst-case status across all components
When this status snapshot was computed (TTL: 30 s)
Component health status (may be operational, degraded, or incident)
GET /api/v1/usage
GET /api/v1/usagePer-key API usage metrics (admin scope). Returns request counts, error counts, rate-limit hits, and latency broken down by route and 1-minute time bucket.
Scoped API key. Scopes: read, commerce, admin.
Start of the time window (ISO 8601). Defaults to 24 hours ago.
End of the time window (ISO 8601). Defaults to now.
API key ID to filter. Defaults to the calling key. Pass * to see all keys on the tenant.
Filter to a specific route pattern (e.g. /accounts/:id).
Usage summary with per-route and per-bucket breakdowns
Per-key API usage metrics aggregated by route and time bucket
API key required
Insufficient scope (admin required)
Last updated
Was this helpful?
