: Most sensor-level APIs, including the Sensor V5 API , use standard Basic Auth (Username and Password).

You can programmatically retrieve several types of data processed directly on the sensor:

Xovis sensors (PC2S, PC3, etc.) offer two primary ways to access data:

Typically configured during the initial sensor provisioning stage.

"elementId": "Main_Entrance_Line_1", "timestamp": "2026-06-01T06:00:00Z", "measurements": [ "type": "IN", "value": 342 , "type": "OUT", "value": 298 ] Use code with caution. Zone Occupancy and Dwell Time GET /capacity_data

The Xovis API ecosystem provides system integrators and developers with the tools to bridge the gap between high-precision 3D sensing hardware and actionable business intelligence. By utilizing these APIs, businesses can extract real-time people-flow data, including live occupancy, queue metrics, and demographic insights, to power customized analytics platforms. API Architecture and Methods

: Industry-specific case studies, such as the Transportation Eurostar Study , provide context on how wait times and throughput KPIs are implemented in real-world scenarios.

Implement retry logic for network timeouts or sensor reboots.

The flexibility of the API makes it a powerful tool for connecting Xovis data to a wide range of business software:

The sensor hosts a built-in web server exposing a RESTful interface. Developers submit structured HTTP requests directly to the sensor's IP address to fetch device statuses, current counts, or system configurations.

If you are building a live dashboard or a digital sign showing "Current Capacity," you need instantaneous data rather than historical intervals. /api/v4/live/occupancy Method: GET