Channels

Channels allow you to pre-assign groups of seats to specific users or user groups, such as sponsor employees, VIPs, or guests. This feature enables you to restrict access to certain seats for regular ticket buyers while making them available through specialized ticketing interfaces (such as an intranet).

Overview

When seats are assigned to a channel, they become unavailable for selection by default. These seats can only be selected and booked when the appropriate channel key is provided, either when rendering the seating chart or when making booking requests.

Channel Properties

Each channel has the following properties:

• name: A human-readable identifier used only within the Event Manager interface
• key: A unique identifier for the channel, used in management API operations (e.g. adding or removing objects)
• id: A read-only UUID that serves as the public identifier for the channel
• color (optional): A visual indicator used only within the Event Manager interface
• index (optional): A number that indicates the ordering of channels; index is used in the Event Manager interface
• objects (optional): An array of objects assigned to the channel. GA areas listed here are assigned as a whole.
• areaPlaces (optional): A map of GA area label to the number of places within that area assigned to the channel. Allows partial assignment of a GA area's capacity to a channel. A GA area cannot appear in both objects and areaPlaces. See General Admission Area Places on Channels.

Important: Channel names and colors are never exposed to end users. Only the id is shared with ticket buyers.

General admission area places on channels

note

Area places on channels is a beta feature and is disabled by default. It must be enabled in the workspace or company settings.

When you assign a specific number of places from a GA area to a channel using areaPlaces, a partition is created for that area. This partition behaves like a regular GA area object, but only covers the assigned number of places.

For example, if an area GA1 has a capacity of 100 places and you assign 5 places to channel1, a partition of 5 places is created — leaving 95 places in the original area.

Partition identifier

The partition's object identifier follows this format:

<original area label>##<channel id>

For example, if GA1 is assigned to a channel with id "a1b2c3d4-...", the partition identifier would be GA1##a1b2c3d4-....

You must use this partition identifier when holding or booking places via the API. For example, when booking objects, pass the partition identifier instead of the original GA area label. And of course, the channel secret key is required as well.

All server-side SDKs provide a convenience method on the Channel object to compute this identifier:

PHP

$channel->areaPartitionLabel('GA1') // returns "GA1##<channel id>"

C#

channel.AreaPartitionLabel("GA1") // returns "GA1##<channel id>"

Java

channel.areaPartitionLabel("GA1") // returns "GA1##<channel id>"

Python

channel.area_partition_label('GA1') # returns "GA1##<channel id>"

Ruby

channel.area_partition_label('GA1') # returns "GA1##<channel id>"

Javascript

channel.areaPartitionLabel('GA1') // returns "GA1##<channel id>"

Go

channel.AreaPartitionLabel("GA1") // returns "GA1##<channel id>"

API Endpoints

For detailed information about channel management endpoints, see:

• Replace channels on an Event
• Add a channel
• Remove a channel
• Update a channel
• Add Objects to a channel
• Remove Objects from a channel