API changelog

​

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-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).