What is the challenge? The API has no way to set a page or folder's position within the table of contents tree. parent_id controls nesting, but not order among siblings. Reordering only works by manually dragging in the UI.
What is the impact? Te...
Krysta Boyer
10 days ago
in APIFuture consideration
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
about 2 months ago
in APIFuture consideration
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
6 months ago
in APIFuture consideration
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
about 2 years ago
in APIFuture consideration
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 ...
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
10 months ago
in APIFuture consideration
What is the challenge? Aha! does not have an API end point that provides subscription details - plan type, number of seats. What is the impact? Teams would like the ability to programmatically call for subscription details to keep subscription det...
Kristina Gass
over 1 year ago
in APIFuture consideration
What is the challenge?
Be able to handle value from audit without deduced the "impacted" json field changes and without process the current string provided in "value" by sending both value separately to let developer handle them on their side if...
Add an API endpoint (or option) to create/link an integration record (e.g. Aha ↔ Jira) with use_remote/“commit from Jira” behavior, so Jira can overwrite/sync the Aha entity on initial link—matching what the UI supports.
What is the challenge? The current API does not support programmatically creating an integration link and selecting the “use_remote / commit from Jira” option in the same flow (or at all), so the UI can do something the API cannot.
What is the im...
Paweł Żmuda
4 months ago
in APIFuture consideration
What is the challenge? Updating the Collections on a document is currently a manual process. We have an Employee Handbook published for all employees. It is comprised of folders that come out of various workspaces - in order to make sure authors a...
Stephanie Redl
5 months ago
in APIFuture consideration