This topic provides an example of a JSON response for an account aggregation operation.
Using the Web Services source, you can have multiple account aggregation operations.
A post was split to a new topic: Why POST instead of GET for HTTP Method in Web Services?
Hi Theja C! Thank you for your input. This appears to be related to configuring a product feature. I’ve moved your comment to our ISC Discussions and Questions category for greater help from the community.
The Example Screenshots are incorrect, and show “Authentication URL” When the system shows “Context URL” for the General Information section.
Additionally, could you show an example on how to use the ID from the response of the first endpoint in the Context URL of the second response?
For example, the second URL expects the URL to be: “/users/<USER_ID_FROM_FIRST_RESPONSE>/profile” but when setting it to “/users/$response.id$/profile”, an error occurs showing the URL as “/users//profile”
A note should be added to the documentation to state that the first endpoint in the Aggregation should return ALL of the Resource Objects (Accounts/Entitlements) and that subsequent child endpoints can add onto them.
Hi Geoff. Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-5192