Brella (BYOK)

Brella (BYOK) — connector documentation

• MCP endpoint: https://byok-brella.connectorbay.com/mcp
• REST API: POST https://byok-brella.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-brella.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Brella Brella Core API organization token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-brella.connectorbay.com/health · Tool schemas: https://byok-brella.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-brella · agent@connectorbay.com

What Brella (BYOK) is for

Brella (BYOK) lets an AI assistant read your own Brella data through the Brella API with a key you supply (Brella Core API organization token). Read-only: 12 tools (list_events, list_event_analytics, get_ticket_sales_analytics, get_event_timeline_analytics, get_event_benchmarks, list_content_sessions, list_session_analytics, list_sponsors, list_sponsor_categories, list_tracks, list_ticket_types, list_announcements). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.brella.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brella. Brella and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which Brella events do we have this year?"
• "How many meetings were accepted at each of our Brella events?"
• "How much ticket revenue did our Brella event bring in?"
• "How did joined registrants build up before the Brella event?"
• "How does the meeting acceptance rate compare across our last three Brella events?"
• "What sessions are scheduled on the main track of my Brella event?"

What it does

• list_events: List the organization's events. Which fields come back is set by the token's scopes. Returns JSON:API records, paged.
• list_event_analytics: Aggregate event metrics per event: registrations, networking opt-in, meetings, chat, leads, sessions, sponsors and booth traffic. Counts and rates only.
• get_ticket_sales_analytics: Ticket sales totals per event: purchase counts by status, revenue per currency in minor units, tickets sold, discount codes, purchases by type and source.
• get_event_timeline_analytics: Cumulative registration and engagement points over time for one event, by day, week or month. Points are cumulative and should not be summed.
• get_event_benchmarks: Compare engagement metrics (seat claim rate, networking opt-in, meeting acceptance and similar) across at least two of your events.
• list_content_sessions: List an event's schedule sessions with title, time, track, capacity and RSVP counts as allowed by the token's scopes. Paged.
• list_session_analytics: Per-session engagement metrics for an event: bookmarks, RSVPs, check-ins, tracked viewers and average rating.
• list_sponsors: List an event's sponsors and exhibitors (company-level data) with category, level and booth settings as allowed by the token's scopes.
• list_sponsor_categories: List an event's sponsor categories with level, position and sponsor count.
• list_tracks: List an event's content tracks with name, colour, position and whether they are enabled.
• list_ticket_types: List an event's ticket types with attendance type, networking and lead-scanning settings and registrant counts.
• list_announcements: List an event's announcements with heading, delivery mode, schedule and sent and seen counts.

BYOK key

You bring your own Brella Brella Core API organization token (https://docs.brella.io/getting-started/token-scopes#create-a-token-and-configure-its-scopes). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.brella.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.brella.io/getting-started/authentication (the API this connector calls, with a BYOK key)

Live from the Brella API (api.brella.io) with a BYOK key; documentation: https://docs.brella.io/getting-started/authentication. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brella. Brella and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Brella account.

Built for: Worldwide. Languages: English.

Brella (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Brella (BYOK) is. Brella (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Brella data: Read your Brella event-networking data: events, schedule sessions, tracks, sponsors, ticket types, announcements and event, ticket-sales and session analytics with your own organization token. You bring your own Brella Brella Core API organization token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Brella call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.brella.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Brella rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Brella receives. The request we make on your behalf, including the key and the arguments, under Brella's own terms and privacy policy. Brella acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Brella gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Brella data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Brella (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Brella at any time to end all access.

Children. Brella (BYOK) is a general-audience service operated by the adult using the assistant, under Brella's own age rules.

Changes. We will post changes here with a new effective date.

Brella (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Brella (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Brella (BYOK) provides: Read your Brella event-networking data: events, schedule sessions, tracks, sponsors, ticket types, announcements and event, ticket-sales and session analytics with your own organization token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Brella credentials and only access data you are allowed to access. Brella's terms apply to your use of Brella; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Brella. Brella and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Brella returns, lightly trimmed; it may be incomplete, delayed or changed by Brella. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Brella account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Brella's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Brella may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Brella key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Brella takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-brella

Brella (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-brella.connectorbay.com/mcp
• REST API: https://byok-brella.connectorbay.com/openapi.json
• Live status: https://byok-brella.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Brella (BYOK) never asks for them.