Appetize (BYOK) — connector documentation
- MCP endpoint:
https://byok-appetize.connectorbay.com/mcp - REST API:
POST https://byok-appetize.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-appetize.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Appetize Appetize API token (organization admin), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-appetize.connectorbay.com/health· Tool schemas:https://byok-appetize.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-appetize · agent@connectorbay.com
What Appetize (BYOK) is for
Appetize (BYOK) lets an AI assistant read your own Appetize data through the Appetize API with a key you supply (Appetize API token (organization admin)). Read-only: 10 tools (list_apps, get_app, list_app_versions, list_app_tags, list_builds, get_build, list_tags, list_sessions, get_usage_summary, get_account_report). 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.appetize.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Appetize. Appetize 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 apps have I uploaded to Appetize?"
- "What is the latest build of com.example.app on Appetize?"
- "Which versions of com.example.app are on Appetize?"
- "Which tags are set on com.example.app builds in Appetize?"
- "Show the newest Appetize builds tagged beta."
- "What are the details of Appetize build b_abc?"
What it does
list_apps: List the apps in the Appetize account with platform, dates and the latest build; filter by text, platform, version or tags.get_app: Get one app by platform and package name or bundle identifier, with its latest build.list_app_versions: List all version names uploaded for one app.list_app_tags: List all tags used on the builds of one app.list_builds: List builds in the account with version, build number, tags, notes and last-played time; filter by app, platform, version or tags.get_build: Get one build by id: app, version, build number, tags, note and timestamps.list_tags: List every tag currently assigned to a build in the account.list_sessions: List streaming sessions started in a period with device, OS version, platform, length and queue time, filterable by app or device.get_usage_summary: Summarise streaming usage as number of sessions and minutes, grouped by day, week, month or a custom number of days.get_account_report: Show account-level counts such as the number of users in the Appetize organization.
BYOK key
You bring your own Appetize Appetize API token (organization admin) (https://appetize.io/organization/api-token). 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.appetize.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.appetize.io/rest-api (the API this connector calls, with a BYOK key)
Live from the Appetize API (api.appetize.io) with a BYOK key; documentation: https://docs.appetize.io/rest-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 Appetize. Appetize 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 Appetize account.
Built for: Worldwide. Languages: English.