---
title: "EventResourceRequest (Calendar)"
description: "A room or resource request for a specific event."
---

> Documentation Index
> Fetch the complete documentation index at: https://planningcenterkit.mackenly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# EventResourceRequest (Calendar)

A room or resource request for a specific event.

| Property | Value |
| --- | --- |
| Product | [Calendar](/reference/calendar/) (`pco.calendar`, API version `2026-06-22`) |
| Resource type | `EventResourceRequest` |
| TypeScript | `Calendar.EventResourceRequest`, attributes `Calendar.EventResourceRequestAttributes`, schema `Calendar.EventResourceRequestSchema` |
| Planning Center path | `/calendar/v2/event_resource_requests` |
| Planning Center docs | [EventResourceRequest](https://api.planningcenteronline.com/docs/apps/calendar/versions/2026-06-22/vertices/event_resource_request) |

## How to reach it

| Client path | Returns | Filters | Create |
| --- | --- | --- | --- |
| `pco.calendar.event_resource_requests` | Collection |  | No |
| `pco.calendar.events.id(eventId).event_resource_requests` | Collection |  | No |
| `pco.calendar.people.id(personId).event_resource_requests` | Collection | `awaiting_response`, `future`, `not_in_conflict`, `not_overbooked`, `overbooked` | No |
| `pco.calendar.resources.id(resourceId).event_resource_requests` | Collection |  | No |
| `pco.calendar.resource_approval_groups.id(resourceApprovalGroupId).event_resource_requests` | Collection | `awaiting_response`, `future`, `not_in_conflict`, `not_overbooked`, `overbooked` | No |
| `pco.calendar.resource_bookings.id(resourceBookingId).event_resource_request` | Collection |  | No |

From a collection, `.id(eventResourceRequestId)` addresses one EventResourceRequest: `pco.calendar.event_resource_requests.id(eventResourceRequestId)`. Collections support [`where`, `include`, `order`, and pagination](/guides/querying/); single resources have `get()`.

## Attributes

On `Calendar.EventResourceRequestAttributes`. Every resource also has `id` and `type` (`'EventResourceRequest'`) next to its attributes.

| Name | Type | Description |
| --- | --- | --- |
| `approval_sent` | `boolean \| null` | Whether or not an email has been sent to request approval |
| `approval_status` | `string \| null` | See [details](#approval-status). |
| `created_at` | `string \| null` | UTC time at which request was created |
| `notes` | `string \| null` | Additional information about the room or resource request |
| `quantity` | `number \| null` | How many of the rooms or resources are being requested |
| `updated_at` | `string \| null` | UTC time at which request was updated |
| `visible_on_kiosks` | `boolean \| null` | Whether this resource request is visible on kiosks |

### Attribute details

#### `approval_status` {#approval-status}

Possible values:
- `A`: approved
- `P`: pending
- `R`: rejected

## Relationships and includes

Side-load with `include()` (or `get({ include })`) and read with `related(resource, name)`: `created_by`, `event`, `resource`, `room_setup`, `updated_by`.

| Relationship | Type | To | Includable |
| --- | --- | --- | --- |
| `created_by` | To one | [Person](/reference/calendar/person/) | Yes |
| `event` | To one | [Event](/reference/calendar/event/) | Yes |
| `event_resource_request` | To one | [EventResourceRequest](/reference/calendar/event-resource-request/) | No |
| `resource` | To one | [Resource](/reference/calendar/resource/) | Yes |
| `room_setup` | To one | [RoomSetup](/reference/calendar/room-setup/) | Yes |
| `updated_by` | To one | [Person](/reference/calendar/person/) | Yes |

## Querying

### Where

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

| Field | Value type | Operators |
| --- | --- | --- |
| `approval_sent` | `boolean` | Equality only |
| `approval_status` | `string` | Equality only |
| `created_at` | `string \| Date` | `gt`, `gte`, `lt`, `lte` |
| `updated_at` | `string \| Date` | `gt`, `gte`, `lt`, `lte` |

No documented `order` fields.

### Filters

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

| Edge | Filters |
| --- | --- |
| `event_resource_requests` on [Person](/reference/calendar/person/) | `awaiting_response`, `future`, `not_in_conflict`, `not_overbooked`, `overbooked` |
| `event_resource_requests` on [ResourceApprovalGroup](/reference/calendar/resource-approval-group/) | `awaiting_response`, `future`, `not_in_conflict`, `not_overbooked`, `overbooked` |

## Edges

Follow these from one EventResourceRequest, `ref = pco.calendar.event_resource_requests.id(eventResourceRequestId)`:

| Edge | Leads to | Returns | Filters | Create |
| --- | --- | --- | --- | --- |
| `ref.answers` | [EventResourceAnswer](/reference/calendar/event-resource-answer/) | Collection |  | No |
| `ref.created_by` | [Person](/reference/calendar/person/) | Collection |  | No |
| `ref.event` | [Event](/reference/calendar/event/) | Collection |  | No |
| `ref.resource` | [Resource](/reference/calendar/resource/) | Collection |  | No |
| `ref.resource_bookings` | [ResourceBooking](/reference/calendar/resource-booking/) | 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 |
| `ref.room_setup` | [RoomSetup](/reference/calendar/room-setup/) | Collection |  | No |
| `ref.updated_by` | [Person](/reference/calendar/person/) | Collection |  | No |

## Writing

| Property | Value |
| --- | --- |
| Create | No |
| Update | No |
| Delete | No |

## Example

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

const page = await pco.calendar.event_resource_requests.perPage(25).list();
const items: Calendar.EventResourceRequest[] = page.data;
```

Source: https://planningcenterkit.mackenly.com/reference/calendar/event-resource-request/index.mdx
