---
title: "Live (Services)"
description: "The Live resource in Planning Center Services: how to reach it, its attributes, and what you can query and write."
---

> 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.

# Live (Services)

| Property | Value |
| --- | --- |
| Product | [Services](/reference/services/) (`pco.services`, API version `2018-11-01`) |
| Resource type | `Live` |
| TypeScript | `Services.Live`, attributes `Services.LiveAttributes`, schema `Services.LiveSchema` |
| Planning Center path | `/services/v2/series/{series_id}/plans/{plan_id}/live` |
| Planning Center docs | [Live](https://api.planningcenteronline.com/docs/apps/services/versions/2018-11-01/vertices/live) |

## How to reach it

| Client path | Returns | Filters | Create |
| --- | --- | --- | --- |
| `pco.services.series.id(seriesId).plans.id(planId).live` | Collection |  | No |

From a collection, `.id(liveId)` addresses one Live: `pco.services.series.id(seriesId).plans.id(planId).live.id(liveId)`. Collections support [`where`, `include`, `order`, and pagination](/guides/querying/); single resources have `get()`.

## Attributes

On `Services.LiveAttributes`. Every resource also has `id` and `type` (`'Live'`) next to its attributes.

| Name | Type | Description |
| --- | --- | --- |
| `can_chat` | `boolean \| null` |  |
| `can_control` | `boolean \| null` |  |
| `can_control_video_feed` | `boolean \| null` |  |
| `can_take_control` | `boolean \| null` |  |
| `chat_room_channel` | `string \| null` |  |
| `dates` | `string \| null` |  |
| `live_channel` | `string \| null` |  |
| `series_title` | `string \| null` |  |
| `title` | `string \| null` |  |

## Relationships and includes

Side-load with `include()` (or `get({ include })`) and read with `related(resource, name)`: `controller`, `current_item_time`, `items`, `next_item_time`, `service_type`.

## Querying

No documented `where` fields.

No documented `order` fields.

## Edges

Follow these from one Live, `ref = pco.services.series.id(seriesId).plans.id(planId).live.id(liveId)`:

| Edge | Leads to | Returns | Filters | Create |
| --- | --- | --- | --- | --- |
| `ref.controller` | [Person](/reference/services/person/) | Collection |  | No |
| `ref.current_item_time` | [ItemTime](/reference/services/item-time/) | Collection |  | No |
| `ref.items` | [Item](/reference/services/item/) | Collection |  | No |
| `ref.next_item_time` | [ItemTime](/reference/services/item-time/) | Collection |  | No |
| `ref.service_type` | [ServiceType](/reference/services/service-type/) | Collection |  | No |
| `ref.watchable_plans` | [Plan](/reference/services/plan/) | Collection |  | No |

## Writing

| Property | Value |
| --- | --- |
| Create | Documented, but on no path the client follows |
| Update | Yes, `update()` on a reference |
| Delete | Yes, `delete()` on a reference |

See [Writing data](/guides/writing-data/).

## Actions

Run with `ref.action(name, body?)`. Bodies are untyped: see Planning Center's docs for each action.

| Action | Path | Description |
| --- | --- | --- |
| `go_to_next_item` | `POST /services/v2/series/{series_id}/plans/{plan_id}/live/{live_id}/go_to_next_item` |  |
| `go_to_previous_item` | `POST /services/v2/series/{series_id}/plans/{plan_id}/live/{live_id}/go_to_previous_item` |  |
| `toggle_control` | `POST /services/v2/series/{series_id}/plans/{plan_id}/live/{live_id}/toggle_control` |  |

## Example

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

const seriesId = '1'; // Series id
const planId = '1'; // Plan id

const page = await pco.services.series.id(seriesId).plans.id(planId).live.perPage(25).list();
const items: Services.Live[] = page.data;
```

Source: https://planningcenterkit.mackenly.com/reference/services/live/index.mdx
