Xovis Api Documentation «LATEST ●»

Understanding the Xovis API: A Guide to Integration and Data Access

The Xovis system can be integrated into your software architecture in two primary ways, each suited to different use cases.

For high-frequency coordinate data used in live map visualizations. 2. Core API Categories xovis api documentation

Xovis sells several sensor generations (3D, X3, PC Tool 2 vs. 3). The API documentation does not clearly separate which endpoints work with which firmware. You often find an endpoint, only to discover it’s unsupported on your hardware.

What or platform (e.g., Python, Node.js, Power BI) are you building this on? Understanding the Xovis API: A Guide to Integration

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

| 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 . | Core API Categories Xovis sells several sensor generations

Not strictly real-time; increases network overhead due to repeated polling requests. The Push Method (Webhooks & Data Forwarding)