To tailor this integration specifically to your setup, please share a few more details:
: Handling custom icons or storage files on the device. 2. Authentication xovis api documentation
A matrix of coordinate densities representing foot traffic intensity. 5. Push vs. Pull: Utilizing MQTT and Webhooks To tailor this integration specifically to your setup,
| 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 . | | | zone_id | integer | No | Specific zone ID
The documentation assumes users already have an Xovis Access Point (XAP) or cloud instance running. It provides no "sandbox" or mock server for testing before hardware arrives.
: To configure a new data push agent, you must:
This review is based on publicly available Xovis documentation and community feedback as of 2025. Always refer to the official Xovis Developer Portal for the latest updates.
© 2025 Appedus - Appedus All Right Reserved