Sections of an Arrangement, derived from its chord chart
| Property | Value |
|---|---|
| Product | Services (pco.services, API version 2018-11-01) |
| Resource type | ArrangementSections |
| TypeScript | Services.ArrangementSections, attributes Services.ArrangementSectionsAttributes, schema Services.ArrangementSectionsSchema |
| Planning Center path | /services/v2/songs/{song_id}/arrangements/{arrangement_id}/sections |
| Planning Center docs | ArrangementSections |
How to reach it
| Client path | Returns | Filters | Create |
|---|---|---|---|
pco.services.songs.id(songId).arrangements.id(arrangementId).sections |
Single resource | No |
Collections support where, include, order, and pagination; single resources have get().
Attributes
On Services.ArrangementSectionsAttributes. Every resource also has id and type ('ArrangementSections') next to its attributes.
| Name | Type | Description |
|---|---|---|
sections |
unknown[] | null |
See details. |
Attribute details
sections
Given an arrangement with the folowing chord_chart:
VERSE 1
D Bm G D
Be thou my vision O Lord of my heart
A Bm G A
naught be all else to me save that Thou artThe value will be:
[
{
"label": "Verse",
"lyrics": "Be thou my vision O Lord of my heart
naught be all else to me save that Thou art",
"breaks_at": null
}
]Querying
No documented where fields.
No documented order fields.
Edges
This resource has no documented edges.
Writing
| Property | Value |
|---|---|
| Create | No |
| Update | No |
| Delete | No |
Example
import type { Services } from '@mackenly/planningcenterkit';
function describe(resource: Services.ArrangementSections): string {
return `${resource.type} ${resource.id}`;
}