Xovis Api Documentation Apr 2026

Most paths were straight lines: people walked through. But one repeated pattern caught his eye: a sudden stop at coordinate [x: 214, y: 87] , then a rapid reversal.

The Xovis API didn't see faces. But it saw behavior . And behavior never lies. Black Friday approached. Alex configured a webhook —a feature buried deep in the documentation under POST /webhooks/subscriptions .

He walked to that spot in the real mall. It was an empty pillar.

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: xovis api documentation

“Here’s your API documentation,” he said. “Good luck.”

“Traffic is down 12%,” his district manager would say. “Why?”

{ "zone": "lower_level", "current_occupancy": 3, "timestamp": "2025-12-01T22:00:00Z" } Three people. After hours. In a zone with no security cameras. Most paths were straight lines: people walked through

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.

He drilled into GET /paths for that corridor.

Then corporate installed .

He didn’t guess anymore. He read the flow.

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 .

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. But it saw behavior