Any route that doesn’t use /cc
, /beta
, or /v3
are internal only routes. You won’t be able to call them yourself.
I was unable to find a beta or v3 API that returns the account correlation config. The v3 source API will only return the manager correlation config. I’ll talk to engineering about getting the account correlation added to the v3 sources API response.
In the meantime, it looks like you can use a cc
API to get the account correlation config. Please note that cc
is not a production supported API, and can change without notice. I wouldn’t advise using this in production critical applications.
You will need to find the sourceId used by CC, which is different than v3/beta. One way to get this ID is to check your address bar when inside a source in the UI:
Or, you can call the cc list sources endpoint.
GET https://{tenant}.api.identitynow.com/cc/api/source/list
To get the account correlation config, use this endpoint.
GET https://{tenant}.api.identitynow.com/cc/api/source/get/{sourceId}
This returns a response object that has the account correlation config:
"correlationConfig": {
"attributeAssignments": [
{
"complex": false,
"filterString": null,
"ignoreCase": true,
"matchMode": null,
"operation": "EQ",
"property": "identificationNumber",
"value": "id"
}
],
"id": "2c918084838b1cc90183a9ced42916c3",
"name": "Employees [source] Account Correlation"
},