Yoco (BYOK)

Yoco (BYOK) — connector documentation

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

What Yoco (BYOK) is for

Yoco (BYOK) lets an AI assistant read your own Yoco data through the Yoco API with a key you supply (personal application API key with read scopes (business/orders:read, business/payouts:read, business/locations:read, business/devices:read)). Read-only: 11 tools (list_payments, get_payment, list_orders, get_order, list_refunds, list_payouts, get_payout, list_payout_entries, list_payment_links, list_locations, list_card_machines). 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.yoco.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Yoco. Yoco 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 payments did my Yoco business take this week?"
• "Show Yoco payment 1732194482873-c777dc85"
• "Which Yoco orders were completed today?"
• "Show Yoco order 1585232943682-9f7e"
• "Which refunds did Yoco process recently?"
• "When were my last Yoco payouts and how much?"

What it does

• list_payments: List payments (card, instant EFT, cash) with status, method, source, receipt number and total, tip and refunded amounts in cents. Needs the business/orders:read scope.
• get_payment: Get one payment by id with status, method, source, receipt number and amounts in cents.
• list_orders: List orders with status, order number, location, channel and gross, discount, tax, tip and net amounts in cents. Needs the business/orders:read scope.
• get_order: Get one order by id with status, timestamps and gross, discount, tax, tip and net amounts in cents.
• list_refunds: List refunds with status, type, linked payment, method and amount in cents.
• list_payouts: List payouts to your bank with type, status and gross, fee, net and capital repayment amounts in cents. Needs the business/payouts:read scope.
• get_payout: Get one payout by id with type, status and gross, fee, net amounts in cents.
• list_payout_entries: List the entries that make up one payout (payments, refunds, fees, adjustments) with gross, fee and net amounts, for reconciliation.
• list_payment_links: List payment links with reference, status, URL and linked order.
• list_locations: List the business locations with id and name. Needs the business/locations:read scope.
• list_card_machines: List card machines with nickname, serial number and dates. Needs the business/devices:read scope.

BYOK key

You bring your own Yoco personal application API key with read scopes (business/orders:read, business/payouts:read, business/locations:read, business/devices:read) (https://developer.yoco.com/docs/api/authentication/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 api.yoco.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://developer.yoco.com/api-reference/yoco-api (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

Yoco (BYOK) — Privacy Policy

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

What Yoco (BYOK) is. Yoco (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Yoco data: Read your Yoco business in South Africa: payments, orders, refunds, payouts, payment links, locations and card machines with your own personal API key. You bring your own Yoco personal application API key with read scopes (business/orders:read, business/payouts:read, business/locations:read, business/devices:read); the assistant sends it to us with each request.

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

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

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

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

Yoco (BYOK) — Terms of Service

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

1. The Service. Yoco (BYOK) provides: Read your Yoco business in South Africa: payments, orders, refunds, payouts, payment links, locations and card machines with your own personal 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 Yoco credentials and only access data you are allowed to access. Yoco's terms apply to your use of Yoco; 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 Yoco. Yoco 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 Yoco returns, lightly trimmed; it may be incomplete, delayed or changed by Yoco. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Yoco 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 Yoco'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; Yoco 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 Yoco 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 Yoco 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-yoco

Yoco (BYOK) support

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

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