Xovis Api Documentation Site
Easy to implement; works well behind restrictive firewalls.
This section of the docs is dense and aimed at C++ or embedded developers. Examples are scarce. Many users complain that error handling (e.g., what happens when the socket drops) is poorly explained. xovis api documentation
Best for legacy systems requiring scheduled CSV or XML file drops. 2. Authentication and Security Easy to implement; works well behind restrictive firewalls
| Parameter | Type | Required | Description | | :--- | :--- | :--- | :--- | | sensor_id | string | Yes | The unique identifier of the sensor. | | zone_id | integer | No | Specific zone ID. If omitted, returns data for all zones. | | start_ts | datetime | Yes | Start time (ISO 8601 format, e.g., 2023-10-27T00:00:00Z ). | | end_ts | datetime | Yes | End time (ISO 8601 format). | | granularity | string | No | Aggregation level ( 1h , 1d ). Default is 1h . | Many users complain that error handling (e
Accurate data analysis depends heavily on timestamps. Ensure all Xovis sensors and your backend servers are synchronized to the same Network Time Protocol (NTP) server.
