Skip to main content
Nektir provides fast, reusable reads from our own published database. Application requests do not wait for Utah DABS and do not trigger upstream collection.
api.nektir.com currently hosts these private pilot docs only. The public API runtime has not been deployed yet, so /v1 requests should use the local development base URL until a separate production API origin is published.
Inventory represents the most recent public-source observation we successfully retrieved. It is not a reservation, purchase guarantee, or claim that Utah DABS updated its source at the same time.

What you can build

Search products

Resolve exact six-character SKUs or search product names with category, price, status, and availability filters.

Find availability

Browse reported inventory across stores, near coordinates, or within a selected store set.

Browse a store

Retrieve store details and products with reviewed inventory observations at that location.

Build honest freshness UI

Use retrieval, publication, coverage, and warning metadata without pretending unknown source age is known.

Design principles

  • Stable API-owned UUIDs are distinct from Utah DABS source identifiers.
  • Utah DABS SKUs and store codes are strings so leading zeroes are preserved.
  • Missing, zero, row-absent, unchecked, stale, restricted, and discontinued states remain distinct.
  • Store, warehouse, and on-order quantities are not combined.
  • Cursor pagination stays pinned to one immutable publication revision.
  • Collection rows use compact source-presence and hours summaries; detail endpoints provide complete lifecycle and schedule metadata.
This is an independent service and is not affiliated with or endorsed by Utah DABS.