RELATED IDEAS
Expand payload response in "Assistant usage API" endpoint
What is the challenge? |
Using the "Assistant usage API" endpoint to extract usage of the AI assistant into a 3rd party database, to be used to create a usage dashboard. There are certain data points not present in the response payload, which is making it difficult to easily build the dashboard. |
|---|---|
What is the impact? |
There is a possibility that the data in the dashboard is not entirely accurate |
Describe your idea |
1. Return "start_at" and "end_at" in the payload response 2. Add "group by" functionality to group the results in the payload by day |
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved
I’d like to suggest a few points to the endpoint (e.g., https://www.aha.io/api/resources/assistant_usage/list_assistant_users_within_a_time_window):
Echo Input Parameters in Output
While the API accepts
start_atandend_atas input parameters, it would be helpful if these values were also included in the response payload. This would provide clarity on the timeframe covered when reviewing the results, especially in automated reporting or auditing scenarios.Grouping by Timeframe
Adding the ability to group results by a functional time unit—such as day, week, or month—based on the activity timestamp would be ideal. This would allow for more flexible analysis and visualization of usage trends.
Detailed Activity Records
Alternatively, returning all activity details with their respective timestamps would also work, provided the volume of records remains manageable. This would give consumers of the API the flexibility to perform their own grouping or filtering as needed.
These enhancements would significantly improve usability and clarity for teams analyzing assistant usage data.