The response returned an array of trajectories—each a list of coordinates over time.
He pulled GET /paths for the last hour. Three trajectories moved in perfect synchronization—stopping together, starting together. Not shoppers. Not cleaners.
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. xovis api documentation
“Traffic is down 12%,” his district manager would say. “Why?”
{ "zone": "main_entrance", "interval": "2025-03-10T14:00:00Z", "in": 847, "out": 812, "net": 35 } For the first time, he knew exactly how many people were inside. Two weeks later, Alex noticed something strange. The response returned an array of trajectories—each a
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. Not shoppers
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.
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.
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:
It wasn’t.