Skip to main content

Sites

Sites represent client-owned physical locations.

Use siteCode as your stable site identifier. It must be unique for your client account.

Common operations:

  • GET /sites
  • POST /sites
  • GET /sites/{id}
  • PATCH /sites/{id}

Resolve a known client-side identifier with an exact-match list filter:

GET /api/v1/sites?siteCode=SEA-10027
GET /api/v1/sites?uniqueID=KIOSK-12
GET /api/v1/sites?uniqueID2=ASSET-77821

Use only one of these filters per request. The response keeps the normal list shape and returns either the matching client-owned site or an empty data array.

The API derives client ownership from your access token. Do not send a tenant ID or Quickbase record ID.

Legacy fields uniqueID, uniqueID2, friendlyLocationName, and friendlyLocationName2 may still appear on site responses for backward compatibility. New site-visit asset assignment workflows should use site-specific Site Assets configured in SSN rather than relying on those legacy site-level fields.