# Identitynow webservices connector json response mapping

**URL:** <https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350>\
**Category:** SHF Discussion and Questions\
**Created:** [August 10, 2022, 8:33pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350 "2022-08-10T20:33:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vinit\_lodaya](https://avatars.discourse-cdn.com/v4/letter/v/ccd318/32.png) [@vinit\_lodaya](https://developer.sailpoint.com/discuss/u/vinit_lodaya)\
**Post date:** [August 10, 2022, 8:33pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350/1 "2022-08-10T20:33:19Z")

</div>

Hello,

I have a json response like below. The userids are the list of accounts. What should be the response mapping configured in the account aggregation ? I tried root path as $ and in the response mapping userid : userids[\*] but it only return one account (userid is in the account schema).

[  
{  
“cohortid”: 001,  
“userids”: [  
123456,  
456789,  
891836,  
…  
]  
}  
]

Thanks  
Vinit Lodaya

---

<div class="post-metadata">

**Author:** ![alejandro\_gilhammer](https://avatars.discourse-cdn.com/v4/letter/a/cab0a1/32.png) [@alejandro\_gilhammer](https://developer.sailpoint.com/discuss/u/alejandro_gilhammer)\
**Post date:** [August 10, 2022, 9:03pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350/2 "2022-08-10T21:03:44Z")

</div>

Have you tried with: $.[0].userids.\*

> **[JSONPath Online Evaluator](https://jsonpath.com/)**
>
> JSONPath Online Evaluator

---

<div class="post-metadata">

**Author:** ![vinit\_lodaya](https://avatars.discourse-cdn.com/v4/letter/v/ccd318/32.png) [@vinit\_lodaya](https://developer.sailpoint.com/discuss/u/vinit_lodaya)\
**Post date:** [August 10, 2022, 9:51pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350/3 "2022-08-10T21:51:30Z")

</div>

Hello @alejandro_gilhammer,  
Tried $.[0].userids.\* with blank root path and it doesnt return any accounts.

Thanks  
Vinit Lodaya

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [August 11, 2022, 2:45pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350/4 "2022-08-11T14:45:12Z")

</div>

It’s possible that your JSON response is not valid JSON. Technically, 001 is not a valid number type in JSON, but your `cohortid` uses 001. A valid number would be 1. If `cohortid` needs the leading 0’s, then it would be more appropriate for it to be a string type, like “001”.

I’m not sure if the CCG logs are capturing this type of error, but it can certainly cause issues with any tool that needs to consume JSON. You can see this error in action by pasting your sample in a JSON validator tool, like [json validator at DuckDuckGo](https://duckduckgo.com/?q=json+validator).

My educated guess is that `cohortid` is causing validation issues and preventing any JSONpath from working. If you have control over target webservice, then making `cohortid` a string might fix this. If you don’t have control, then I suspect you will need to create an after operation rule to manually parse this response.

---

<div class="post-metadata">

**Author:** ![vinit\_lodaya](https://avatars.discourse-cdn.com/v4/letter/v/ccd318/32.png) [@vinit\_lodaya](https://developer.sailpoint.com/discuss/u/vinit_lodaya)\
**Post date:** [August 11, 2022, 3:49pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350/5 "2022-08-11T15:49:55Z")

</div>

Hello @colin_mckibben,

I changed the cohortid to 001 to mask confidential data. It is a 3-digit number without quotes. I validated the json at DuckDuckGo and it does say that the json is valid. My guess is that the connector is considering the entire list of userids as one user when I used $[0] as the root path and userids.[\*] in the response mapping for userid. I will take a look at the ccg logs to see if I can find something useful.

Thanks  
Vinit Lodaya

---

<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:** [July 19, 2023, 2:23pm UTC](https://developer.sailpoint.com/discuss/t/identitynow-webservices-connector-json-response-mapping/5350/6 "2023-07-19T14:23:26Z")

</div>