Xovis Api Documentation Apr 2026

The Flow Within

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

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

Then corporate installed .

{ "event": "threshold.crossed", "zone": "main_entrance", "value": 204, "timestamp": "2025-11-28T10:13:22Z" } At 10:13 AM on Black Friday, the webhook fired. Security opened the overflow lot. The digital sign rerouted traffic. Silver Creek didn’t have a single fire code violation that day—unlike the mall across town.

And all of it, every number, every trajectory, every alert, came from a simple GET request and a key.

He drilled into GET /paths for that corridor.

He called security. They found three individuals in the server room, copying credit card data from a compromised Wi-Fi hotspot.

Corporate called it a miracle. Alex called it an API call. One night, Alex checked the GET /occupancy/current endpoint. The mall closed at 9 PM. By 10 PM, occupancy should be zero.

The sensors were discreet—small black rectangles near the ceilings, watching entrances, corridors, and even the food court. They used stereo vision and 3D tracking, not cameras that recorded faces, but anonymous blobs of movement.