Hi, I need to write a webservice after rule for an aggregation operation, Now whatever I configured in pagination will remain same. Is that true. can someone share any same code if you have worked on the same use case. Any guidance would be approeciated.

Hey Chandra, Pagination config happens in the connector. If it’s setup correctly there, it will continue to work the same. You do not need to implement pagination logic in the after operation rule The After Rule will receive the aggregated data per page, and you can manipulate or transform it as …

[image] chandramohan27: Now whatever I configured in pagination will remain same Can you be more specific about this and also explain what are you looking to achieve? Pagination configuration in the UI is to iterate through multiple API calls when all records are not returned in on API call …

@iamology So if my response has 10 pages, then my After rule gets executed for 10 times?

that’s right. After Operation is called after each page. If you like to reuse any of the values in these executions, you can use transientValue approach explained in this page: [image] Using WebService connector rules to streamline and accommodate “interesting” sources Video …

can you clarify what you need for pagination here? Does it use Query params, ie https://site?limit=250&offset=250 or something in the body? does it involve a response header? part of the previous response?

[image] StephenHolinaty: s it involve a response header? part of the previous response? @StephenHolinaty My requirement here is. The API call returns body something like below ``` { "records": \[ { "foldername": "testuser1", "id": "41" }, { "fol…

based on what you’ve written here, that doesnt sound like “Pagination” that sounds like you need (pseudo-code…) GET /Users parse the user responses, and get things like email, foldername, id CHILD OPERATION of the first agg (set a parent endpoint of the 1st call) GET /users/$response.id$ do …

Expanding on the parent/child endpoint relationship slightly more, the connector will perform (page 1) of the GET to /Users then for each individual record, as specified by your root path ($, $.users, etc.), it will call the child operation to supplement the data.

@StephenHolinaty Actually the reason I thought of after rule is because there is an additional logic. my second API call returns multiple records, I need to check if it is equals to “Employee“ only then take the value “userEmail” and set it on response object.

you might even be able to do that with JSONPath in your mappings root: $ email: $[?(@.type == “Employee”)].email or similar

Webservice After Rule - Aggregation

Identity Security Cloud (ISC) ISC Discussion and Questions

StephenHolinaty (Stephen Holinaty) September 25, 2025, 4:01pm 12

this might also help: Using WebService connector rules to streamline and accommodate “interesting” sources

Topic		Replies	Views
Webservice After Rule ISC Discussion and Questions webservice-connector , rules , identity-security-cloud	7	226	November 25, 2024
Web services after operation rule for aggregation ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	1	807	August 29, 2023
HTTP Aggregation operation - Paging ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	11	289	December 23, 2024
Web Service Connector ISC Discussion and Questions aggregation , identity-security-cloud	11	179	October 28, 2025
Using WebService connector rules to streamline and accommodate “interesting” sources Video Library identity-security-cloud , developer-days-2024-isc , developer-days	3	1441	April 17, 2024

Webservice After Rule - Aggregation

Related topics