Xovis Api Documentation May 2026

It wasn’t.

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. 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. It wasn’t

The API endpoint GET /dwell-times for the "north corridor" showed an average stay of . That was too low. People should linger near the new bookstore and the coffee cart. One night, Alex checked the GET /occupancy/current endpoint

Alex didn’t know. He had old infrared beams at entrances that counted shadows, not people. On rainy days, they double-counted umbrellas. On busy Saturdays, they missed families entirely.

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 .