reset_count : Remotely clear sensor counts for session-based tracking.
"status": "error", "code": "INVALID_TIMESTAMP", "message": "start_time must be before end_time"
For developers and system integrators, the is the key to transforming raw pedestrian data into actionable business intelligence. Whether you are looking to integrate real-time occupancy data into a building management system (BMS), feed footfall metrics into a CRM, or trigger automated alerts in a queue management dashboard, understanding this documentation is critical.
Are you querying a or using the centralized Xovis Hub ? xovis api documentation
: For large-scale areas, the API facilitates the combination of up to 200 sensors via the Xovis SPIDER , enabling seamless path tracking across massive physical footprints.
Best for legacy systems requiring scheduled CSV or XML file drops. 2. Authentication and Security
You can programmatically retrieve several types of data processed directly on the sensor: reset_count : Remotely clear sensor counts for session-based
The Xovis API documentation categorizes endpoints based on functional capabilities. Below are the core metric categories available for integration. Count Data
Your server application must parse this JSON and store or process the direction and gender data accordingly.
]
While comprehensive REST API documentation from Xovis is not publicly indexed, third-party and community-driven resources provide valuable insights. For instance, an open-source driver for the PlaceOS building management system documents a Xovis::SensorAPI Crystal class. It lists methods that give a clear picture of the API's capabilities:
While this guide provides a strategic overview, the definitive source remains the official Xovis documentation delivered with your software. Always download the latest version, test against a sandbox XCS instance, and remember: high-quality people counting starts with hardware, but intelligence begins at the API.
Chat