Xovis Api Documentation __top__

Xovis 3D sensors are the industry standard for people counting, crowd management, and foot traffic analysis in retail, airports, and public spaces. However, the hardware is only half the solution. The true value of Xovis data is unlocked when you integrate it into your own systems, dashboards, or Business Intelligence (BI) platforms.

| Feature | Xovis API Docs | Brickstream (now Sensormatic) | Traf-Sys | |---------|----------------|-------------------------------|-----------| | REST API | ✅ Detailed | ✅ Good | ❌ Limited | | Real-time streaming | ✅ (Socket/MQTT) | ❌ No | ✅ (WebSocket) | | Sandbox environment | ❌ No | ✅ Yes | ❌ No | | Rate limits documented | ❌ No | ✅ Yes | ❌ No |

X-API-Key: your_api_key_here Content-Type: application/json xovis api documentation

For on-premises installations, the Xovis PC Tool offers a local API. The documentation here is noticeably different—more technical, less user-friendly.

: Used for automated, real-time data delivery. In firmware v5 and higher, this is managed through "Logics," where you define a Connection (the destination server) and an Agent (the data format and type being sent). Authentication and Security Xovis 3D sensors are the industry standard for

"devices": [ "id":"xv-01", "model":"X4", "fw":"2.5.1", "ip":"192.168.1.10" ]

Response:

"It’s just a RESTful interface," he muttered, scrolling through the Swagger UI . He began by authenticating his session, sending a request to the

If you already have access to Xovis equipment and need a specific endpoint or data format (e.g., real-time WebSocket streams, occupancy, dwell time), let me know — I can help draft further example calls. | Feature | Xovis API Docs | Brickstream

The average duration an individual stays within the zone. Heatmaps and Coordinate Data