Xovis Api Documentation //top\\ [ 5000+ TRUSTED ]

A physical sensor can monitor multiple "virtual zones." New users often query /sensors expecting occupancy data, but the docs clarify that occupancy belongs to /zones .

If you want to start building your integration, let me know:

All requests follow a standard pattern: http://<XCS_Server_IP>/api/v1/<endpoint>

The data you can access through these APIs falls into several core categories:

Are you connecting directly to or managing them via a Xovis Hub/Cloud platform?

Gender statistics and staff exclusion (requires specific plugins like PIGES or PISTE ).

Protocol options depend on the data type and security requirements:

The is more than a technical manual; it is the bridge between high-fidelity sensor data and your digital ecosystem. By mastering the authentication flows, understanding the difference between occupancy and queue endpoints, and respecting rate limits and timezone nuances, you can build systems that automatically adjust HVAC based on crowding, trigger staffing alerts for long queues, or generate ROI reports for retail footfall.

: Sent at pre-configured intervals (e.g., every 5 or 15 minutes).