In this release
We have updated the aliases filter behavior on all basic GET endpoints. Previously, creating aliases was case-sensitive, but filtering by alias on the GET endpoints performed case-insensitive matching. With this release, filtering by alias is now case-sensitive, making alias lookups behave the same as ID lookups. This is a breaking change.
This change improves consistency across the API and allows alias-based retrieval to work more predictably—similar to GET by ID.
Updated endpoints
The following endpoints are affected:
GET /json/realestate
GET /json/realestatecomponent
GET /json/buildingcomponent
GET /json/room
GET /json/storey
GET /json/asset
GET /json/device
GET /json/sensor
GET /json/actuator
GET /json/collection
GET /json/apartment
GET /json/tenantunit
GET /json/system
GET /json/twin
GET /realestate
GET /realestatecomponent
GET /buildingcomponent
GET /room
GET /storey
GET /asset
GET /device
GET /sensor
GET /actuator
GET /collection
GET /apartment
GET /tenantunit
GET /system
GET /twin
Breaking changes
Alias filtering on all listed endpoints is now case-sensitive, see above.
Fixes and minor improvements
No additional functionality changes in this release. This update is focused on the alias behavior adjustment.
Per Karlberg
Per Karlberg, a distinguished technology executive, demonstrates deep expertise in the nexus of real estate, technology, and ESG. Holding advanced degrees from Lund University, and with key roles as CEO of our company and Co-Founder of ProptechOS, he has shaped the proptech field through significant contributions to real estate technology advancements. His instrumental work in co-authoring “The realestatecore ontology” has facilitated digital transformation and ESG breakthroughs in the real estate sector.
Read his full bio and information here.