Xovis Api — Documentation

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.

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.

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

The response returned an array of trajectories—each a list of coordinates over time.

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 . Most paths were straight lines: people walked through

No. Behind the pillar was a leading to an old storage area. And inside? A group of teenagers had set up an unlicensed phone repair shop. They were pulling customers away from the official kiosk on the second floor.

Then corporate installed .

It wasn’t.

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

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