Performance seating
get_performance_seatingRead-onlyIdempotent
Retrieve seating availability for a performance, including groups with capacity and remaining seats, and optionally individual available seats with price band and seat type.
Instructions
Seating availability for one performance: the seating groups (areas, sections, blocks, rows) with capacity and capacity remaining, from GET /performance/{id}/seating-group/, and optionally the individual available seats (seating objects with price band, seat type and group) from GET /performance/{id}/seating-object/. Seat lists can be large, so seats are off by default and capped by max_seats; a per-group summary is always included when seats are fetched.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| codes | No | Values for the API's `code` parameter (repeated). The spec types it as a list of strings and does not say what it does. | |
| max_seats | No | Most individual seats to return (the endpoint is not paged; the rest are summarised) | |
| package_id | No | Seats priced for this package (API parameter `package_id` on seating-object; only with include_seats) | |
| parent_ids | No | Only groups/seats under these seating groups (API parameter `parent_id`, repeated, on both endpoints) | |
| include_root | No | Include the top-level groups (API parameter `include_root` on seating-group; the API's default is true) | |
| include_seats | No | Also fetch the individual available seats | |
| performance_id | Yes | Performance ID (a positive whole number) | |
| include_contact_details | No | Include email addresses and phone numbers typed into seating group labels. Off by default: email addresses and phone numbers typed into any text field (names, descriptions, notes, labels, references) are replaced with [email redacted] / [phone redacted]. |