APIs

  1. Admin Floors (v1)

    The Floors API provides access to create, read and update floor resources. Floors are a component of the organizational hierarchy. A building is composed of one or more floors.

  2. Admin Geotransforms (v1)

    The Geotransforms API provides a mechanism for generating geotransform objects from an array of ground control points.

  3. Admin 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.

  4. Admin Known Devices (v2)

    The Asset Known Device API provides access to create, read and update known device resources. Known Devices resources connect a known entity like a person or asset to one or more devices. A known device id is added to a position object as the position streams through the system. A known device can be associated with a single physical device with multiple ids (wifi, bluetooth, and/or bls) or can be associated with multiple physical devices. In addition, known devices can be assigned categories.

  5. Admin Lights Map (v1)

    The Lights Map API provides access to operations to retrieve the current lights map for an Eclypse Controller.

  6. Admin Luminaire Positions (v1)

    The Luminaire Positions API provides access to operations that retrieve and update luminaire positions.

  7. Admin Luminaire Summaries (v1)

    The Luminaire Summaries API provides access to operations that retrieve luminaire summaries.

  8. Admin Luminaire Types (v1)

    The Luminaire Types API provides access to operations that retrieve and update luminaire types.

  9. Admin Map Tiling (v1)

    The Map Tiling API provides access to operations for kicking off map tiling tasks

  10. Admin Map Tokens (v1)

    The Map Tokens API provides access to create, read and update map token resources. Map Tokens are resources that define authentication information to external mapping systems. Typically, Atrius uses the ArcGIS Online mapping system for rendering and serving out map tiles for a floor. If a map service is "secured" on ArcGIS Online, then the authentication information for that service must be stored as a map token and then associated with the floor.

    Once the map token authentication information is stored in this system, a new token will be generated for each request for a map token. The Atrius system will proxy through to ArcGIS Online to request a new token using the authentication information stored in this resource.