# Issue with response mapping **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** webservice-connector, identity-security-cloud\ **Created:** [July 25, 2025, 1:05pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103 "2025-07-25T13:05:45Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![karishma\_shaik2](https://avatars.discourse-cdn.com/v4/letter/k/7ab992/32.png) [@karishma\_shaik2](https://developer.sailpoint.com/discuss/u/karishma_shaik2)\ **Post date:** [July 25, 2025, 1:05pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/1 "2025-07-25T13:05:45Z")
We are currently facing issue with response mapping in our web services source during account creation. Although the accounts are being successfully created, the response mapping is not functioning as expected. The target response from the application after account creation is: ```auto { "CSODCreationid": 78731 } ``` we attempted to map the CSODCreationid attribute to verify the response, but it is consistently coming back as blank in IdentityNow. I have also attached the following for reference: The response mapping configuration ![image](https://global.discourse-cdn.com/sailpoint/original/3X/e/7/e71d5717ad656efcff0476e7a5c9c3d05c606dcb.png) ![image](https://global.discourse-cdn.com/sailpoint/original/3X/d/1/d15acb677e9634935931b886006ca24bc998b3d2.png) The account schema used for validation ![image](https://global.discourse-cdn.com/sailpoint/original/3X/c/7/c73ad07763a6c345e6429307a7748ba5ffa1d5e2.png) I would appreciate any guidance on potential misconfigurations or necessary changes to ensure the response mapping works correctly. Looking forward to your support. ---
**Author:** ![HussainshaSyed001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/hussainshasyed001/32/28234_2.png) [@HussainshaSyed001](https://developer.sailpoint.com/discuss/u/HussainshaSyed001)\ **Post date:** [July 25, 2025, 1:44pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/2 "2025-07-25T13:44:30Z")
> [@karishma\_shaik2](#): > > Although the accounts are being successfully created, the response mapping is not functioning as expected hi need some clarity please: “Although the accounts are being successfully created, the response mapping is not functioning as expected” you mean account is created but ISC is unable to fetch userid? are you sure root path is correctly defined? I suggest to check root path (use json path validator tool to check correct root path) ---
**Author:** ![TheOneAMSheriff](https://avatars.discourse-cdn.com/v4/letter/t/ee59a6/32.png) [@TheOneAMSheriff](https://developer.sailpoint.com/discuss/u/TheOneAMSheriff)\ **Post date:** [July 25, 2025, 5:44pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/3 "2025-07-25T17:44:31Z")
Hi @karishma_shaik2, What is your account schema like? Is **userId** marked as **Account ID** and **Account Name**? If not give it a try please. ---
**Author:** ![udayputta](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/udayputta/32/14195_2.png) [@udayputta](https://developer.sailpoint.com/discuss/u/udayputta)\ **Post date:** [July 28, 2025, 5:13am UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/4 "2025-07-28T05:13:49Z")
hi based on the screenshots that you have shared the configuration looks fine. But can you validate once by pulling the source from postman also. As Amar mentioned this should be atleast Account ID (nativeIdentity) if all of your endpoints rely on this userId. If still this does not work you can validate by attaching AfterOperationRule and if required make a get call and return your response to return all the attributes for the account along with userId. ---
**Author:** ![karishma\_shaik2](https://avatars.discourse-cdn.com/v4/letter/k/7ab992/32.png) [@karishma\_shaik2](https://developer.sailpoint.com/discuss/u/karishma_shaik2)\ **Post date:** [July 29, 2025, 12:35pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/5 "2025-07-29T12:35:05Z")
userId is not account id for us. we have unique account number which is marked as Account Id ---
**Author:** ![TheOneAMSheriff](https://avatars.discourse-cdn.com/v4/letter/t/ee59a6/32.png) [@TheOneAMSheriff](https://developer.sailpoint.com/discuss/u/TheOneAMSheriff)\ **Post date:** [July 29, 2025, 1:59pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/6 "2025-07-29T13:59:10Z")
Hi Shaik, As I understand, SailPoint ISC expects an account with all mandatory account attributes(account ID and name) to be returned after a create account operation. If your API response do not return these required values until a manual action from end-user like accept the invitation, you may try returning empty strings for the account ID and name in **Response Mapping** and wait for account aggregation to fix the empty account. If your API response can return these required values immediately, I believe @udayputta’s suggestion above to run a [Web Services After Operation Rule | SailPoint Developer Community](https://developer.sailpoint.com/docs/extensibility/rules/connector-rules/webservices-after-provisioning-rule) would be a solid solution. Good luck. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [September 27, 2025, 1:59pm UTC](https://developer.sailpoint.com/discuss/t/issue-with-response-mapping/160103/7 "2025-09-27T13:59:36Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.