The Xovis developer ecosystem operates primarily through two main data retrieval paradigms:
: For large areas, one sensor can be designated as a "Master" to aggregate data from multiple units, presenting a single unified data stream through its API. 📄 Key Documentation Components
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.
Even with proper configuration, issues can arise. Here are a few common problems and where to look for solutions: xovis api documentation
Xovis sensors can act as MQTT clients. You can configure them to publish data payloads to an MQTT broker (like Mosquitto or AWS IoT Core) instantly whenever a count event occurs.
The Xovis platform utilizes a decentralized architecture where the 3D sensors themselves can compute and store data. Depending on your system design, you will interact with the Xovis API in one of two ways:
"timestamp": "2026-04-11T11:00:00Z", "in": 203, "out": 187, "net": 16 The Xovis developer ecosystem operates primarily through two
curl -X GET "https://api.xovis.io/v3/data/count?sensor_id=SNSR_001&start_ts=2023-10-01T00:00:00Z&end_ts=2023-10-01T23:59:59Z&granularity=1h" \ -H "X-API-Key: your_api_key_here"
While specific endpoints vary by firmware version, the standard structure follows these patterns:
The average duration an individual stays within the zone. Heatmaps and Coordinate Data Even with proper configuration, issues can arise
The Xovis API is flexible regarding data serialization. For RESTful responses and data pushes, the sensor can output data in either JSON or XML (v2 or v1 legacy). For newer integrations, JSON is generally preferred due to its lightweight nature and wide support in analytics platforms. For legacy systems, XML v1 is still available for line count data.
curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://<xovis-host>/api/devices"
All API requests require an API key passed via the X-API-Key header.