You’re offline. This is a read only version of the page.
Hello from our testing and reading through help articles, it appears that pagination is not a supported feature when building a custom connector.
I would like to know if we get our connector certified, will we then have the ability to use pagination within our connector?
Please let me know if this is not the case or if there is a know solution.
Hi @will2424
You need to add as parameter. Then when users call the API they can set these but they need to internally maintain the skip count. Start with zero and set default top as 100 or something. I would use a Do until loop to call these and each iteration increment the skip count (0, 100, 200, etc) each time.
Thanks
@abm Thank you for the response.
We are using the JSON:API spec to build our RESt API.
In order to use the top and skip parameters, would our API have to comply with the OData standard?
What is the best way to add these parameters in my custom connector and test?
Thanks!
Hi @will2424
Looks like the option you looking available for MS connectors only.
Could you use top and skip as parameters in your custom connection to retrieve the records?
Thanks
#1
Michael E. Gernaey
497
Super User 2025 Season 2
#2
David_MA
436
Super User 2025 Season 2
#3
Riyaz_riz11
244
Super User 2025 Season 2
Share
Report
All responses (
Answers (
