My ideas: API

What is the challenge? Admins who manage users and provisioning programmatically can work with many account settings through the API, but they cannot create paid seat groups there. This forces teams to leave automated provisioning workflows an...

What is the challenge? The Audit History API currently provides limited information for User-type fields. For custom User-type fields, it exposes only the user IDs (raw_value) without the corresponding email addresses. For system User-type fields ...

What is the challenge? The current API does not support programmatically creating an integration link and selecting the “use_remote / commit from Jira” option in the same flow (or at all), so the UI can do something the API cannot. What is the im...

What is the challenge? Updating the Collections on a document is currently a manual process. We have an Employee Handbook published for all employees. It is comprised of folders that come out of various workspaces - in order to make sure authors a...

What is the challenge? When multiple capacity planning scenarios are active on the same record, list reports return duplicate rows for each capacity estimate, one per active scenario. There is no way to distinguish which estimate belongs to which ...

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...

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? 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...

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 ...

What is the challenge? Broadcasts can't be scheduled with start/expiration dates, so organizational requirements for quarterly reminders - or admin announcements re: holidays, etc. require a person to create, enable, and disable broadcasts manua...