Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Vitally (BYOK) — connector documentation

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

What Vitally (BYOK) is for

Vitally (BYOK) lets an AI assistant read your own Vitally data through the Vitally API with a key you supply (Vitally REST API key (US data center)). Read-only: 9 tools (list_accounts, get_account, list_users, search_users, list_notes, list_tasks, list_nps_responses, list_meetings, list_note_categories). 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 *.rest.vitally.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Vitally. Vitally 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 Vitally accounts renew soon?"
  • "Show Vitally account acct_123"
  • "Which users are tracked in Vitally?"
  • "Is ana@example.com a user in Vitally?"
  • "What notes were logged in Vitally recently?"
  • "Which Vitally tasks are overdue?"

What it does

  • list_accounts: List Vitally accounts (customers) with owner, MRR, renewal and churn dates, last seen time, user count, NPS score, health score and traits. Active accounts by default.
  • get_account: Get one Vitally account by its Vitally id or external id.
  • list_users: List Vitally users (your customers' end users) with name, email, last seen time, last NPS score and feedback and segments. Contains personal data.
  • search_users: Find a Vitally user by exactly one of: email, email domain or external id.
  • list_notes: List notes logged on accounts and organizations with subject, text, date, author, category, tags and source.
  • list_tasks: List tasks with name, description, due date, completion time and assignee.
  • list_nps_responses: List NPS survey responses with score, feedback, respondent user id and response time, for accounts or organizations.
  • list_meetings: List meetings with title, description, start and end time, location, status, AI summary and source.
  • list_note_categories: List the categories notes can have, with id and name.

BYOK key

You bring your own Vitally Vitally REST API key (US data center) (https://docs.vitally.io/pushing-data-to-vitally/rest-api). 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 *.rest.vitally.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

Live from the Vitally API (*.rest.vitally.io) with a BYOK key; documentation: https://docs.vitally.io/pushing-data-to-vitally/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 Vitally. Vitally 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 Vitally account.

Built for: Worldwide. Languages: English.