1. Insights Known Device Property Type (v1)

    The Asset Known Device Property Type API provides access to known device property type resources. Known Devices Property Type resources provide a typing system for optional properties associated with a known device.

  2. Insights Known Devices (v2)

    The Known Device API provides access retrieve known device resources. Known Devices resources can connect an anonymous entity like a person or asset to one or more Known Devices.

  3. Insights Live Positions (v1)

    The Live Positions API provides access to real time and/or near real time positions and position aggregates.

  4. Insights Organizations (v1)

    The Admin Organization API provides access to read resources. Organizations are the top level of the organizational hierarchy. All child resources are associated to organizations either directly or through intermediary resources. Only a partner can create or modify an organization.

  5. Insights Positions (v3)

    The Positions API provides access to operations that retrieve live & historical position information. This position data is ingested and sanitized by the Atrius position processing system. Note, there may some delay between a position sent from a device and becoming available through this API.

  6. Insights Product Sources (v1)

    The Product Sources API provides access to retrieve the available data sources (e.g. Assets, Navigator, etc.) for Atrius messages.

  7. Insights Sites (v1)

    The Sites API provides access to read site resources. Sites resources are a key element of the organizational hierarchy. A site resource is a discrete location in the world. It can be composed of one (retail store) or more buildings (college campus). Configuration and metric calculations are tied directly to the site configuration.

  8. Insights Zones (v1)

    The Zone API provides access to read zone resources. Zones represent physical areas on a floor where positions are collected and metrics are processed. A position must exist in a zone in order for it to be collected by the system. Zones are represented as GeoJSON features.

    There are three types of zones:

    • Capture Area (multi-floor | site optional) - Represent the maximum bounds for collecting positions. Any positions identified as outside of the capture area are dropped from the system.
    • Metric (site required) - Represent areas for position and metric collection. The collection of zone represent a site metric.
    • Action (site optional) - Represent areas on the floor where client actions should occur. The messageContent is open for client applications to store application specific content.
  9. Live View Categories (v1)

    The Categories API provides access to retrieve Category resources. Category resources are a mechanism for adding additional contextual information about a resource.

  10. Live View Floor Map Tokens (v1)

    The Floor Map Tokens API Provides Access To Operations That Retrieve Floor Map Tokens Which Are Used To Access Map Services For A Site.