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

Aha (BYOK) — connector documentation

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

What Aha (BYOK) is for

Aha (BYOK) lets an AI assistant read your own Aha data through the Aha API with a key you supply (Aha! API key). Read-only: 11 tools (get_current_user, list_workspaces, list_features, list_workspace_features, get_feature, list_epics, list_workspace_releases, list_initiatives, list_goals, list_ideas, list_users). 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 *.aha.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Aha. Aha 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 Aha! user is my API key connected to?"
  • "Which workspaces exist in our Aha! account?"
  • "What features does our Aha! account have?"
  • "What features are in workspace PRJ1?"
  • "Show Aha! feature PRJ1-1"
  • "What epics exist in Aha!?"

What it does

  • get_current_user: Show the Aha! user the key belongs to: name, email, workspace roles and accounts.
  • list_workspaces: List workspaces (products, product lines and teams) with reference prefix, type and creation date.
  • list_features: List features across the account (only a few fields by default; ask for more with fields).
  • list_workspace_features: List the features of one workspace with reference number, name and creation date.
  • get_feature: Get one feature by reference number (for example PRJ1-1) or id, with status, dates, score, release and epic.
  • list_epics: List epics across the account with reference number and name.
  • list_workspace_releases: List the releases of one workspace with start and release dates.
  • list_initiatives: List initiatives with status, effort and value.
  • list_goals: List goals with progress, dates and workspace.
  • list_ideas: List ideas with votes and workspace. Filter by search text, status, tag or dates.
  • list_users: List users with role flags, seats and enabled state.

BYOK key

You bring your own Aha Aha! API key (https://www.aha.io/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 *.aha.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 Aha API (*.aha.io) with a BYOK key; documentation: https://www.aha.io/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 Aha. Aha 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 Aha account.

Built for: Worldwide. Languages: English.