Skip to main content
We operate an open platform at Broadcast and aim to both ingest and push event data to and from different platforms. Its still early days, but in this section we document some of the formats and options currently available.

​
Sending data to Broadcast

The following fields are required in order to send basic events data to Broadcast:
NameTypeDescriptionRequired
nameStringThe descriptive name of the event.Yes
startTimeStringDate and time for when doors open in Full ISO Format. See below for more info on date formatting.Yes
endTimeStringDate and time for when doors close in Full ISO Format. See below for more info on date formatting.Yes
venueIdStringUnique venue id provided by Broadcast.Yes
coverStringA textual label detailing the events costs. Use currency code as a prefix to prices. eg: NOK 400No
freeEntryBooleanMark if entry is free - this aids searching in Broadcast.No
ticketLinkStringFull URL to purchase tickets for the event.No
soldOutBooleanMark if the event is sold out.No
publishedBooleanIf you want to remove an event from Broadcast, you can set this to false and it will set the event status to draft.Yes
tagsArrayAn array of tags, eg ['Rock','Metal','Heavy']. Must contain a minimum of one tag, and a maximum, of three in total totalYes
picStringFull URL to a picture we can import. Format is ideally 16:9 for the best results, but we do employ auto cropping and face detection if this a problem. Optimum dimensions for images is 1920px by 1080pxYes
lastUpdatedStringDate when the event was last updated. This helps up process the import faster and more efficiently. Full ISO Format. See below for more info on date formatting.No
We can, and do, accept more info than this but these are just the basics to get you started.

​
Reading data from Broadcast

If you want to read public upcoming events from Broadcast, use the Public event info API. If you need richer, authenticated workspace-scoped reads, use the Workspace event info API.

​
Date formatting

All Dates/Timestamps must be in full ISO 8601 format with UTC (Z suffix). Example: 2025-05-10T18:00:00.000Z. Time zone offsets (±HH:mm) are not allowed and must be converted to UTC before sending.

​
Input options

We have two main ways to get data in to Broacast via automated feeds

​
Remote API feed

In this scenario you can expose an endpoint where we can retrieve a JSON response containing your events info. We then pick this up and map it the correct formats. If required data is missing then the event is created as a draft in our system.

​
Webhooks

Webhooks can be used to make changes to individual events, or notify us to fetch an updated JSON feed or pretty much anything we want!

​
Mapping data

The fields outlined above are what we prefer to recieve, but we are able to consume data in any format or structure and then map it as required for Broadcast. Likewise we can map our data into any required format so as to send the info on to any other platform.

​
Flexibility is everything!

If what have outlined above doesn’t work for you then please get in touch at support@broadcast.events. We will do everything we can to get a solution in place that works for you and your clients.🤓
Last modified on June 21, 2026