Xovis Api Documentation < PREMIUM | 2026 >

GET /api/v1/data/history : Fetch count data for a specific time range (requires from and until parameters).

While the official documentation covers configuration, the community provides excellent examples for getting data into other systems. The most notable is the sdu-cfei/xovis-driver on GitHub, which offers:

Count data tracks the number of people crossing a predefined virtual line (Count Line) or entering a specific zone. xovis api documentation

A local HTTP/HTTPS interface built directly into each individual sensor. It is ideal for real-time querying, configuration changes, and localized integrations.

Security is paramount when exposing IoT devices to a network. Xovis utilizes standard web security protocols to secure API endpoints. Authentication Types GET /api/v1/data/history : Fetch count data for a

: Triggered instantly when a line is crossed (e.g., entrance/exit).

The Xovis API offers a range of features that make it a powerful tool for developers. Some of the key features include: A local HTTP/HTTPS interface built directly into each

This interface is used for on-demand data retrieval and device management. It allows you to query specific sensor functions, such as current counting values or device status, directly through standard HTTP requests.