Xovis Api Documentation -

curl -H "X-API-Key: sk_live_..." \ https://api.xovis.com/v1/counts/total?zone=main_entrance&interval=hour He got back JSON. Clean. Precise. Real .

The API endpoint GET /dwell-times for the "north corridor" showed an average stay of . That was too low. People should linger near the new bookstore and the coffee cart. xovis api documentation

He set a rule: When main_entrance.counts.in exceeds 200 people in 5 minutes, send an alert to security and trigger a digital sign outside saying "EAST ENTRANCE IS LESS BUSY". The webhook payload was minimal: curl -H "X-API-Key: sk_live_

And that was its strength. No GDPR nightmares. No privacy lawsuits. Just pure, aggregated truth. A year later, Alex presented to corporate using custom dashboards powered entirely by Xovis API data. He predicted a 14% traffic drop before Christmas due to road construction—and he was right, because the API showed early footfall decay at the south entrance. People should linger near the new bookstore and

When a struggling mall manager discovers the raw data stream from the Xovis people-counting API, he learns that numbers don’t just tell him how many people enter—they whisper secrets, expose lies, and predict the future. Part One: The Blind Manager Alex Kline had managed the Silver Creek Mall for three years. Every month, he reported footfall figures to corporate. Every month, his reports were guesswork.

It wasn’t.