--- title: Aha API Integration on Truto slug: aha category: Ticketing canonical: "https://truto.one/integrations/detail/aha/" --- # Aha API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Users** — The User object represents a User. - **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them ## How it works 1. **Link your customer's Aha account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Aha.** The Proxy API is a 1-to-1 mapping of the Aha API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync customer feedback directly into Aha! Ideas** — Customer success and support platforms can let their users push feature requests and feedback straight into Aha! as Ideas, linking customer revenue data to product priorities so PMs can make informed decisions. - **Bridge engineering execution with product strategy** — Engineering analytics and DevOps tools can pull Aha! workspaces, users, and work items to correlate development activity with strategic product initiatives, giving leadership visibility into how engineering time maps to business goals. - **Automate go-to-market workflows from release milestones** — Marketing automation and release communication tools can monitor Aha! releases and features to automatically generate changelogs, product update emails, or in-app announcements when new functionality ships. - **Link sales pipeline data to product roadmap items** — CRM and revenue intelligence platforms can push prospect feature requests into Aha! with deal context attached, enabling product teams to quantify the revenue impact of roadmap decisions. - **Centralize user and workspace data across product tools** — Platforms managing cross-tool workflows can use Truto's Unified User Directory API to ingest Aha! users and workspaces, building a unified view of who owns what across the product development stack. ## What you can build - **Aha! workspace and user directory sync** — Automatically import and keep in sync all Aha! workspaces (product lines) and users via Truto's Unified User Directory API so your app always has an up-to-date org map. - **One-click 'Send to Aha!' for customer feedback** — Let your end users push support tickets or feedback items directly into Aha! as Ideas or Features, with customer context and revenue metadata embedded in the request. - **Revenue-weighted feature request tracker** — Surface Aha! features alongside linked deal sizes and customer MRR pulled from your platform, so product managers can prioritize by actual business impact. - **Cross-tool user identity resolution** — Match Aha! users to identities in your platform using workspace membership and email data from Truto's Unified User Directory, enabling accurate attribution across tools. - **Automated release notification pipeline** — Monitor Aha! release and feature status changes to trigger downstream actions in your product — like drafting changelogs, notifying stakeholders, or updating customer-facing status pages. - **Strategic vs. unplanned work dashboard** — Ingest Aha! epics, features, and user assignments to build executive dashboards that show how engineering effort aligns with strategic initiatives versus ad hoc requests. ## FAQs ### What authentication method does the Aha! integration use? Aha! supports OAuth 2.0 and API key authentication. Truto handles the auth flow for your end users, so you don't need to build or maintain token management yourself. ### Which Truto Unified APIs are available for Aha! today? Aha! is currently supported under Truto's Unified User Directory API, which covers Users and Workspaces. Additional tools and Unified API coverage (such as Ticketing resources for Features, Ideas, and Releases) are built on request. ### Can I access Aha! custom fields through Truto? Aha! exposes custom fields on features, ideas, and other objects via its REST API. Truto can support custom field reads and writes as part of a tailored integration — reach out to discuss your specific mapping requirements. ### Does Aha! support webhooks for real-time data? Yes, Aha! provides activity webhooks that fire on status changes, feature updates, and other events. These can be leveraged through Truto to trigger real-time workflows in your application without polling. ### Are there rate limits I should be aware of on the Aha! API? Aha! enforces rate limits on its REST API that vary by plan. Truto manages pagination and request throttling on your behalf, so your integration stays within limits without custom retry logic. ### What if I need Ticketing API resources like Features, Ideas, or Releases? These are not yet available as pre-built Truto resources but are fully supported by the Aha! API. Truto builds new tools and Unified API mappings on request — most integrations are shipped within days.