In current implementation using the V1 API, apps are utilizing the following endpoint to fetch specific content along with its associated web resources:

/rest/api/content/{id}?expand=body.view,body.view.webresource.superbatch.tags.all,body.view.webresource.tags.all

This endpoint allows to retrieve content with its complete viewable body, including all associated web resources and tags, which are essential for apps to function correctly. In planning the migration to the V2 API, it has been identified that there is no direct equivalent or documented method to achieve the same functionality, specifically the ability to fetch web resources associated with content in a similar manner.

As an app developer, we would like to have endpoint or method in the V2 API that allows for fetching web resources associated with content, similar to the V1 API. This would include options to expand or include web resource tags, such as superbatch.tags.all and tags.all, within the V2 architecture.