Xovis Api Documentation May 2026

Xovis has modernized its API documentation to include MQTT and Webhooks, which are essential for cloud integration.

What’s Well Documented: Payload structure, retry logic (exponential backoff), and security (HMAC signatures for verification).

What’s Missing: No clear guidance on throughput limits (e.g., max webhooks per second per sensor). Developers must guess or test destructively. xovis api documentation

Retrieves people counting data (In, Out, Passby) for a specific sensor or zone.

Endpoint: GET /data/count

Query Parameters:

| Parameter | Type | Required | Description | | :--- | :--- | :--- | :--- | | sensor_id | string | Yes | The unique identifier of the sensor. | | zone_id | integer | No | Specific zone ID. If omitted, returns data for all zones. | | start_ts | datetime | Yes | Start time (ISO 8601 format, e.g., 2023-10-27T00:00:00Z). | | end_ts | datetime | Yes | End time (ISO 8601 format). | | granularity | string | No | Aggregation level (1h, 1d). Default is 1h. | Xovis has modernized its API documentation to include

Example Request:

curl -X GET "https://api.xovis.io/v3/data/count?sensor_id=SNSR_001&start_ts=2023-10-01T00:00:00Z&end_ts=2023-10-01T23:59:59Z&granularity=1h" \
-H "X-API-Key: your_api_key_here"

Example Response:

  "sensor_id": "SNSR_001",
  "location_id": "LOC_NYC_05",
  "data": [
"timestamp": "2023-10-01T08:00:00Z",
      "in": 145,
      "out": 132,
      "passby": 50,
      "occupancy": 13
    ,
"timestamp": "2023-10-01T09:00:00Z",
      "in": 210,
      "out": 195,
      "passby": 65,
      "occupancy": 28
]

If you want, I can: