Skip to main content

Add one or more channels

Adds one or more channels to an event or season, optionally with objects assigned to it.

Note

All seats (or tables, booths or GA places) passed in to this API will be considered as "used seats" for pricing purposes.

Add a single channel

POST https://api-{region}.seatsio.net/events/{eventKey}/channels

Example request body

{
"key": "channel1",
"name": "Channel 1",
"color": "#ED303D",
"index": 1,
"objects": ["A-1", "A-2"]
}

The request body should be a JSON object with these properties:

  • key needs to be unique and is required (UUIDs are a great choice)
  • name needs to be unique and is required
  • color needs to be a valid css color; color is used in the Event Manager, to be able to distinguish different channels. End users (ticket buyers) will not get to see the channel by color.
  • index (optional): a number that indicates the ordering of channels; index is used in the Event Manager, to keep ordering of channels consistent.
  • objects (optional): the full object labels of the objects that need to be assigned to this channel.
Warning

The specified objects will be un-assigned from any previous channels.
That means that if seat A-1 is already assigned to channelA, and you create a new channelB with A-1 assigned to it, it will no longer be assigned to channelA and only be assigned to channelB.

Response

204 - No Content
400 - Bad Request if the request was not valid (e.g. if the channel key you're adding already exists)

Add multiple channels

To add more than one channel in one API call, you can use the same endpoint but post an array of channel objects instead.

POST https://api-{region}.seatsio.net/events/{eventKey}/channels

Example request body

[

{
"key": "channel1",
"name": "Channel 1",
"color": "#ED303D",
"index": 1,
"objects": ["A-1", "A-2"]
},
{
"key": "channel2",
"name": "Channel 2",
"color": "#AABBCC",
"index": 2,
"objects": ["A-3", "A-2"]
},
]

The request body should be a JSON array, containing JSON objects with these properties:

  • key needs to be unique and is required (UUIDs are a great choice)
  • name needs to be unique and is required
  • color needs to be a valid css color; color is used in the Event Manager, to be able to distinguish different channels. End users (ticket buyers) will not get to see the channel by color.
  • index (optional): a number that indicates the ordering of channels; index is used in the Event Manager, to keep ordering of channels consistent.
  • objects (optional): the full object labels of the objects that need to be assigned to this channel.
Warning

The specified objects will be un-assigned from any previous channels.
That means that if seat A-1 is already assigned to channelA, and you create a new channelB with A-1 assigned to it, it will no longer be assigned to channelA and only be assigned to channelB.

Response

204 - No Content
400 - Bad Request if the request was not valid (e.g. the channel keys are not unique)