We would like to have a full understanding on how the various Aha! API endpoints (https://www.aha.io/api) relate to each other. Understood there is some customer facing documentation that explains the high-level of the Aha! Data Model. The value of this to customers would be critical to deeper levels of data analysis, accurate level of detail when the API is leveraged for CRUD operations (Create Read Update Delete), and streamlined integration with tools inside & outside of Aha!.
Traditionally this can be done via an Entity Relationship Diagram. The purpose of this is to show the data's cardinality (one-to-one, one-to-many, & many-to-many) and overall relationship. This model tends to get complex to understand with the presence of nested arrays via the response of various endpoints of the API.
Overview of Entity Relationship Diagrams (ERD)
Right now the high level information is available here https://www.aha.io/support/roadmaps/videos/aha-roadmaps-overview/aha-data-model-product-management. It would be super helpful to have this Entity Relationship Diagram and Data Model detailed in the developer documentation (https://www.aha.io/api).