Xovis Api Documentation ((link))

If you configure a push for using XML, a snippet might look like this:

This returns average time spent (in milliseconds) per zone, helping you optimize product placement.

: Modern sensors support MQTT for instant, low-latency pedestrian flow reporting. Remote Management via Xovis HUB xovis api documentation

The Xovis ecosystem operates on an edge-computing model. The 3D sensors process video streams locally on the device to count people, calculate dwell times, and map journeys. No video streams leave the sensor, ensuring strict compliance with global privacy regulations like GDPR.

: A utility for discovering sensors on a local network and configuring IP settings. Firmware Support If you configure a push for using XML,

: The central platform for partners to access technical materials, manuals, and training. Xovis Support Portal

Payload structure, retry logic (exponential backoff), and security (HMAC signatures for verification). The 3D sensors process video streams locally on

: Secure scheduled file transfers, heavily utilized for batch daily reporting. Standard API Endpoint Architecture

When a person crosses the defined line, the sensor pushes a payload to your URL. A typical LineCrossing event looks like this:

Returns uptime, CPU load, firmware version, and camera calibration status (e.g., CALIBRATED , ERROR ). 4. Push vs. Pull: Choosing Your Data Delivery Method