2026-06-22

Booking and conflict endpoints now redact event data for users without access to the event. Clients may receive BookedEvent, BookedEventInstance, and BookedEventTime stubs in place of the full Event / EventInstance / EventTime resources on affected traversals.

OpenAPI Description

Changes

Type	Changes to	Notes
breaking	`bookedeventinstance-resourcebooking-event_instance`	Changed the `event_instance` include type on `/resource_bookings` from `EventInstance` to `BookedEventInstance`, which exposes a booking-safe attribute subset and redacts the event name for users without access to the underlying calendar
breaking	`bookedevent-resourcebooking-event`	Changed the `event` include type on `/resource_bookings` from `Event` to `BookedEvent`, which exposes only the `name` attribute and redacts it for users without access to the underlying calendar
breaking	`bookedeventinstance-conflictgroup-event_instances`	Changed the head of `conflict_groups/:id/event_instances` from `EventInstance` to `BookedEventInstance`, redacting event names for users without calendar access
breaking	`bookedeventtime-bookedeventinstance-event_times`	Changed the head of `/resource_bookings/:id/event_instance/event_times` from `EventTime` to `BookedEventTime`, removing the identifying `name` label and redirecting the `event` include to the redacted `BookedEvent` stub
breaking	`event_time`	Restricted the `name` attribute on event times to users who can view the underlying event
breaking	`conflict_resource_booking`	Changed `event` relationship type on `ConflictResourceBooking` from `Event` to `BookedEvent`
breaking	`conflict_resource_booking`	Changed `event_instance` relationship type on `ConflictResourceBooking` from `EventInstance` to `BookedEventInstance`