Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Clear

API

MCP server manage_record update strips rich formatting

What is the challenge? MCP server manage_record update strips rich formatting like table cell background colors, text colors inside table cells, and column widths What is the impact? it messes up the existing formatting. Describe your idea. Fix ...
Guest 10 days ago in API Planning to implement

Expose Structured TestRail Test Data in Aha! Develop for Reporting and Traceability

What is the challenge? The TestRail integration displays test data within Aha! Develop but does not expose it as structured, reportable fields. Attributes like Test Case ID, Test Status, Execution Result, and Coverage render as a display only bl...
Bek Price 4 months ago in API Likely to implement

Support creation of paid seat groups via API

What is the challenge? Admins who manage users and provisioning programmatically can work with many account settings through the API, but they cannot create paid seat groups there. This forces teams to leave automated provisioning workflows an...
Terri Salie 3 months ago in API Future consideration

Add granular scoping controls for API keys

What is the challenge? API keys inherit the full permissions of the user who creates them, and there does not appear to be a way to scope the key itself to specific workspaces, folders, or record types. This creates concern internally when bui...
Jeremy Bruno 7 months ago in API Future consideration

Provide Microsoft Power Automate Connector

What is the challenge? Easily integrating with Aha! using Microsoft integration platforms What is the impact? Having to rekey data - costs time Describe your idea Microsoft provides a low-code multi-platform integration service calle...
Chris Doran over 2 years ago in API Future consideration

Expand API support for incremental synchronization and change tracking

What is the challenge? Customers replicating Aha! data into external systems need efficient ways to identify created, updated, and deleted records. Some entities do not consistently support capabilities such as: Account-level updated_since...
Jeanette Resnikoff 4 months ago in API Planning to implement

Expose Account > Activity data through API

What is the challenge? I would like to integrate Aha! activity logs into my SIEM but cannot access the information from the Account > Activity table via the API. What is the impact? Unable to integrate with the corporate SIEM without th...
Madeleine Black about 1 year ago in API Already exists

Please fix the published OpenAPI spec to declare the query parameters the API supports

We build spec‑driven integrations against the Aha! REST API (OpenAPI codegen, LLM tool frameworks). These clients can only send parameters the published openapi.json​ declares. The gap is API‑wide, not endpoint‑specific: the spec omits query param...
Przemek Kulik 3 months ago in API Likely to implement

Enhance the Audit History API to provide complete user information for both custom User-type fields and system User-type fields. For custom User-type fields, in addition to the existing raw_value (user IDs), expose the corresponding user email addresses (similar to the email_value field returned by the entity retrieval APIs). This would eliminate the need for additional user lookup API calls and keep the Audit History API consistent with the entity retrieval APIs. For system User-type fields (such as Assigned To, Created By, etc.), enhance the Audit History API to expose the underlying user identifiers and email addresses, rather than only the display names. Providing user IDs and email values would enable reliable processing of audit records, avoid ambiguities caused by duplicate display names, and offer a consistent experience across all User-type fields. These enhancements would improve API consistency, reduce integration complexity, and make audit history processing more reliable for customers integrating with Aha!.

What is the challenge? The Audit History API currently provides limited information for User-type fields. For custom User-type fields, it exposes only the user IDs (raw_value) without the corresponding email addresses. For system User-type fields ...
Guest 4 months ago in API Future consideration

Expand payload response in "Assistant usage API" endpoint

What is the challenge? Using the "Assistant usage API" endpoint to extract usage of the AI assistant into a 3rd party database, to be used to create a usage dashboard. There are certain data points not present in the response payload, which is m...
Dale Potter 12 months ago in API Future consideration