This is the most common data type. The sensor tracks when a person crosses a virtual "Count Line" or enters a "Zone."
Before making requests, you must establish a secure connection with the sensor or the Xovis Hub. https:// /api/v4/ Xovis Hub: https:// /hub/api/v1/ Authentication Methods
Telemetry sent immediately when a virtual line is crossed. xovis api documentation
: Sensors feature a native REST API for direct device control and data retrieval, alongside flexible data push options that stream pre-processed information to external servers.
Always parse the timestamp field with a UTC parser before converting to local time. This is the most common data type
When integrating with third-party analytics platforms (e.g., Aislelabs), documentation suggests creating a dedicated controller user specifically for API authentication to segregate access rights and maintain security audit trails.
"elementId": "Entrance_Line_1", "elementType": "LINE", "interval": 60, "values": [ "timestamp": "2026-05-28T07:00:00Z", "countForward": 14, "countReverse": 3 , "timestamp": "2026-05-28T07:01:00Z", "countForward": 19, "countReverse": 5 ] Use code with caution. 4. Best Practices for Developers : Sensors feature a native REST API for
HTTP Basic Authentication or Bearer Tokens (depending on firmware version and setup).
: Data is pre-processed directly on the sensor to maintain full privacy compliance (GDPR), ensuring only anonymous, actionable insights are transmitted. Key Integration Features
For advanced analytics (e.g., heatmaps or path tracking), the API can push raw person coordinates. The sensor tracks the (x,y) foot position of every person in the scene, updating them at configurable intervals (e.g., every 5 seconds).