Are we able to paginate the Get Assets API call?

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [ ] Bug report
  • [ ] Performance issue
  • [ x] Documentation issue or request

Current behavior

Assets can only be requested all at once.

Expected behavior

For thousands of assets, we will need to be able to paginate the results coming from the server.

Minimal reproduction of the problem

Use the assets API to query a large set of assets.


App Name: N/A

  • [ x] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: @latest


  • [x ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

This would be a feature request if the option is currently available. At the moment, I am looking for documentation if the option exists.

I found the documentation. I was looking at the “Get Assets” POST operation not the GET operation. For anyone else that searches the support forum for the same reason, see the documentation regarding “skip” and “top”

1 Like

The main reason for the Post Query is the UI. If you make a search with 50 ids you exceed the max URL length and therefore it was necessary to introduce the POST endpoint.

q is a JSON query and odata is an odata query of course. Both are described here:

Thank you for the additional clarification!