For the initial setup, as my use case is using Unsplash for profile avatar, I’ve hard-coded “avatar” for the “query” query parameter.
So when my users are looking for an Unsplash pics for their profile, they get “avatar” relative pictures in the list. I put an input where the user can then enter keywords, and the list is built with a dynamic “query” filter, populated using the keywords input value.
When the user find the photo for his profile, he needs to click on the picture, which is zoomed in using a modal with a select button. This button is linked to an UPDATE Current user action where the profiles avatar url is populated with the Unsplash web format image.
It works very well, even if indeed the initial setup depends on the use case. For me it’s not an issue to provide a fake keyword, as the Unsplash API is used as a search API. But in some case it could be an issue.
I hope we could soon use variable when setting up the external collection, but it’s also true that per default, Unsplash should provide their most popular photos when the query parameter is empty.
Hope this helps…