Xovis Api Documentation Jun 2026

Options: cameraId: Indicate the unit ID startTime: Specify the beginning instant (within Unix time type) endTime: Indicate the conclusion instant (within Unix format structure)

Introduction

Xovis API Documentation: A Complete Guide Introduction The Xovis API is a strong tool that allows developers to incorporate Xovis’ inventive skill into his own applications. With the Xovis API, developers can leverage the capabilities of Xovis’ citizens counting and analytics solutions to secure precious insights into customer behavior, improve trade operations, and develop overall customer experience. In this article, we will offer a comprehensive manual to the Xovis API documentation, incorporating everything from acquiring started to higher usage and implementation. Getting Started with Xovis API To get started with the Xovis API, developers require to list for an API key on the Xovis website. Once registered, developers will get an API key that can be used to confirm API requests. The Xovis API employs RESTful architecture and supports HTTP means such as GET, POST, PUT, and DELETE. API requests can be made using any HTTP customer library or tool, such as curl or Postman. API Endpoints xovis api documentation

To illustration, an successful answer for the /cameras terminus may seem similar to that: "cameras": [ "id": 1, "name": "Camera 1", "location": "Store Entrance" , "id": 2, "name": "Camera 2", "location": "Store Interior" ] Individuals Tracking API Connectors The Xovis API supplies the selection from human tracking API endpoints which enable developers for retrieve human counting information for certain cameras or time spans. /counts The /counts point provides people counting information concerning the specific camera as well as period interval. Options: cameraId: Indicate the unit ID startTime: Specify