Eventbrite (BYOK)

Eventbrite (BYOK) — connector documentation

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

What Eventbrite (BYOK) is for

Eventbrite (BYOK) lets an AI assistant read your own Eventbrite data through the Eventbrite API with a key you supply (private token (personal OAuth token)). Read-only: 10 tools (get_me, list_my_organizations, list_organization_events, get_event, list_event_attendees, list_event_orders, list_organization_orders, list_ticket_classes, list_organization_venues, list_venue_events). 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. Eventbrite 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 Eventbrite account is my token for?"
• "Which Eventbrite organizations do I belong to?"
• "What live Eventbrite events do I have coming up?"
• "What are the details of Eventbrite event 1234567890?"
• "Who is attending Eventbrite event 1234567890?"
• "Which orders were placed for Eventbrite event 1234567890?"

What it does

• get_me: Show the Eventbrite account the private token belongs to: as returned by Eventbrite (the shape of this object is not itemised in the docs, so it is passed through whole).
• list_my_organizations: List the organizations the account belongs to with id, name and vertical. The organization id is needed for the event, order and venue tools.
• list_organization_events: List an organization's events with name, dates, status, capacity and URL, filtered by status and time. Paged by continuation token.
• get_event: Get one event: name, summary, dates and time zone, status, currency, capacity, online flag and URL.
• list_event_attendees: List the attendees (one per ticket) of an event with status, check-in flag, ticket class, order and the attendee's name and email. Contains personal data of ticket holders.
• list_event_orders: List the orders placed for an event with status, buyer name and email, totals and dates. Contains personal data of buyers.
• list_organization_orders: List orders across all events of an organization with status, buyer, event, totals and dates. Contains personal data of buyers.
• list_ticket_classes: List an event's ticket types with name, price, fee, capacity, number sold, sales window and on-sale status.
• list_organization_venues: List an organization's venues with name, address, coordinates and capacity.
• list_venue_events: List the events held at one venue with name, dates and status.

BYOK key

You bring your own Eventbrite private token (personal OAuth 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/api (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

Eventbrite (BYOK) — Privacy Policy

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

What Eventbrite (BYOK) is. Eventbrite (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Eventbrite data: Read your Eventbrite organizations, events, attendees, orders, ticket classes and venues with your own private token (read-only; never creates or changes events). You bring your own Eventbrite private token (personal OAuth token); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Eventbrite 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 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 receives. The request we make on your behalf, including the key and the arguments, under Eventbrite's own terms and privacy policy. Eventbrite 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 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 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 (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 at any time to end all access.

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

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

Eventbrite (BYOK) — Terms of Service

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

1. The Service. Eventbrite (BYOK) provides: Read your Eventbrite organizations, events, attendees, orders, ticket classes and venues with your own private token (read-only; never creates or changes events). 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 credentials and only access data you are allowed to access. Eventbrite's terms apply to your use of Eventbrite; 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. Eventbrite 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 returns, lightly trimmed; it may be incomplete, delayed or changed by Eventbrite. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Eventbrite 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'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 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 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 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

Eventbrite (BYOK) support

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

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