Xola (BYOK)

Xola (BYOK) — connector documentation

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

What Xola (BYOK) is for

Xola (BYOK) lets an AI assistant read your own Xola data through the Xola API with a key you supply (Xola API key). Read-only: 9 tools (get_current_user, list_experiences, get_experience, get_upcoming_dates, list_timeslots, list_events, list_purchases, list_coupons, get_transactions_summary). 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 xola.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Xola. Xola 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 Xola account is my key connected to?"
• "Which experiences does my Xola account offer and what do they cost?"
• "Give me the full details of Xola experience exp1"
• "On which dates is experience exp1 available for 4 guests?"
• "What timeslots with free seats does experience exp1 have in November?"
• "How full are my tours next week?"

What it does

• get_current_user: Show the Xola account the key belongs to: id, name, account type and whether it is enabled. Use the id as the seller in other tools.
• list_experiences: List experiences (tours and activities) with name, price, currency, status, excerpt and group size limits. Filter by seller, category, name text or location.
• get_experience: Get one experience with description, price, currency, status, cancellation policy and group limits.
• get_upcoming_dates: List the upcoming dates on which an experience has availability, optionally for a minimum number of seats and from a start date.
• list_timeslots: List bookable timeslots with date, time, open and maximum capacity, privacy, unit prices and whether booking or waitlisting is possible.
• list_events: List scheduled events (departures) with start, end, title, open seats, reserved, confirmed and pending guest counts, privacy and assigned guides.
• list_purchases: List bookings (purchases) with status, customer name, amount, balance, currency and source. Email and phone are not returned. Filter by seller, status or text.
• list_coupons: List coupons with name, type, discount algorithm and amount, usage limit, source and the experiences they cover. Needs a seller or an experience id.
• get_transactions_summary: Summarise transactions: total amount, seller earnings, count, average amount and breakdowns by type and payment method.

BYOK key

You bring your own Xola Xola API key (https://developers.xola.com/). 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 xola.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://developers.xola.com/ (the API this connector calls, with a BYOK key)

Live from the Xola API (xola.com) with a BYOK key; documentation: https://developers.xola.com/. 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 Xola. Xola 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 Xola account.

Built for: Worldwide. Languages: English.

Xola (BYOK) — Privacy Policy

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

What Xola (BYOK) is. Xola (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Xola data: Read your Xola tour and activity business: experiences, open dates, timeslots, events, bookings, coupons and transactions with your own API key. You bring your own Xola Xola API key; the assistant sends it to us with each request.

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

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

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

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

Xola (BYOK) — Terms of Service

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

1. The Service. Xola (BYOK) provides: Read your Xola tour and activity business: experiences, open dates, timeslots, events, bookings, coupons and transactions with your own 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 Xola credentials and only access data you are allowed to access. Xola's terms apply to your use of Xola; 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 Xola. Xola 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 Xola returns, lightly trimmed; it may be incomplete, delayed or changed by Xola. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Xola 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 Xola'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; Xola 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 Xola 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 Xola 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-xola

Xola (BYOK) support

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

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