Please consider addressing the following when creating your topic:
What have you tried?
I’m integrating SailPoint IdentityNow with Qualtrics via a REST API connector to fetch user data using the /v3/users endpoint. I want to handle pagination so that I can retrieve all users, not just the first 100 or 250.
I’ve reviewed the documentation and understand that /v3/users uses offset-based pagination. I tried using query parameters like limit and offset, and iterating through pages until the returned result is less than the limit.
I also attempted to implement this using a custom connector or rule in SailPoint (Groovy/Java), looping through calls to the API.
What errors did you face (share screenshots)?
There were no hard errors, but:
-
After the first page of results, subsequent pages either return empty lists or do not advance pagination properly
-
It’s unclear if the API response always returns
items, or if the structure changes. -
I’m not sure if the pagination loop is implemented correctly within SailPoint rules.
-
Share the details of your efforts (code / search query, workflow json etc.)?
[
{
"type": "nextPage",
"absoluteNextPageField": "$.result.nextPage"
}
]
What is the result you are getting and what were you expecting?
I expected to retrieve all users in chunks of 100 or 250 using pagination logic. Instead, after the first or second page, the result either becomes empty or repeats data.
My goal is to fetch all user records from IdentityNow and push them into Qualtrics (or another downstream system).
Would appreciate any help:
- Confirming if the response format is consistent (
items[], plain array, etc.) - Best practices to implement offset-based pagination inside SailPoint (e.g., REST connector or Rules)
- Whether
/v3/usersalways returns total count or supports acount=trueparameter