API
Sort by:
Trending
Status:
Showing 76
1
VOTE
API support to modify paid seat group owners
What is the challenge? Paid seat group owners need to manually identified in the account setting by a billing admin. What is the impact? Changes to paid seat group ownership, which empower teams to manage their workspace's users, are bottlenecked ...
0
Future consideration
1
VOTE
1
VOTE
Get PNG of report/roadmap through API
What is the challenge? Regular updates are needed for Aha Roadmaps shared on a company-internal site to ensure data freshness. Embedding only works when content is left unsecured, and linking to securely published content introduces some experienc...
0
Future consideration
2
VOTE
1
VOTE
provide idea_endorsements and idea_subscriptions as part of the get all idea api
What is the challenge? get a complete view via API on ideas What is the impact? currently you need to do 3 queries to get the complete idea Describe your idea add fields=idea_endorsements,idea_subscriptions to the https://www.aha.io/api/resources/...
0
Future consideration
1
VOTE
Subscription model with a possible Aha! listener
What is the challenge? We have a scenario wherein Github is becoming Single Source of Truth for any changes. Our idea is that can Aha! have a listener. Listener will listen to any changes in Github. this will help changes in Aha! maintained. this ...
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
Aha and JIRA integration comment
What is the challenge? When linking with Epics in JIRA, if the title of the Epic in JIRA has a "-" in it, the comparison field for the name doesn't show any character before the "-" What is the impact? slight annoyance of having to put the correct...
0
Future consideration
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
3
VOTE
Ability to delete product with REST API
Using the REST API I'm able to delete epics, Features, Ideas and other records, but for some reason this operation is not available for Products. At least it's not documented. Is there an internal/experimental API I could use? Is there any other w...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved