Xovis 3D sensors (such as the PC2S and PC2SE) are autonomous people-counting devices that process data directly on the "edge". Integration is achieved through two primary methods:
If you are hitting dead ends, consider these three scenarios:
Once you obtain the correct link and log in, the documentation is comprehensive. Here is what to expect:
The documentation link depends on how you access the data:
The API transforms raw data into actionable insights. Its advanced AI models power a wide range of real-time applications, including: xovis api documentation link
Once logged into the Xovis Support Portal, navigate to the or "Downloads & Documentation" section. From there, you will find links to:
To develop a feature using Xovis 3D sensors, you can access the Sensor V5 API Documentation hosted on the Postman API Network. Xovis sensors primarily feature a and data push options, allowing for easy integration into customized data intelligence or retail analytics software. Key API Resources
Device configuration, status monitoring, and data retrieval. 2. Data Push (Push Mechanism)
If you purchased through a reseller (e.g., Securiton, Johnson Controls), ask them to request the documentation on your behalf. Xovis 3D sensors (such as the PC2S and
If you are a current customer deploying sensors but lack access to the Hub, you can request the specific API documentation package directly through the Xovis Support Portal.
Depending on your architecture, you will interact with three main types of Xovis APIs: Device-Level REST API
Live queue management systems in airports or dynamic digital signage triggers in retail. 3. Xovis Spider API
: The primary location for official API documentation is the restricted Xovis Hub . You need an active partner or customer account to log in and download the latest API specifications, Swagger files, and SDKs. Its advanced AI models power a wide range
Xovis primarily caters to system integrators, and official SDKs are available through their partner program. However, the public developer community has created valuable resources, including the xovis-push-data-sample in Go, and various Python drivers on GitHub. These can serve as excellent references for understanding the API's mechanics.
This on-device documentation is the most reliable source of truth, as it dynamically reflects the exact API version your sensor is running.
Relies on HTTPS, SFTP, and MQTTS for secure communication over private or public networks. Authentication & Access Control
This is the most common and efficient method. The sensor is configured to send data to a specified server via HTTP(S), FTP, or SFTP at predefined intervals or when specific events occur.