The documentation assumes users already have an Xovis Access Point (XAP) or cloud instance running. It provides no "sandbox" or mock server for testing before hardware arrives.
What is your specific (e.g., retail analytics, live building occupancy, or queue management)? Share public link
]
This comprehensive guide breaks down the Xovis API documentation, exploring how the API works, key endpoints, data formats, and best practices for building a robust integration. 1. Overview of Xovis Data Integration Architecture
The Xovis API documentation categorizes endpoints based on functional capabilities. Below are the core metric categories available for integration. Count Data xovis api documentation
Data from Xovis sensors can trigger real-time automations. For instance, when zone occupancy reaches a certain threshold, the API can send a command to the HVAC system to increase ventilation or adjust temperature, leading to energy savings and enhanced comfort.
For real-time applications, sensors can be configured to push data automatically via HTTPs, SFTP, or MQTTS . Common push triggers include: The documentation assumes users already have an Xovis
HTTP Basic Authentication or Bearer Tokens (depending on firmware version and setup).
All data payloads are delivered in JSON or XML , making them easy to parse in any programming language. Share public link ] This comprehensive guide breaks
Xovis operates on an edge-computing architecture. This means the 3D stereoscopic sensors process video streams locally on the device itself, calculating counts, dwell times, and fill levels without sending video feeds to the cloud. This design ensures strict data privacy and compliance with GDPR regulations.