Errors and limits

Errors use application/problem+json and include:

{
  "type": "https://utah-dabs-api.invalid/problems/invalid_parameter",
  "title": "Invalid request",
  "status": 400,
  "detail": "lat,lng must be supplied together",
  "instance": "/v1/stores",
  "code": "INVALID_PARAMETER",
  "request_id": "018f2fd0-a3d4-7d20-9c11-9482722f6b26",
  "invalid_params": [
    { "name": "lat,lng", "reason": "must be supplied together" }
  ]
}

Status	Handling
`400`	Correct the invalid or incompatible parameters.
`404`	The route or published resource does not exist.
`410`	Restart pagination without the expired cursor.
`429`	Wait for `Retry-After`, then retry with jitter.
`500`	Retry only if appropriate and retain `request_id` when reporting the failure. Internal details are deliberately withheld.
`503`	Keep last-known-good application state and retry with exponential backoff.

EXPORT_UNAVAILABLE identifies a busy cold-export builder or an export size/time limit. Honor Retry-After and retry the same revision-pinned URL. Download resources sequentially; persistent limit failures require operator review. DATABASE_UNAVAILABLE means the stored serving database is unavailable; neither error manufactures empty inventory or resets successful observation timestamps. Every response includes X-Request-ID; error bodies repeat it as request_id. This is the value an API consumer should include in a support report. Geographic filters require both lat and lng to contain numeric coordinates. Supplying radius_m without coordinates returns 400; the radius is never silently ignored. Zero is a valid coordinate. Product prices use inclusive bounds in minor currency units. price_min_minor must not exceed price_max_minor; equal bounds and either bound alone are supported. Change-history and observed-change filters require a valid calendar date and time with an explicit timezone. Impossible dates such as February 29 in a non-leap year return 400.

Data warnings

Successful responses can include compact, code-only meta.warnings. These are not transport errors. Use the code table rather than displaying a server-supplied sentence verbatim:

Code	Meaning
`FIXTURE_DATA`	The published inventory is historical fixture evidence, not current DABS inventory.
`INVENTORY_COVERAGE_PARTIAL`	Unchecked product/store pairs remain; an empty result does not establish no stock.
`SOURCE_REFRESH_DELAYED`	A scheduled attempt is overdue or failed; the API is retaining the last successful observation.
`UPSTREAM_PRODUCT_UNAVAILABLE`	DABS itself currently fails to serve the product detail. Inventory stays unchecked or last-known-good, and automated retries are paused after operator confirmation.
`SOURCE_SCHEMA_QUARANTINED`	Automatic refresh stopped because identity or response structure did not validate.
`CATALOG_BATCH_OLD`	The latest complete catalog batch exceeds the configured catalog retrieval-age policy. This code is reserved for catalog-age monitoring and is not inferred from inventory age.

Inventory objects separately expose their last successful times.retrieved_at, Nektir times.published_at, and last_refresh_attempt. A recent failed attempt never replaces the successful observation timestamp. Utah DABS source-update time remains unknown unless a source explicitly provides it. This invariant is documented here and in /v1/meta; it is not repeated as a warning on every inventory response. The local pilot default is 300 public requests per minute per client address. An online deployment may enforce the same policy at its trusted edge instead. Treat the published Retry-After header as authoritative if deployment policy changes.

Get started

Core concepts

Integration guides

Data warnings