Skip to main content
PUT
Set the status of a building
A new building is UNPUBLISHED. The building keeps this status in published (true for PUBLISHED) until you change it again. The values are case-sensitive. Sending the status the building already has returns 409, so a repeated call is not safe to treat as a no-op. The status does not delete any data. If your service account’s role limits access to published buildings, an unpublished building returns 403 on reads, including Get a building and Get a job. Publishing and unpublishing still work in that case.

Authorizations

Authorization
string
header
required

Paste an access token from Create an access token. Tokens expire, so request a new one if you receive 401.

Path Parameters

buildingId
string
required

Building identifier from List buildings.

Body

application/json
status
string
required
Pattern: ^(PUBLISHED|UNPUBLISHED)$

Response

The building with its new status.

_id
string
organizationId
string
createdAt
string
read-only

Date and time in UTC, with a numeric offset and no colon, for example 2026-10-28T13:51:31+0000.

Example:

"2026-10-28T13:51:31+0000"

updatedAt
string
read-only

Date and time in UTC, with a numeric offset and no colon, for example 2026-10-28T13:51:31+0000.

Example:

"2026-10-28T13:51:31+0000"

name
string
identifier
string
area
object
yearBuild
integer<int32>
primaryFunction
string
tags
string[]
address
object
picture
string
tz
string
areasCount
integer<int32>
devicesCount
integer<int32>
connectorsCount
integer<int32>
systemsCount
integer<int32>
pointsCount
integer<int32>
stats
object
baseTemp
number<double>
published
boolean
ossEnabled
boolean
climateZone
object
region
string
brand
string
zone
string
district
string
phoneNumber
string
site
object
products
object[]