Hi,

We have successfully implemented Content Delivery API V2 in our application, and the API calls are functioning as expected. However, I seek clarification regarding referencing a folder versus a page.

In our observations, querying a reference to a folder only retrieves information about the folder itself and not its contents.Consequently, if our intention is to store a collection of assets in a folder and display them, it appears that we must include them on a page instead.

Could someone confirm this understanding or provide insights on an alternative approach?

Here's the API call that we are firing:

https://examplesite.com/siteassets/images/***_photos_lib

https://examplesite.com/siteassets/images/***_photos_lib?expand=* 

Even with the "expand" parameter, the response is limited to just the folder itself, which is not the case when using "expand" to query a page.

For additional context, here's a snapshot of our folder structure & the JSON response that is returned when querying:.

JSON Response :

[
  {
    "contentLink": {
      "id": 157558,
      "workId": 0,
      "guidValue": "fd060af6-545a-4c94-9575-7c9c46bd853d",
      "url": "/siteassets/images/***_photos_lib/?v=4939bf"
    },
    "name": "***_Photos_lib",
    "existingLanguages": [],
    "contentType": [
      "Folder",
      "SysContentFolder"
    ],
    "parentLink": {
      "id": 4956,
      "workId": 0,
      "guidValue": "a5fda262-55da-41d2-8ff3-0d045dbd439d",
      "url": "/siteassets/images/?v=4a3347"
    },
    "routeSegment": "***_photos_lib",
    "url": https://examplesite.com/siteassets/images/***_photos_lib/?v=4939bf,
    "changed": "2023-03-08T15:37:16Z",
    "created": "2023-03-08T15:37:16Z",
    "saved": "2023-03-08T15:37:30Z"
  }
]