Website logo
⌘K
API quickstart
Welcome
Forming API requests
Response status codes
Rate-limiting & pagination
How data is structured in Brella
A note on external_id fields
Authentication & API keys
Changelog
Events
Invites
Attendees
RSVP & Session check-in
Get all RSVPs by attendee id
Get all RSVPs by timeslot id
Create RSVP for timeslot
Delete RSVP from timeslot
Sponsors
Speakers
Schedule
Statistics & analytics
Get all meetings & chats by attendee id (cloned)
Get meeting or chat by id
Get tracking sessions by attendee id
Get tracking session slices by attendee id
Webhooks
Docs powered by Archbee
API quickstart

Forming API requests

0min

The Brella API works with json data. Every request made to the API must contain the following three headers:

Brella-API-Access-Token: [APIKEY]

Content-Type: application/json

Accept: application/vnd.brella.v4+json

This API is organized around REST. All request and response bodies, including errors, are encoded in JSON.

Request bodies for POST, PUT and PATCH requests use snake_case for object keys.

Response bodies comply with the JSON API specification.



Updated 15 Nov 2023
Did this page help you?
PREVIOUS
Welcome
NEXT
Response status codes
Docs powered by Archbee
Docs powered by Archbee