| Endpoint | Method | Description | | :--- | :--- | :--- | | /sensors | GET | Lists all sensors connected to the XCS. | | /counts/interval | GET | Retrieves historical footfall data (requires start/end time). | | /occupancy/current | GET | Snapshot of current load per zone. | | /queue/status | GET | Data for actively monitored queue areas. | Let’s simulate a real-world use case: Displaying real-time store occupancy on a digital sign. Step 1: Read the Request Parameters According to the Xovis API documentation, the /occupancy/current endpoint supports optional filtering by locationId . If omitted, it returns all zones.
This returns average time spent (in milliseconds) per zone, helping you optimize product placement. Polling an API every minute is inefficient. The Xovis documentation describes webhooks. You configure XCS to send an HTTP POST to your server only when an event occurs (e.g., queue exceeds 10 people or occupancy hits 90%). xovis api documentation
In the age of smart buildings and data-driven retail, accurate people counting has transitioned from a luxury to a necessity. Xovis , a Swiss leader in high-precision people flow analysis, stands at the forefront of this industry. Their 3D stereo vision sensors are renowned for millimeter-precision counting, but the true power of these sensors is unlocked through their Application Programming Interface (API). | Endpoint | Method | Description | |