Calling Paginated API with an "endCursor" variable that needs to be passed to subsequent calls

Question

Hey there.&nbsp;I'm looking for help for a bit of a complicated problem.&nbsp;&nbsp;I have a connection to a REST API that returns a pagination variable to send on subsequent API requests to retrieve the next page.&nbsp;I am trying to loop through the pages and get all the data into PBI desktop but am having trouble doing so with this endCursor variable.Here's an example response for a call with an "endCursor"(the variable in question) and a "hasNextPage":&nbsp;"pagination":&nbsp;{&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"endCursor":&nbsp;"(random variable is here)",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"hasNextPage":&nbsp;true&nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;I'm not sure how I would be able to pass the variable into the "RelativePath" and have it loop through all the data.Has anyone done this successfully?

anonymous · Accepted Answer

HI&nbsp;Anonymous,Perhaps you can take a look at the 'GenerateByPage' helper function to create a custom function to iterator and expand records based on the page number:Helper functions for M extensions for Power Query connectors - Power Query | Microsoft DocsRegards.Moonlight

Forum Discussion

Calling Paginated API with an "endCursor" variable that needs to be passed to subsequent calls

2 Replies

Related content

Paginated Report

Paginated report

Paginated Report headers not repeating

Paginated Reports

GraphQL- Shopify Pagination