Qlik Community

Connectivity & Data Prep

Discussion board where members can learn more about Qlik Sense Data Connectivity.

Qlik Insider: SaaS capabilities for Data Integration and Analytics, May 25th! Register Now
Showing results for 
Search instead for 
Did you mean: 

Incomplete URL in 'next' field for REST pagination

I'm trying to scrape paginated user data from a REST API, and the format of the 'next' field needed for pagination is `/api/v2/users/default/production?h= <TOKEN>` rather than the full `https://app.example.com/api/v2/users/default/production?h= <TOKEN>` 

How would I configure the pagination options of the API connection to correctly find the next link? The connection currently only pulls the first page of 20 users when it should be getting 3000+


Labels (1)
0 Replies