Xovis Api Documentation //free\\ -
The Xovis API documentation provides a powerful toolset for transforming physical foot traffic into actionable digital intelligence. Whether you choose the simplicity of REST pulls or the real-time efficiency of HTTP pushes, structured integration allows your business to optimize staffing, improve retail layouts, and manage crowd safety seamlessly.
Don't overload the sensor. For "Live" data, once every 5–10 seconds is usually sufficient.
The Xovis API has a range of use cases across various industries, including:
Understanding these components is the first step. The subsequent sections provide deeper technical dives into each. xovis api documentation
GET /api/v1/zones/occupancy?zoneId=entrance_main Host: 192.168.1.50 Authorization: Bearer [YOUR_API_TOKEN] Use code with caution.
Queue length (number of people waiting), waiting time (average time spent in queue), and service time.
Based on driver documentation, standard implementation methods include: The Xovis API documentation provides a powerful toolset
curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://<xovis-host>/api/devices"
Most current Xovis sensors run on , which supports the Sensor V5 OpenAPI specification . Common Data Points
capacity_data / count_data : Retrieve live occupancy and throughput statistics. For "Live" data, once every 5–10 seconds is
This model is a pull mechanism where your software acts as the client. It sends an HTTP request to the Xovis sensor or management server to fetch data.
Below are the most critical endpoints used for data extraction. A. Real-Time Counting Data ( /counts )
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.
For environments like airport security checkpoints, immigration lines, or retail checkouts, the API exposes advanced queue metrics.