A retailer wants to display live occupancy on a TV screen in the store window.

The Xovis API ecosystem is designed to bridge the gap between high-precision 3D sensing and actionable business intelligence. By exposing core sensor functionalities through a robust REST API and data push options, Xovis allows developers to integrate real-time people flow data directly into custom software environments, such as retail analytics platforms, airport management systems, and smart building dashboards. Core API Capabilities

Response:

Connecting Xovis sensors to cash register software.

Returns the current cumulative inbound and outbound counts for defined counting lines. Sample Response:

Understanding where customers linger is gold for retailers. The documentation explains the dwell_time parameter: GET /zones/id/dwell?interval=PT1H

: Implements standard HTTP request-response endpoints. It is ideal for device discovery, remote adjustments, querying historical logs, and managing sensor firmware.

The Xovis API is a that allows external applications to communicate with the XCS. It returns data in standard JSON format, making it universally compatible with cloud services, on-premise databases, and modern web frameworks.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

System health, uptime, and storage information (sensors can store data for up to 120 days). Authentication

Retrieve real-time metrics for up to 99 counting lines and 99 zones per sensor.

Most current Xovis sensors run on , which supports the Sensor V5 OpenAPI specification . Common Data Points

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