Skip to content

ResourceBooking (Calendar)

A specific booking of a room or resource for an event instance.

A specific booking of a room or resource for an event instance.

Property Value
Product Calendar (pco.calendar, API version 2026-06-22)
Resource type ResourceBooking
TypeScript Calendar.ResourceBooking, attributes Calendar.ResourceBookingAttributes, schema Calendar.ResourceBookingSchema
Planning Center path /calendar/v2/resource_bookings
Planning Center docs ResourceBooking

How to reach it

Client path Returns Filters Create
pco.calendar.resource_bookings Collection approved, approved_conflict, approved_pending, approved_pending_conflict, approved_pending_rejected, approved_pending_rejected_conflict, approved_rejected, approved_rejected_conflict, conflict, future, pending, pending_conflict, pending_rejected, pending_rejected_conflict, rejected, rejected_conflict, resources, rooms No
pco.calendar.events.id(eventId).resource_bookings Collection future No
pco.calendar.event_instances.id(eventInstanceId).resource_bookings Collection future, resources, rooms No
pco.calendar.event_resource_requests.id(eventResourceRequestId).resource_bookings Collection approved, approved_conflict, approved_pending, approved_pending_conflict, approved_pending_rejected, approved_pending_rejected_conflict, approved_rejected, approved_rejected_conflict, conflict, future, pending, pending_conflict, pending_rejected, pending_rejected_conflict, rejected, rejected_conflict No
pco.calendar.resources.id(resourceId).resource_bookings Collection approved, approved_conflict, approved_pending, approved_pending_conflict, approved_pending_rejected, approved_pending_rejected_conflict, approved_rejected, approved_rejected_conflict, conflict, future, pending, pending_conflict, pending_rejected, pending_rejected_conflict, rejected, rejected_conflict No

From a collection, .id(resourceBookingId) addresses one ResourceBooking: pco.calendar.resource_bookings.id(resourceBookingId). Collections support where, include, order, and pagination; single resources have get().

Attributes

On Calendar.ResourceBookingAttributes. Every resource also has id and type ('ResourceBooking') next to its attributes.

Name Type Description
created_at string | null UTC time at which the booking was created
ends_at string | null UTC time at which usage of the booked room or resource ends
quantity number | null The quantity of the rooms or resources booked
starts_at string | null UTC time at which usage of the booked room or resource starts
updated_at string | null UTC time at which the booking was updated

Relationships and includes

Side-load with include() (or get({ include })) and read with related(resource, name): event_resource_request, resource.

Relationship Type To Includable
event To one Event No
event_instance To one EventInstance No
resource To one Resource Yes

Querying

Where

where(field, value) for equality; where(field, op, value) with the operators listed.

Field Value type Operators
created_at string | Date gt, gte, lt, lte
ends_at string | Date gt, gte, lt, lte
starts_at string | Date gt, gte, lt, lte
updated_at string | Date gt, gte, lt, lte

Order

order(...) accepts these fields, ascending, or descending with a - prefix: created_at, ends_at, starts_at, updated_at.

Filters

filter(...) names depend on the edge you query through:

Edge Filters
pco.calendar.resource_bookings approved, approved_conflict, approved_pending, approved_pending_conflict, approved_pending_rejected, approved_pending_rejected_conflict, approved_rejected, approved_rejected_conflict, conflict, future, pending, pending_conflict, pending_rejected, pending_rejected_conflict, rejected, rejected_conflict, resources, rooms
resource_bookings on Event future
resource_bookings on EventInstance future, resources, rooms
resource_bookings on EventResourceRequest approved, approved_conflict, approved_pending, approved_pending_conflict, approved_pending_rejected, approved_pending_rejected_conflict, approved_rejected, approved_rejected_conflict, conflict, future, pending, pending_conflict, pending_rejected, pending_rejected_conflict, rejected, rejected_conflict
resource_bookings on Resource approved, approved_conflict, approved_pending, approved_pending_conflict, approved_pending_rejected, approved_pending_rejected_conflict, approved_rejected, approved_rejected_conflict, conflict, future, pending, pending_conflict, pending_rejected, pending_rejected_conflict, rejected, rejected_conflict

Edges

Follow these from one ResourceBooking, ref = pco.calendar.resource_bookings.id(resourceBookingId):

Edge Leads to Returns Filters Create
ref.event_resource_request EventResourceRequest Collection No
ref.resource Resource Collection No

Writing

Property Value
Create No
Update No
Delete No

Example

import type { Calendar } from '@mackenly/planningcenterkit';

const page = await pco.calendar.resource_bookings.order('created_at').perPage(25).list();
const items: Calendar.ResourceBooking[] = page.data;

Type to search…

↑↓ navigate↵ selectEsc close