splose (BYOK)

splose (BYOK) — connector documentation

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

What splose (BYOK) is for

splose (BYOK) lets an AI assistant read your own splose data through the splose API with a key you supply (splose API key). Read-only: 12 tools (get_api_key_owner, list_services, list_locations, list_practitioners, list_appointments, list_invoices, list_payments, list_credit_notes, list_payment_methods, list_cancellation_reasons, list_busy_times, get_practitioner_availability). 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.splose.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by splose. splose 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 splose workspace is my API key connected to?"
• "What services does my splose practice offer and what do they cost?"
• "Which locations does my splose practice have?"
• "Which practitioners are active in my splose practice?"
• "What appointments are booked at my splose practice next week?"
• "Which invoices are still awaiting payment at my splose practice?"

What it does

• get_api_key_owner: Show which splose organisation and practitioner the API key belongs to and when the key expires.
• list_services: List the practice's services (appointment types and support activities) with type, code, duration, price, group size and tags.
• list_locations: List the practice's locations with address, phone, timezone and whether online booking is on.
• list_practitioners: List practitioners (staff) with profession, role, active flag and timezone. Contact details and provider numbers are not returned.
• list_appointments: List appointments (time, service, location, practitioner, price, group size) without patient details, optionally limited to a period or practitioner.
• list_invoices: List invoices with number, dates, location, practitioner, subtotal, tax, total, paid amount and status. Patient and contact ids are not returned.
• list_payments: List payments received with number, amount, date, location and payment method id. Patient ids are not returned.
• list_credit_notes: List credit notes with number, linked invoice, subtotal, tax, total and sent status. Patient ids are not returned.
• list_payment_methods: List the payment methods configured in the practice (name and description).
• list_cancellation_reasons: List the cancellation reasons that can be recorded against appointments.
• list_busy_times: List blocked-out busy times (start, end, location, practitioners, type) without notes.
• get_practitioner_availability: List a practitioner's working availability (date, location, start and end time) for a period of at most 100 days.

BYOK key

You bring your own splose splose API key (https://docs.splose.com/introduction). 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.splose.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.

Notices

Business and scheduling data only: patient and contact records, clinical notes and patient ids are not exposed by these tools. Covers the Australian server; UK workspaces (api-uk.splose.com) are not supported.

Data sources

• https://docs.splose.com/introduction (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

splose (BYOK) — Privacy Policy

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

What splose (BYOK) is. splose (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own splose data: Read your splose practice's services, locations, practitioners, appointment slots, invoices, payments and availability with your own API key. You bring your own splose splose API key; the assistant sends it to us with each request.

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

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

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

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

splose (BYOK) — Terms of Service

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

1. The Service. splose (BYOK) provides: Read your splose practice's services, locations, practitioners, appointment slots, invoices, payments and availability 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 splose credentials and only access data you are allowed to access. splose's terms apply to your use of splose; 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 splose. splose 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 splose returns, lightly trimmed; it may be incomplete, delayed or changed by splose. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your splose 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 splose'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; splose 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 splose 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 splose 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-splose

splose (BYOK) support

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

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