Try our conversational search powered by Generative AI!
AI OnAI Off
If you want to list the content in a folder, you need to load the children; https://examplesite.com/siteassets/images/***_photos_lib/children. Just like you list any content.
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 :