Xovis Api Documentation Site

: Ad-hoc queries, auditing configuration settings, downloading system logs, or syncing historical data batches up to 120 days old.

: Allows for pull-based data retrieval. Users can query specific endpoints for real-time counts, historical data, and device status.

"zoneId": "Queue_Lane_A", "currentOccupancy": 14, "avgDwellTimeSeconds": 45.2 Use code with caution. AI Extension Metadata Payloads xovis api documentation

Xovis documentation takes security seriously but makes it cumbersome.

"zoneName": "Main Entrance", "currentOccupancy": 42, "timestamp": "2023-10-27T10:15:00Z" Use code with caution. 6. Best Practices for Developers "timestamp": "2023-10-27T10:15:00Z" Use code with caution.

: Data push objects typically use JSON , while sensor status reports often use XML .

The sensor can be configured to send JSON packets to your server whenever a new event occurs. This is ideal for: Real-time dashboard updates. Immediate integration with POS systems. Reducing latency in data analytics. Key Use Cases Addressed by Xovis API : Ad-hoc queries

Endpoints for network scanning, configuration updates, and license management.

The documentation is generally divided into several key functional areas: A. Sensor Management & Configuration