# Changelog

### November **21, 2025**

**New Release:**

* Introduce `filters` in webhook property to filter webhook events containing certain ids
* Introduce `send_on_value_change` boolean in webhook property that the event is sent only when the value changes

**Impact**

* No breaking changes.
* The new properties will help reduce the unneeded events.

### **October 10, 2025**

**New Release:**\
Introduce `floor_custom_id` / `room_custom_id` / `zone_custom_id` in our [reporting](https://docs.butlr.io/historical-occupancy/reporting-api-overview) API.

**Impact**

* No breaking changes.
* These fields are only returned when there's a value.

### **August 13, 2025**

**New Release:**\
We have introduced new **1-minute rollup event types** for Floor Occupancy, Room Occupancy, and Zone Occupancy. These events provide smoothed, minute-aligned occupancy counts and are recomputed with a short look-back period to account for potential delays. This approach may result in updated counts for previous minutes within a rolling 5-minute window.

**New Event Types:**

* `FLOOR_OCCUPANCY_1M`
* `ROOM_OCCUPANCY_1M`
* `ZONE_OCCUPANCY_1M`

**Impact**

* No breaking changes.
* Clients can subscribe to these new event types via webhooks to receive more stable, aggregated occupancy data per minute, improving the accuracy of time-series analysis and reducing noise from second-by-second fluctuations.

### April 30, 2025

**New Release:**

We are introducing the `stats` API under reporting. The `stats` API will give an aggregate view of occupancy data over the specified time range.

**How to Use It**

[API specifications](https://docs.butlr.io/historical-occupancy/reporting-api-overview/statistic-overview).

**Impact**

* No breaking changes
* Clients can use this API to query for aggregate occupancy statistics over a period of time

### April 2, 2025

#### **New Release:**

We’ve introduced a **Calibrated Occupancy** option that enhances the accuracy of traffic-based occupancy data across your spaces.

**How to Use It**

Developers can now enable `calibrated:true` by adding in as filter in [Reporting API](https://docs.butlr.io/historical-occupancy/reporting-api-overview/floor-occupancy) calls to relevant traffic-based endpoints.

**What It Does**

Over time, miscounts from entry and exit sensors can build up, especially in busy areas with multiple entrances. This can lead to:

* Occupancy appears to drop to zero too early
* Spaces showing as occupied even after everyone has left

This new **calibrated model** helps correct for these discrepancies, delivering occupancy counts that more closely reflect real-world usage patterns.

**Key Benefits**

* More accurate traffic-based occupancy trends
* Improved reliability in areas with complex traffic flows
* Better alignment with actual space usage throughout the day

### March 1, 2025

**New Release:**

We’ve introduced new metadata fields to our webhook messages to provide additional customer-specific context. These fields allow for better mapping of data to customer-defined locations.

**Added Fields:**

* `floor_custom_id` → Customer’s unique floor identifier
* `room_custom_id` → Customer’s unique room identifier
* `zone_custom_id` → Customer’s unique zone identifier

**Impact:**

* No breaking changes.
* Existing webhook message structure remains unchanged, ensuring backward compatibility.
* Clients can now utilize these additional fields to enhance data integration.

***

### December 12, 2024

**New Features Released:**

* [**Real-Time Occupancy Webhook:**](https://docs.butlr.io/real-time-occupancy/webhooks-overview) Receive instant updates on occupancy changes for seamless integration and automation.
* [**Tag Management**](https://docs.butlr.io/asset-management/graphql-api-overview/asset-tags)**:** Assign one or more tags to floor, room, and zone assets, enabling better organization and categorization of spaces.
* [**Tag-Based Occupancy Queries:**](https://docs.butlr.io/historical-occupancy/reporting-api-overview/query-occupancy-by-tag) Query presence-based occupancy data for floors, rooms, and zones by tag, providing powerful insights tailored to specific categories or use cases.

***

### **October 11th, 2024**

**Legacy v2 APIs Deprecation**\
The following endpoints will reach their end-of-life on **Friday, October 11th, 2024**:

* `v2/spaces`
* `v2/hives`
* `v2/sensors`
* All sub-resources of the above endpoints.

{% hint style="danger" %}
**Important Note:** All **Login**, **Reporting**, and **Detections** endpoints will remain functional and supported. Please update your integrations accordingly.
{% endhint %}

***

### **September 20th, 2024**

**Fixtures Endpoint Deprecation**\
The **fixtures endpoint**, including objects and sub-resources associated with floors (formerly known as spaces), reached its end-of-life on **Friday, September 20th, 2024**.

**Context:** This feature was part of our previous installation tool, which was deprecated earlier in 2024. There is no replacement functionality for fixtures.

Please review your implementation to ensure compatibility with the latest APIs. For questions or assistance, contact our support team at <support@butlr.io>