Is your feature request related to a problem? Please describe.

Structuring endpoints based on entities rather than service-specific endpoints, the proposal seeks to streamline the understanding of functionalities related to specific entities, such as users, things, groups, channels, domains making it easier for users to navigate and comprehend the available API functionalities within a specific context.

Describe the feature you are requesting, as well as the possible use case(s) for it.

Structuring API endpoints not based on service-specific endpoints but rather on entities, For example, within the users.yml file, all endpoints would start with /users. Operations related to specific users, such as retrieving user tags (users/{userID}/tag), would be included here. However, I propose including additional endpoints, like /users/{userID}/things, which pertain to the things associated with a user, even if the things functionality resides in a different service.

By including such endpoints in the users.yml API specification, users interacting with this document will find it easier to understand as they would expect users.yml to provide comprehensive user-related functionalities, even if certain functionalities are fulfilled by other services.

Indicate the importance of this feature to you.

Must-have

Anything else?

No response