Replies: 1 comment 1 reply
|
The api already has includes, so this is already possible. And yes, these includes don't appear in the api docs. The api docs are auto generated and will be improved once we refactor the API. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Currently, when fetching the list of servers via the
List ServersAPI endpoint, the response only contains general server information. It does not indicate which users (subusers) have access to each server or what specific permissions they possess.To audit or manage access across multiple servers, external applications currently have to make additional individual API calls for every single server. For large deployments, this creates unnecessary overhead and risks hitting API rate limits.
Describe the solution you'd like
Enhance the
List ServersAPI endpoint response (or allow an optionalincludeparameter, e.g.,?include=subusersor?include=permissions) to include access details for each server.Ideally, the response for each server object would include:
Describe alternatives you've considered
Iterating over every server individually using the subusers endpoint. This is inefficient and scales poorly as the number of servers grows.
Additional context
This enhancement would significantly improve external integrations, third-party management dashboards, automated auditing, and user access reporting scripts.
All reactions