API
Sort by:
Recent
Status:
Showing 68
5
VOTE
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...
0
Future consideration
2
VOTE
4
VOTE
Ability to filter on visibility for Ideas API
For "List ideas" and "List ideas for a product" endpoints, it would be useful to have the ability to filter on visibility values. In my application I want to display a list of just ideas with specific visibility values, not all values. Currently I...
0
Future consideration
1
VOTE
REST API: Ability to only list idea votes and comments updated since a given date
Currently, when listing Idea Votes and Idea Comments for a given Idea through the REST API, all records are returned. It would benefit consumers of the REST API to be able to specify an updated_since query string parameter so that only record upda...
0
Future consideration
2
VOTE
Allow exporting the schema of a scorecard through the API
When developing tools which use the Aha! REST API, it can be useful to check the schema that scorecards for a specific workspace/product use, in order to visualize this data. Currently, this can only be achieved by directly loading e.g. Ideas and ...
0
Future consideration
1
VOTE
Make rest API for getting the list to-do that are not associated with any product
Need the rest API which gives list of to-dos that are not associated with any productThe scope of the to-do can be user level and global, means gives list of all to-do in the instance (doesn't matter who created , and assign to) which is not assoc...
0
Future consideration
4
VOTE
Support timestamps on status change dates in the API
I would like to have timestamps supported in the API for any user action oriented dates (like create dates, updated dates, etc.). Currently the timestamp is not included for the status_changed_on field. I'd like for timestamps to be supported for ...
0
Future consideration
1
VOTE
Add user first name and last name fields to Get User API response
Currently Aha stores user first and last names. In the get user and list users REST API response objects, those fields are combined into one field: name. So John and Doe just get returned as John Doe. This causes problems when you have many differ...
0
Future consideration
1
VOTE
Ability to query on custom fields in API
We need to query on a custom field, SF Account ID, on the Aha record, to determine if an account has already been created in Aha. Because we can't do this, we are constantly creating duplicate accounts in Aha that need to be manually removed.
2
Future consideration
1
VOTE
© 2025 Aha! Labs Inc.•All rights reserved