Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
prisma_elmu
Partner - Contributor
Partner - Contributor

Rest API Pagination - Next Link Tagged in "Link" as rel="next"

Hello Qlik Community,

i try to get all the pages of an api request to "https://api.hrworks.de/v2/persons/master-data"

When doing so, the API endpoint will give back the following:

prisma_elmu_0-1698675293242.png


I cannot find the right type of pagination, to automatically get the next page Link. i already tried multiple things, but nothing seems to work.

Its very similar (but not the same) to this request "https://community.qlik.com/t5/Connectivity-Data-Prep/Qlik-Rest-Connector-Pagination-How-to-handle-mu... which seems to be abandoned.

 

Its also very similar to that Request "https://community.qlik.com/t5/Connectivity-Data-Prep/How-to-define-pagination-in-the-Qlik-rest-conne....

"link":https://domain.freshdesk.com/api/v2/tickets?filter=all_tickets&page=2>;rel="next"

 

Is there any way to use the Qlik Sense pagination?

 

===

I did already build a custom Loop (Quick and dirty), which does work, by parsing the response (Link) and making the next request with the next url (by using WITH CONNECTION() ) - but i want to do it in a better / more efficient way by using qlik sense pagination.

 

prisma_elmu_1-1698676187803.png

I know, the code is not the best, i dont want to get a better code at this point.

Thanks in advance.

 

Labels (3)
1 Solution

Accepted Solutions
DaveChannon
Employee
Employee

Hi @prisma_elmu 

In furture you might have more engagement on a topic like this in the app dev forum, but looking at your example, because of the formatting of the response I think you're already using the most appropriate method.

The native connector pagination requires a clean field or attribute from which to retrieve the next url or page number. You'd be using custom from the start, which means you went down the correct path with what you built!

View solution in original post

2 Replies
DaveChannon
Employee
Employee

Hi @prisma_elmu 

In furture you might have more engagement on a topic like this in the app dev forum, but looking at your example, because of the formatting of the response I think you're already using the most appropriate method.

The native connector pagination requires a clean field or attribute from which to retrieve the next url or page number. You'd be using custom from the start, which means you went down the correct path with what you built!

marksouzacosta

As an addition to this topic, I'm excited to share my latest tutorial on integrating Asana with Qlik Cloud using REST APIs!

In this step-by-step guide, you'll learn:
- How to use Asana REST APIs with Postman
- Creating REST Data Connections in Qlik Cloud
- Extracting data from Asana and saving as Parquet files
- Enhancing connections with custom parameters and pagination

Check out the full video on YouTube:
Integrate Asana with Qlik Cloud Using REST APIs: A Step-by-Step Guide
https://youtu.be/lFwar30BNkQ?si=UZoM_x9L5amdJSnf

Regards,

Mark Costa

Read more at Data Voyagers - datavoyagers.net