Skip to Main Content

Share your product feedback

ADD A NEW IDEA

API

Showing 76

Aha should delete the integration link when receiving a delete trigger from a webhook

We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect A...
Marvin van Dongen over 9 years ago in API / Features 8 Future consideration

The v1 API does not support assigning a workspace to a WorkRequest Todo, which is a feature available in the UI. Please update the API to allow for this assignment to achieve parity with the user interface.

What is the challenge? The v1 API has a functional gap compared to the UI. Specifically, the endpoint for creating or updating a WorkRequest Todo does not permit assigning a workspace entity to the "Assigned User" field, even though this action ...
Guest 4 months ago in API 0 Future consideration

Separate the Integration Template from a workspace so it can be managed independently

What is the challenge? When I create an integration template, it is based on a workspace integration that I put in place. If I make changes to that workspace integration, it adjusts the template. My challenge is that I would like to create a templ...
Tobias H 12 months ago in API 2 Future consideration

Integration into ChurnZero

ChurnZero is a customer success management software. Being able to sync customer feature requests to ChurnZero accounts would enable the Customer Success team to have a view into customer-related features.
Aidan Parisian almost 4 years ago in API 0 Future consideration

API to get features in a release with multiple tag query parameters

What is the challenge? Reduce the number of API calls and processing effort to fetch records containing multiple tags What is the impact? Help reduce implementation effort and optimize performance Describe your idea When calling the "Get feature i...
Guest about 1 year ago in API 0 Future consideration

A method to effectively control and manage API access in Aha!

Who would benefit? Aha! administrators What impact would it make? It would help track the API usage across the instance. For example, if someone is generating heavy traffic by creating thousands of Aha features per minute, we as admins need a meth...
Alok Dath almost 2 years ago in API 0 Future consideration

Scope / granular permissions for API Access

Hi All, currently every user with Aha! access can create an api token or authorize Apps to use the Api. And the Scope is tied to the user itself and not configurable. When it comes to projects, utilizing the API, it is the Application Owner / Admi...
Oliver Berger over 2 years ago in API 0 Likely to implement

Aha! API Entity Relationship Diagram/Data Model Documentation

Hi Aha! We would like to have a full understanding on how the various Aha! API endpoints (https://www.aha.io/api) relate to each other. Understood there is some customer facing documentation that explains the high-level of the Aha! Data Model. The...
Mike Champlin over 3 years ago in API 0 Future consideration

Delivery Risks via API

Who would benefit? Users wanting to access this data externally What impact would it make? Allow users to use this data outside of Aha (i.e. external reports, dashboards, etc.). This would allow us to keep track of when something is at risk. How s...
Guest about 2 years ago in API 0 Future consideration

Allow Aha! data use in automations with n8n.io

What is the challenge? The data in aha is vast and messy. Converting it all by hand is time intensive. I have set up atomations with jira and slack to manage work, but I need a way to use Aha! feedback in my prompting automations. Converting and...
Guest 5 months ago in API / Automations 0 Future consideration