Forum Discussion
6 Replies
- tstackFormer Employee
Leveraging the REST Snap’s pagination functionality is definitely the way to go for your use case, but I wanted to make sure your original question was answered as well. The Pipeline Execute snap will kick off a child pipeline for every document it receives (if reuse is turned off). So, to invoke something N times, you’ll need to generate N documents. Generating documents can be achieved with the Sequence snap, if the number is coming from a pipeline parameter. If the number is coming from a document, you can use the ‘sl.range()’ method to create an array that is then split with a JSONSplitter to create the documents for the PipeExec snap.
- nganapathirajuFormer Employee
What is your usecase?
- ddanglerNew Contributor III
We are querying tickets from Zendesk API and it does not return all the records in one call but gives the url to use in the next HTTP call to get the next set of records.
Sample response from the first call:
{ "tickets": [ ... ], "count": 1234, "next_page": "https://account.zendesk.com/api/v2/tickets.json?page=2", "previous_page": null }In this example, I need to make calls to their API until
next_pageisnullor 12 times (1234 /100, because each call returns only max of 100 records).Here is the url to their documentation if you want more details: https://developer.zendesk.com/rest_api/docs/core/introduction#pagination
Please throw some inputs on how this can be done? Thanks in Advance!
- nganapathirajuFormer Employee
You further need to look at how to implement pagination on the REST Get snap.
Rest get snaps support pagination.
https://help.zendesk.com/hc/en-us/articles/229489028#add
Take a look at this blog.
This clearly describes how to implement pagination. This may not be exactly similar for the ZenDesk APIs but you will get the idea.