vivenu (BYOK)

vivenu (BYOK) — connector documentation

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

What vivenu (BYOK) is for

vivenu (BYOK) lets an AI assistant read your own vivenu data through the vivenu API with a key you supply (vivenu seller API key (Dashboard, Settings, Developers, API Keys)). Read-only: 9 tools (list_events, get_event, list_tickets, list_transactions, list_products, list_sales_channels, list_price_tables, list_coupon_series, list_subscription_plans). 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 vivenu.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by vivenu. vivenu 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 events do I have in vivenu?"
• "Show vivenu event 507f191e810c19729de860ea"
• "Which tickets were sold for vivenu event 507f191e810c19729de860ea?"
• "What orders came in for vivenu event 507f191e810c19729de860eb?"
• "What products and vouchers do I sell in vivenu?"
• "Which sales channels do I have in vivenu?"

What it does

• list_events: List the events of the seller with name, start, end, venue and ticket capacity, plus the total count. Page with top and skip.
• get_event: Get one event with venue, capacity, ticket groups, ticket types with prices and categories.
• list_tickets: List sold tickets with event, ticket type, category, status, price and seat, without holder names, emails or barcodes. Filter by event and status.
• list_transactions: List orders with event, status, payment status, payment method, currency and amount, without buyer names, emails or addresses. Filter by status, payment status and event.
• list_products: List products such as vouchers, add-ons, donations and memberships with name, type and active flag. Page with top and skip.
• list_sales_channels: List the sales channels (point of sale, distributors, internal back office) with name, type and status.
• list_price_tables: List price tables (price tiers per ticket type and category) with their names.
• list_coupon_series: List coupon series with name, discount type and value, usage limits and validity dates. Coupon codes are not returned.
• list_subscription_plans: List subscription plans with name, pricing policy and variants. Page with top and skip.

BYOK key

You bring your own vivenu vivenu seller API key (Dashboard, Settings, Developers, API Keys) (https://docs.vivenu.com/api/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 vivenu.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://docs.vivenu.com/api/introduction (the API this connector calls, with a BYOK key)

Live from the vivenu API (vivenu.com) with a BYOK key; documentation: https://docs.vivenu.com/api/introduction. 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 vivenu. vivenu 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 vivenu account.

Built for: Worldwide. Languages: English.

vivenu (BYOK) — Privacy Policy

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

What vivenu (BYOK) is. vivenu (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own vivenu data: Read your vivenu ticketing events, ticket types, tickets sold, orders, products and sales channels with your own vivenu API key. You bring your own vivenu vivenu seller API key (Dashboard, Settings, Developers, API Keys); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one vivenu 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 vivenu.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 vivenu 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 vivenu receives. The request we make on your behalf, including the key and the arguments, under vivenu's own terms and privacy policy. vivenu acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

vivenu (BYOK) — Terms of Service

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

1. The Service. vivenu (BYOK) provides: Read your vivenu ticketing events, ticket types, tickets sold, orders, products and sales channels with your own vivenu API key. 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 vivenu credentials and only access data you are allowed to access. vivenu's terms apply to your use of vivenu; 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 vivenu. vivenu 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 vivenu returns, lightly trimmed; it may be incomplete, delayed or changed by vivenu. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your vivenu 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 vivenu'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; vivenu 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 vivenu 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 vivenu 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-vivenu

vivenu (BYOK) support

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

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