Parameters: cameraId: Indicate the unit ID startTime: Define the beginning instant (within Unix time format) endTime: Specify the finish time (using Unix timestamp format)
In this article, we will offer a thorough directory to the Xovis Interface documentation, addressing everything from acquiring initiated to sophisticated utilization and implementation.
The Xovis Protocol utilizes RESTful framework and supports HTTP methods such as GET, POST, PUT, and DELETE. Interface requests can be made employing any HTTP patron collection or instrument, such as curl or Postman. xovis api documentation
Parameters: cameraId: Input that camera ID startTime: Input that start moment (in UNIX time format) endTime: Input the end time (in POSIX format format)
To example, an valid response for the /cameras endpoint may seem similar to that: "cameras": [ "id": 1, "name": "Camera 1", "location": "Store Entrance" , "id": 2, "name": "Camera 2", "location": "Store Interior" ] People Counting API Endpoints The Xovis API supplies a selection of individual tallying API nodes that enable developers for get people tallying records for particular cameras as well as duration spans. /counts The /counts interface delivers human tracking stats regarding a specific unit as well as time range. Parameters: cameraId: Indicate the unit ID startTime: Define
Xovis Protocol Records: A Comprehensive Guide
For instance, for the purpose of obtain people tracking information regarding device 1 from 2022-01-01 to 2022-01-31, the following call might be made: Parameters: cameraId: Input that camera ID startTime: Input
Reply: JSON entity including people tallying stats