The Brella Public API gives your developers your event's schedule, speakers and sponsors as data, so they can build pages in your own design. Reading this data needs no API key, and the API can't change it.
Before you start
A developer builds and hosts the page. Brella provides the data only.
For a ready-made schedule on your website, use the schedule widget instead. See Schedule widget.
Warning: Anyone who knows your event's join code or URL slug can read this data. Sessions restricted to registrant lists are included. Don't put confidential information in sessions, speakers or sponsors.
What the API returns
Sessions: title, subtitle, content, track, locations, tags, speakers, color, cover image, start and end time in UTC, child sessions, and RSVP settings, including approval and waitlist, with the number of registrations. That number counts every registration, also those waiting for approval, on the waitlist or rejected.
Speakers: name, job title, company, photo, bio and the sessions they speak in.
Sponsors: name, logo, cover image, website and social links, category, content and custom fields. Developers can filter sponsors by category and search them by name.
Session sponsors: which sponsors are linked to which sessions.
Give your developer the join code or URL slug
The API identifies your event by its join code or URL slug.
Open Details in the event sidebar.
Under Visibility, copy the code:
Join code if the event is a Public event.
URL slug if the event is Invite only.
Send the code and the developer documentation links to your developer.
If you change the join code or URL slug, the API address changes too. Ask your developer to update the page.
Developer documentation
Limits
Read-only. To add or change data from another system, use Zapier or the Integration API. See Get your Brella API key and event ID.
Session gating doesn't apply. The API also returns sessions restricted to registrant lists. See Restrict a session to specific registrant lists.