# Webservice Paging

**URL:** <https://developer.sailpoint.com/discuss/t/webservice-paging/188157>\
**Category:** SHF Discussion and Questions\
**Tags:** webservice-connector, identity-security-cloud\
**Created:** [November 13, 2025, 8:55am UTC](https://developer.sailpoint.com/discuss/t/webservice-paging/188157 "2025-11-13T08:55:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandashafreen26](https://avatars.discourse-cdn.com/v4/letter/s/e495f1/32.png) [@sandashafreen26](https://developer.sailpoint.com/discuss/u/sandashafreen26)\
**Post date:** [November 13, 2025, 8:55am UTC](https://developer.sailpoint.com/discuss/t/webservice-paging/188157/1 "2025-11-13T08:55:17Z")

</div>

We have a Web Service connector configured in SailPoint IdentityNow, and we’re encountering an issue with account aggregation.

Currently, the first API call retrieves the initial 2000 records. The response of this first call includes the URL for the next page in the field `d.nextpage`. Below is an example of the response:

{  
“d”: {  
“\_\_type”: “FOUND”,  
“nextpage”: “[https://eupsrob.abc.com/automation/robots\_api.asmx/NUATFull?RecordCount=10&PageGuid='MTjvt”](https://eupsrob.abc.com/automation/robots_api.asmx/NUATFull?RecordCount=10&PageGuid='MTjvt%E2%80%9D),  
“useridlist”: [  
{  
“userid”: “CL0AP000”,  
“useridType”: “PERSONAL”,  
“useridBelongsToEIN”: “1234567”,  
“useridStatus”: “HISTORIC”,  
“useridToHistoric”: “26/06/2020 19:15:00”  
},  
{  
“userid”: “CL0PM000”,  
“useridType”: “PERSONAL”,  
“useridBelongsToEIN”: “987654”,  
“useridStatus”: “HISTORIC”,  
“useridToHistoric”: “10/03/2021 19:36:00”  
}  
]  
}  
}

We would like to understand how to configure paging in the connector so that subsequent calls automatically follow the `d.nextpage` URL until all records are retrieved.

I have tried $.d.nextpage, it is scanning accounts but not bringing in any. Could you please suggest the best approach to handle this type of pagination in IdentityNow?

Thank you for your help.

---

<div class="post-metadata">

**Author:** ![zachm117](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/zachm117/32/3883_2.png) [@zachm117](https://developer.sailpoint.com/discuss/u/zachm117)\
**Post date:** [November 14, 2025, 12:43pm UTC](https://developer.sailpoint.com/discuss/t/webservice-paging/188157/2 "2025-11-14T12:43:36Z")

</div>

HI @sandashafreen26 !

Can you please share the paging steps/logic you have tried?

Here is an example from one of our connectors that would return 5,000 records, then provide a link for the next page of results.

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/b/9/b986c50efced2a38159485e87e758cc454ea4f99.png)

Please let me know if the below Paging Steps works for you:

TERMINATE\_IF $RECORDS\_COUNT$ \< 2000  
$endpoint.fullUrl$ = $response.d.nextpage$

Thank you,

- Zach

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [January 13, 2026, 12:44pm UTC](https://developer.sailpoint.com/discuss/t/webservice-paging/188157/3 "2026-01-13T12:44:26Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.