- title String / the title of the session happening in this timeslot
- start_time DateTime / the start date and time; see notes for more information on formatting
- end_time DateTime / the start date and time; see notes for more information on formatting
- external_id String / see notes for more information
- tags List / if not used, an empty list  must be sent
01: start_time and end_time must be specified in the following format:
- eg: 2029-06-10T14:30:00+0200
- The timezone of the event must be specified accurately, as the API will pass data in UTC time. In the example above +0200 refers to Helsinki time.
- Make sure that the date and time are within the event dates specified in Brella (if your event dates aren't correctly set-up in Brella, first do so via the Admin Panel (Event > Details).
- You may need to do some formatting within your integration before passing this data to Brella
02: track is not technically required, but is highly recommended when passing timeslots via the API — especially if multiple sessions take place simultaneously. A single track cannot have overlapping sessions — the endpoint will return an error if this is the case.
- If the track attribute is empty / not passed, Brella will automatically re-assign the timeslot being updated by the request to the default track.
- The tracks can be existing schedule tracks (created in the Admin Panel), or tracks that do not exist. If the value passed in the track attribute doesn't match an existing track's name, Brella will create a new track named with the value of the track attribute in the request and assign the timeslot there.
03: external_id is not technically required, but is highly recommended when passing timeslots via the API. This value is used to update timeslots, and to find specific timeslots via the API. Typically, it would contain a shared value between the 3rd party system the data is coming from and Brella (eg: you could pass the unique identifier generated by the 3rd party system to the external_id attribute in Brella..