Eventbrite Event Content (BYOK)

Eventbrite Event Content (BYOK) — connector documentation

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

What Eventbrite Event Content (BYOK) is for

Eventbrite Event Content (BYOK) lets an AI assistant read your own Eventbrite Event Content data through the Eventbrite Event Content API with a key you supply (Eventbrite private token). Read-only: 7 tools (get_event_description, get_display_settings, get_ticket_buyer_settings, get_structured_content, list_ticket_groups, get_ticket_group, get_event_series). 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 www.eventbriteapi.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Eventbrite Event Content. Eventbrite Event Content 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:

• "What is the full description text of my Eventbrite event 1234567890?"
• "Which details does the public page of my Eventbrite event 1234567890 show?"
• "What confirmation message do buyers of my Eventbrite event 1234567890 see?"
• "What does the listing page content of my Eventbrite event 1234567890 contain?"
• "Which ticket groups does my Eventbrite organization have?"
• "Show the Eventbrite ticket group 1"

What it does

• get_event_description: Get the long HTML description of an event as sent by Eventbrite.
• get_display_settings: Get an event's display settings (which details the public event page shows) as sent by Eventbrite.
• get_ticket_buyer_settings: Get an event's ticket buyer settings (confirmation message, instructions, sales-ended message, redirect and similar) as sent by Eventbrite.
• get_structured_content: Get the latest published structured content (page modules such as text and images) of an event for a purpose such as the listing page, as sent by Eventbrite.
• list_ticket_groups: List an organization's ticket groups (sets of ticket classes used for cross-event discounts) with status filter, as sent by Eventbrite.
• get_ticket_group: Get one ticket group by id: name, status and the ticket class ids it covers per event, as sent by Eventbrite.
• get_event_series: Get the parent event of a recurring series by series id, as sent by Eventbrite.

BYOK key

You bring your own Eventbrite Event Content Eventbrite private token (https://www.eventbrite.com/platform/api-keys). 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 www.eventbriteapi.com 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://www.eventbrite.com/platform/new/api (the API this connector calls, with a BYOK key)

Live from the Eventbrite Event Content API (www.eventbriteapi.com) with a BYOK key; documentation: https://www.eventbrite.com/platform/new/api. 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 Eventbrite Event Content. Eventbrite Event Content 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 Eventbrite Event Content account.

Built for: Worldwide. Languages: English.

Eventbrite Event Content (BYOK) — Privacy Policy

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

What Eventbrite Event Content (BYOK) is. Eventbrite Event Content (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Eventbrite Event Content data: Read Eventbrite event page content and checkout settings (description, display settings, buyer messages, structured content, ticket groups) with your own private token, without attendees or orders. You bring your own Eventbrite Event Content Eventbrite private token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Eventbrite Event Content 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 www.eventbriteapi.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Eventbrite Event Content 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 Eventbrite Event Content receives. The request we make on your behalf, including the key and the arguments, under Eventbrite Event Content's own terms and privacy policy. Eventbrite Event Content acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Eventbrite Event Content 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 Eventbrite Event Content 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. Eventbrite Event Content (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 Eventbrite Event Content at any time to end all access.

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

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

Eventbrite Event Content (BYOK) — Terms of Service

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

1. The Service. Eventbrite Event Content (BYOK) provides: Read Eventbrite event page content and checkout settings (description, display settings, buyer messages, structured content, ticket groups) with your own private token, without attendees or orders. 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 Eventbrite Event Content credentials and only access data you are allowed to access. Eventbrite Event Content's terms apply to your use of Eventbrite Event Content; 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 Eventbrite Event Content. Eventbrite Event Content 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 Eventbrite Event Content returns, lightly trimmed; it may be incomplete, delayed or changed by Eventbrite Event Content. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Eventbrite Event Content 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 Eventbrite Event Content'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; Eventbrite Event Content 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 Eventbrite Event Content 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 Eventbrite Event Content 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-eventbrite-event-content

Eventbrite Event Content (BYOK) support

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

• MCP endpoint: https://byok-eventbrite-event-content.connectorbay.com/mcp
• REST API: https://byok-eventbrite-event-content.connectorbay.com/openapi.json
• Live status: https://byok-eventbrite-event-content.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. Eventbrite Event Content (BYOK) never asks for them.