Overview
Use this endpoint to read upcoming events across the projects in a workspace.- Endpoint:
GET https://api.broadcast.events/workspace/events - Auth:
Authorization: Bearer <api-key>
Approach
This endpoint is designed for authenticated workspace integrations that need more context than the public feed. The workspace route uses the API key itself as the boundary:- The key decides which workspace is queried.
- The key can optionally restrict results to a subset of allowed projects.
- Your key determines whether you receive the workspace feed or a promoter project feed.
- The response includes the public event fields plus workspace-specific fields such as publishing metadata, richer ticketing details, related events, and JSON-LD.
meta.projects lists the distinct workspace projects represented in the returned page of results.
Source of truth: Event details can change after you fetch them. We recommend linking end users to the canonical Broadcast event using links.self, and to venue pages or profile links when relevant.
Caching
Responses may be cached for about 15 seconds. Changes to events or project membership may take a short time to appear in your feed.Access and authentication
This API is currently available on request. Contact
support@broadcast.events to enable access
for your workspace.
Raw HTTP
workspace.events.read scope.
Query parameters
Notes:
- Ticketmaster affiliate wrapping is disabled for this route.
- UTM parameters are enabled by default unless you pass
disableUtmLinks=true. - For the default workspace feed, invalid or non-positive
limitvalues fall back to50. - For the promoter project feed,
limitmust be a positive whole number. An empty or invalid value returns400; values above100are capped at100. Unsupported or duplicate query parameters also return400.
Promoter project feed
The promoter project feed returns published upcoming and ongoing events from the promoter projects your key can access. Drafts, past events, and templates are excluded. Ask your workspace administrator to select Promoter projects as the key’s Workspace event feed and choose the projects you need. Use the same endpoint, request parameters, and response format shown below. You do not need any additional query parameters. If your key covers multiple promoter projects, their events are combined without duplicates.meta.projects lists the promoter projects represented in the response. If there are no matching events, data is an empty list.
Example request
Example response
Use the copy control on the code block to grab the full JSON.Example response
Response fields
Empty values are omitted from the response, so some optional fields may be missing.At a glance
Response meta
meta.projects[]
Event object
The workspace event object starts with the public event shape and adds a few workspace-specific fields.timing
classification
attendance
attendance.price
attendance.callToAction
location
location.venue
location.venue.address
location.venue.geo
location.venue.links
location.venue.profile
media
Image asset
image.variants
media.embeds[]
links
Event meta
source
relatedEvents
structuredData
Error responses
Notes
- The workspace feed merges venue, promoter, and festival projects; the promoter project feed includes linked promoter events only.
- Events are deduped by event id and sorted by start time before the final limit is applied.
meta.projectsreflects the projects represented in the current returned slice, not every project in the workspace.- The route is workspace-scoped and intended for richer internal integrations than the public feed.