> ## Documentation Index
> Fetch the complete documentation index at: https://docs.broadcast.events/llms.txt
> Use this file to discover all available pages before exploring further.

# API changelog

> History of changes to Broadcast event HTTP APIs on api.broadcast.events.

<Info>
  We document **meaningful** changes to event API behavior, fields,
  authentication, and limits. Typo fixes in docs alone may not always get an
  entry. For access or questions, email
  [support@broadcast.events](mailto:support@broadcast.events).
</Info>

## How to read this log

* **Additive**: New optional fields, new query parameters, or relaxed validation. Existing clients can keep working if they ignore unknown fields.
* **Breaking**: Removed fields, renamed fields, stricter validation, or auth changes that require you to update your integration.
* **Fix**: Corrects unintended behavior; may still affect you if you relied on the old behavior.

***

## 2026-07-09

* **Additive**: Workspace festival objects may now include `lineupGroups`, an array of all configured lineup group names in display order.
* **Additive**: Workspace festival schedule items may now include `lineupGroup` and `lineupOrder` when a festival has manually configured lineup groups. These fields help integrations render lineup-style groupings such as headliners and support acts. They do not change schedule timing or stage values.

## 2026-07-03

* **Additive**: Workspace festival responses now include `dateDisplayMode`, describing how schedule dates should be interpreted.
* **Additive**: Published schedule `timing` objects now include `day` (`YYYY-MM-DD` or `TBC`) and `time` (`HH:mm` or `TBC`) in the festival timezone (`Europe/Oslo`).
* **Breaking**: Schedule `timing` now respects the festival date display setting. For `date_tbc` and `tbc_tbc` modes, ISO and Unix clock fields (`startTime`, `endTime`, `startTimestamp`, `endTimestamp`) are omitted and replaced with `TBC` placeholders where applicable.
* **Breaking**: Schedule `endTime` and `endTimestamp` are now returned only when the festival has `showEndTime` enabled in app settings. Integrations that relied on end times without checking this setting must read them only when present or enable the setting on the festival.

## 2026-06-20

* **Additive**: Workspace festival responses now include `links.ticketing` when a festival has a public ticket link enabled.
* **Additive**: Workspace festival schedule linked events now include `classification`, `attendance`, and `media.image` when available.
* **Behavior**: Workspace festival `links.website` and `links.ticketing` are returned without Broadcast UTM parameters by default. Pass `disableUtmLinks=false` to opt into Broadcast UTM parameters.

## 2026-06-18

* **Docs**: Published documentation for `GET /workspace/festivals`, the authenticated workspace-scoped festival feed on `api.broadcast.events`.
* **Docs**: Documented workspace auth requirements (`workspace.events.read`), the `workspaceFestivalStandard` response shape, festival project metadata, and schedule timing behavior for published lineups.

## 2026-05-04

* **Docs**: Published documentation for `GET /workspace/events`, the authenticated workspace-scoped event feed on `api.broadcast.events`.
* **Docs**: Documented workspace auth requirements (`workspace.events.read`), supported query parameters (`limit`, `disableUtmLinks`), response metadata, and the richer `workspaceStandard` event shape.
* **Additive**: Workspace event responses now include `meta.featuredProjectIds` and `meta.featuredProjects`, listing the distinct workspace projects represented in the returned page of results with ids and names.
* **Behavior**: Clarified current link behavior for the workspace route. Ticketmaster affiliate wrapping is disabled, while Broadcast UTM parameters remain enabled by default unless you pass `disableUtmLinks=true`.
* **Behavior**: Clarified that the route merges upcoming events across workspace venues, promoters, and festivals, then dedupes by event id and sorts by start time before applying the final limit.

## 2026-03-20

* **Docs**: Initial published documentation for `GET /public/events` (public event feed on `api.broadcast.events`), including response shape and access model.
* **Docs**: Described product approach (cached bulk feed, client-side filtering, link back to Broadcast for latest details), caching expectations by tier (free \~5 minutes, paid shorter, realtime on request with pricing TBC).
* **Behavior**: Public events feed cache revalidation aligned to **5 minutes** for the current implementation (free-tier target; shorter paid or custom TTLs can be agreed separately).