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
1 day ago
in API
0
Future consideration
Expose custom field scope (“Filter field values to”) in API
What is the challenge?
The GET /api/v1/custom_field_definitions endpoint does not return the “Filter field values to” scope setting (Account / Product Line / Workspace), even though this property is configurable in the UI.
There is currently no ...
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 1 year ago
in API
1
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
4 months ago
in API
1
Future consideration
What is the challenge?
When integrating with external tools like ChatGPT, creating or modifying records one-by-one requires constant context switching by the AI. They cannot loop through 30 requests like a script might. As a result the AI consta...
David Haukeness
25 days ago
in API
0
Future 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
about 1 year ago
in API
0
Future consideration
Expose integration data and enable field selection in Aha.io API for workflow automation
What is the challenge?
We're building automated release notes workflows that correlate Aha.io requirements with Azure DevOps Pull Requests. The current API has critical gaps that force manual work:
Gap 1: Integration Data Not Accessible
The ...
Guest
about 1 month ago
in API
0
Future consideration
Ability to create new workspaces and set the workspace template via the API
What is the challenge?
Some teams may want to manage their hierarchy and create new workspaces via the REST API, but currently the endpoint to create workspaces does not include the ability to set the workspace template you want applied to the n...
Stephanie Lechner
3 months ago
in API
0
Future consideration
We currently have two applications writing to Aha using 2 different api keys, but both under the same user. It would be great to have a way to distinguish which api-key is used in the history tab of a record. Currently it only shows the user so a ...
Guest
over 1 year ago
in API
2
Future consideration
Proposing a transition from IP-based to token-based API rate limiting
Who would benefit? I am writing on behalf of Unito, a platform dedicated to enabling seamless two-way synchronization between various software tools. We are actively working on expanding our integrations and are enthusiastic about incorporating th...
Guest
about 2 years ago
in API
1
Future consideration