My votes: API
Sort by:
Popular
Filter by:
Status
Showing 47 of 8658
3
VOTE
Add API support to configure number of seats in a paid seat group
Who would benefit? Enterprise+ customers utilizing paid seat groups What impact would it make? Today, paid seat groups can only be managed within the UI. For teams with large user bases, it would be more efficient to be able to modify the number o...
0
Likely to implement
3
VOTE
Enable filtering on custom fields in Custom Table Records List API
Who would benefit? Any customer using custom tables, particularly those integrating with other data sources or needing API-based filtering capabilities What impact would it make? Scripting updates from other sources of truth such as taxonomy syste...
0
Future consideration
3
VOTE
Ability to search comments through API
Who would benefit? Comments to an idea can be added by almost anyone, even if they are not the original owner of the idea, and even without admin permissions. So, if we enabled API search for comments, a non-admin user could add a searchable hasht...
0
Future consideration
3
VOTE
Add 'identity provider type' attribute to 'Update user' API endpoint
Who would benefit? Customers who manage user provisioning and updates through SSO and automated API processes What impact would it make? Customers can manage their user's authentication method en masse through the API - especially helpful with lar...
0
Future consideration
3
VOTE
Return raw value changes in /api/v1/audits
What it looks now: { "audits": [ { "changes": [ { "field_name": "Assigned to user", "value": "Default assignee → Anton Aha", } ] } ]} Proposal: { "audits": [ { "changes": [ { "field_name": "Assigned to user", "value": "Default assignee &a...
0
Unlikely to implement
3
VOTE
3
VOTE
REST API indicates if custom field is read-only
Currently, the REST API doesn't indiciate if the given custom field has been defined as read-only or not. Here's a sample field definition for a read-only field as returned from `/api/v1/products/{productId}` {"id": "7002184427275897244","key": "k...
0
Future consideration
2
VOTE
When returning history via the API add a flag to return all records not just collated records
What is the challenge? It appears that the audits returned from the API only include collated records. Some users need all records. How would you solve it? Add a flag to allow all raw audits to be returned. What impact would it make?
1
Planning to implement
2
VOTE
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...
0
Future consideration
2
VOTE
Increase the maximum number of records returned by the API
Who would benefit? Users who are using the API to build reporting out of Aha! (e.g. Power BI) What impact would it make? It would reduce the number of API calls that need to be made to retrieve large amount of records How should it work? Instead o...
0
Future consideration