Xovis Api - Documentation

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.

{ "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.

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

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

The Flow Within

He called security. They found three individuals in the server room, copying credit card data from a compromised Wi-Fi hotspot. A group of teenagers had set up an

The last line of the Xovis API documentation, which he’d bookmarked, read: “People move. We measure. You decide.” Alex smiled. He had learned to see the invisible city inside the mall—the currents, the eddies, the quiet corners where time stretched or shrank.

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 .

The IT guy handed Alex a link: https://api.xovis.com/v1/ . Security opened the overflow lot

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 all of it, every number, every trajectory, every alert, came from a simple GET request and a key.

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

Then corporate installed .