Apono (BYOK)

Apono (BYOK) — connector documentation

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

What Apono (BYOK) is for

Apono (BYOK) lets an AI assistant read your own Apono data through the Apono API with a key you supply (Apono personal API token). Read-only: 9 tools (list_integrations, list_connectors, list_access_flows, list_bundles, list_spaces, list_access_scopes, list_space_scopes, list_groups, list_activity_reports). 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.apono.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Apono. Apono 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 integrations are connected to Apono and when did they last sync?"
• "Are all my Apono connectors up to date and connected?"
• "Which access flows require MFA and how long do they grant access?"
• "What access bundles exist in Apono?"
• "Which spaces are set up in Apono?"
• "Which access scopes are defined and what do they select?"

What it does

• list_integrations: List the systems Apono manages access for (cloud accounts, databases, SaaS) with type, category, status, connector and last sync time.
• list_connectors: List Apono connectors (the agents that reach your systems) with status, version, whether they are on the latest version, cloud provider and last connection time.
• list_access_flows: List access flows (the rules for who may request what, for how long and who approves) with trigger, approval mode, grant duration and MFA settings.
• list_bundles: List access bundles (named sets of permissions that can be requested together) with description, space and update date.
• list_spaces: List Apono spaces (administrative areas that own flows, bundles and scopes) with their creation and update dates.
• list_access_scopes: List access scopes (saved resource queries used in access flows) with their query text and space.
• list_space_scopes: List space scopes (the resource queries that limit what a space may manage) with their query text.
• list_groups: List groups Apono knows from connected identity sources, with the integration each group comes from.
• list_activity_reports: List saved activity reports (name, output format, fields included, schedule and update date) without their recipients.

BYOK key

You bring your own Apono Apono personal API token (https://docs.apono.io/api-reference/api-overview/api-authentication). 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.apono.io 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.apono.io/api-reference/api-overview/readme (the API this connector calls, with a BYOK key)

Live from the Apono API (api.apono.io) with a BYOK key; documentation: https://docs.apono.io/api-reference/api-overview/readme. 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 Apono. Apono 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 Apono account.

Built for: Worldwide. Languages: English.

Apono (BYOK) — Privacy Policy

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

What Apono (BYOK) is. Apono (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Apono data: Read your Apono just-in-time access setup: integrations, connectors, access flows, bundles, spaces, scopes, groups and activity reports with your own API token. You bring your own Apono Apono personal API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Apono 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.apono.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Apono 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 Apono receives. The request we make on your behalf, including the key and the arguments, under Apono's own terms and privacy policy. Apono acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Apono (BYOK) — Terms of Service

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

1. The Service. Apono (BYOK) provides: Read your Apono just-in-time access setup: integrations, connectors, access flows, bundles, spaces, scopes, groups and activity reports with your own API token. 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 Apono credentials and only access data you are allowed to access. Apono's terms apply to your use of Apono; 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 Apono. Apono 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 Apono returns, lightly trimmed; it may be incomplete, delayed or changed by Apono. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Apono 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 Apono'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; Apono 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 Apono 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 Apono 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-apono

Apono (BYOK) support

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

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