Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
REST APIs typically have some mechanism to transmit large volumes of records broken up into pages of results. Power Query has the flexibility to support many different paging mechanisms. However, since each paging mechanism is different, some amount of modification of the paging examples is likely to be necessary to fit your situation.
Typical Patterns
The heavy lifting of compiling all page results into a single table is performed by the Table.GenerateByPage() helper function, which can generally be used with no modification. The code snippets presented in the Table.GenerateByPage() helper function section describe how to implement some common paging patterns. Regardless of pattern, you'll need to understand:
- How do you request the next page of data?
- Does the paging mechanism involve calculating values, or do you extract the URL for the next page from the response?
- How do you know when to stop paging?
- Are there parameters related to paging (such as "page size") that you should be aware of?