The inability to instantly retrieve an asset’s related items through the API is a significant limitation in Hudu.

Overall, the platform works very well, but this specific gap creates serious scalability and performance issues. For example, if I need to obtain a list of assets related to a single contact, the only option via the API is to pull all 7,000+ relations in our database and then filter them client-side.

This becomes especially problematic during common workflows such as user offboarding. If I am offboarding 10 users and need to identify all assets associated with each user, I must repeatedly retrieve and process the entire relations dataset. While this may work in small batches, it does not scale and introduces unnecessary load, latency, and complexity.

It is clear that your development team has already identified this as a problem, as the get_relations functionality exists and works well in the web interface. However, that same capability is not exposed through the API, which significantly limits automation and integration use cases.

Exposing asset-specific or contact-specific relation queries via the API would greatly improve efficiency, scalability, and real-world automation workflows.