• Real-time API: this API describes the position, demographic profile and attention behavior of each detected person, up to 15 times per second.
It is designed to be used for triggering content within a 3rd party application, such as a CMS (see the list of applications having implemented this API here).
• Final event API: this API describes the demographic profile, total attention and dwell time and number of glances of the person that has just left the field of view of the camera.
It is useful for collecting anonymous audience data for reporting purposes outside of VidiCenter.
• Local Status API: this API lets a 3rd party application receive information on the inner operations of the local VidiReports instance (current status, video resolution, license permissions, last and next uploads, etc).
• Content API: this API lets VidiReports catch the ID of the content(s) that played when a watcher was looking towards a digital signage screen.
CMS companies will want to integrate this simple piece of code in order to enable audience per content reporting in the Quividi solution (see the list of CMS having implemented this API here).
The first 3 APIs require a specific license entitlement provided upon request.
• Watcher and OTS API (aka “standard Cloud API”): this API exports audience and traffic data at various granularity levels from VidiCenter
• Audience per content API: this detailed API provides the audience of a content, second by second, watcher per watcher
• Monitoring API: this API outputs some monitoring values (such as percentage of light, CPU usage, presence of camera, etc) and is meant to be used in alert workflows.
• Clip Metadata API: this API makes it possible to complete the content ID captured by the Content API with other metadata (such as the name of the content), in order to make Audience per content reports easier to read.
Those APIs can be queried at any wanted granularity level (number of locations, time span).
They require a secret token, provided by Quividi upon request.