Improvement·Sun Sep 13·2026-09-14

Room and location image removal

Authorized venue admins can clear a room floor-plan reference through the room setup API. New floor-plan URLs still require the signed upload and finalize flow; a direct URL cannot be attached through room PATCH.

Location setup also supports removing one exact saved gallery image while keeping the remaining images in order, including images previously uploaded through BookingBible. This operation compares the saved gallery before writing. If another admin changes the gallery at the same time, reload and retry instead of overwriting their change. Removing an already absent image is safe to repeat.

These operations remove catalog references, not stored files. They do not delete bookings, client records, locations or rooms and do not send customer messages. Room changes still require `settings.business`; location changes require `locations.manage`. Both use the existing tenant-scoped, staff-JWT and idempotency controls.

Existing web image controls are unchanged. Native Business controls are a required companion still under implementation; this API change does not establish device or store parity. Consumer, Branded and published Sites remain read-only catalog consumers and do not receive staff tools. Location provisioning, billing and primary-location changes are not part of these APIs. Native owner-defined custom terminology remains a separate gap.

Next update

Public appointment team listings

Public venue team listings can include active service providers and instructors, including a delivery capability on another primary role. A generic staff account is not automatically a public professional. The venue's public-listing setting and professional collaboration withdrawals remain authoritative.

Authorized venue admins can clear a room floor-plan reference through the room setup API. New floor-plan URLs still require the signed upload and finalize flow; a direct URL cannot be attached through room PATCH. Location setup also supports removing one exact saved gallery image while keeping the remaining images in order, including images previously uploaded through BookingBible. This operation compares the saved gallery before writing. If another admin changes the gallery at the same time, reload and retry instead of overwriting their change. Removing an already absent image is safe to repeat. These operations remove catalog references, not stored files. They do not delete bookings, client records, locations or rooms and do not send customer messages. Room changes still require `settings.business`; location changes require `locations.manage`. Both use the existing tenant-scoped, staff-JWT and idempotency controls. Existing web image controls are unchanged. Native Business controls are a required companion still under implementation; this API change does not establish device or store parity. Consumer, Branded and published Sites remain read-only catalog consumers and do not receive staff tools. Location provisioning, billing and primary-location changes are not part of these APIs. Native owner-defined custom terminology remains a separate gap.

All updates

Improvement·Sun Sep 13·2026-09-14

Room and location image removal

Authorized venue admins can clear a room floor-plan reference through the room setup API. New floor-plan URLs still require the signed upload and finalize flow; a direct URL cannot be attached through room PATCH.

Location setup also supports removing one exact saved gallery image while keeping the remaining images in order, including images previously uploaded through BookingBible. This operation compares the saved gallery before writing. If another admin changes the gallery at the same time, reload and retry instead of overwriting their change. Removing an already absent image is safe to repeat.

These operations remove catalog references, not stored files. They do not delete bookings, client records, locations or rooms and do not send customer messages. Room changes still require `settings.business`; location changes require `locations.manage`. Both use the existing tenant-scoped, staff-JWT and idempotency controls.

Existing web image controls are unchanged. Native Business controls are a required companion still under implementation; this API change does not establish device or store parity. Consumer, Branded and published Sites remain read-only catalog consumers and do not receive staff tools. Location provisioning, billing and primary-location changes are not part of these APIs. Native owner-defined custom terminology remains a separate gap.

Next update