How data is structured in Brella

before building your integration, it's important to understand how key data is structured in brella this guide will help explain the hierarchy of various entities organization all your brella events live inside a parent “organization” events most of your event content and settings are inside "events" in brella invites a new invite is created whenever a new registration is created, or a ticket is purchased invites offer the most complete data related to event attendance attendees a new attendee is created whenever a registrant claims an invite and onboards onto the platform the app adoption rate can vary by event, so attendees are not a good measure of event attendance speakers dedicated speaker profiles that event organizers can control these can be linked to content timeslots in the schedule, and displayed in the speakers tab if speakers need to be able to participate in the event, create an invite they can redeem to become an attendee you can give them special permissions and access to networking using user groups sponsors sponsor categories brella offers 3 different sponsor categories (small, medium and large) that can be renamed to suit an event every sponsor company is assigned to one category sponsor companies these are the entities you can manipulate and view via the /sponsors endpoints schedule content timeslots these timeslots in the schedule are used to display information related to your various sessions you can also attach speakers, tags and locations to these timeslots networking timeslots these timeslots are used solely for networking purposes you can attach tags and locations to these timeslots you can't create these via the api just yet webhooks webhooks proactively deliver different data payloads in real time based on specific triggers our api can create, update and delete webhooks