Hi All, I’m working on pagination of NERM API where i used metadata=true to get the next set of accounts. TERMINATE_IF $RECORDS_COUNT$ < $pageSize$ OR $response._metadata.next$ IS NULL OR $response._metadata.next$ == "" $endpoint.fullUrl$ = $application.baseUrl$ + $response._metadata.next$ But wh…

@SivaLankapalli @srezzaki @jorgedeloittespain Thanks for your inputs. I have tried the pagination script, but it is not working as expected for NERM APIs. At last I found the solution. What have I tried so far? Set the root path as $ and add the pagination attributes to store metadata values like…

Check your API (response strcuture carefully) , and ensure thatSailpoint is mappings are: record path - accounts ; total count path - metadata.count; next page path -metadata.next; stop condition next == null

yes, mate SP must know where is the current account array is, where the next - page info is and where the total account is…BUT ONLY THE ACTUAL ARRAY (ACCOUNTS) SHOULD BE AGGREGATED

I have added the profiles.* in the root path of response information. But the metadata.next is coming from outside of these profiles. [image] Can you help me with what exactly I need to do?

Try this Response attribute mapping ( $.profiles (Root Path) ; Pagination Attribute $._metadata.next; Total account (Optional) $._metadata.total and the offset key offset

so to fix this YOU MUST map the pagiantion variables relative to the absolute root ($) while the account attributes remain relative to the Root Path ($.profiles)

Like this below, right? anything need to change in pagination script [image] [image] [image] TERMINATE_IF $RECORDS_COUNT$ < $pageSize$ OR $response._metadata.next$ IS NULL OR $response._metadata.next$ == "" $endpoint.fullUrl$ = $application.baseUrl$ + $response._metadata.next$

Hello I don’t know why you are using metadata, but check this post to configure pagination in NERM Push or Pulled IDN users into NERM via API - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

Hi @srezzaki , I already tried this, resulting in same issue i faced earlier: aggregated count 200 but actual records 100

The configuration should definitly work, can you share the configuration of the aggregate operation and results (screenshots)

Webservice Pagination not working for NERM API

Identity Security Cloud (ISC) ISC Discussion and Questions

Santhakumar (Shantha Kumar) May 11, 2026, 3:40pm 3

Did I need to add the metadata in response mapping? Or what exactly you are saying?

Topic		Replies	Views
Pagination not working on web service connector ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	9	275	December 13, 2024
NERM Web Services SAAS Connector Configuration - Paging ISC Discussion and Questions webservice-connector , apis , aggregation , identity-security-cloud , nerm	4	431	July 12, 2024
Webservices connector- Aggregation fetch single record only ISC Discussion and Questions webservice-connector , apis , aggregation , identity-security-cloud	2	55	November 25, 2025
Pagination Issue for Web Service Connector ISC Discussion and Questions webservice-connector , apis , identity-security-cloud	9	121	July 20, 2025
Webservice SaaS connector Pagination issue ISC Discussion and Questions identity-security-cloud	19	359	March 25, 2025

Webservice Pagination not working for NERM API

Related topics