Data 360: Consent API call Troubleshooting on Error

Error message

"INVALID_ID_FIELD: individulaId [ID] not exists"

{
    "results": {
        "result": "Failure",
        "errorCode": "PROBLEM_PROCESSING_REQUEST",
        "errorMessage": "Problem processing request: INVALID_ID_FIELD: individualId [Individual ID] not exists."
    }
}

Resolution

There is no default consent data created for the profile when it is first created. Therefore, a GET call will return an INVALID_ID_FIELD exception if a PATCH request has not previously been executed for the Individual ID. Make a PATCH call to set the consent flag for that profile before executing a GET request. 

For example, a PATCH call to the endpoint /services/data/v63.0/consent/action/processing?ids=A123&mode=cdp&status=optin will return the following response indicating that the Individual ID A123 is updated with a true value for shouldforget:

{
    "cdpResult": {
        "A123": {
            "result": "Success",
            "shouldforget": true
        }
    }
}

Subsequently, if a GET call is then made for this Individual ID it will also return the currently consent status and no longer return a INVALID_ID_FIELD exception.