Best Practice Recommendations based on Merge Response
Merge Response:
{
"Model With Duplicate Unique Field Exists",
"detail": "Candidate with unique field already exists",
"problem_type": "MODEL_WITH_DUPLICATE_UNIQUE_FIELD_EXISTS"
}Candidate might already exist. You can check by using the filters in your logs and finding that candidate with a 201 created response. Or, you can check via GET /Candidates Request.
If you are trying to update a Candidate's application, please use POST Application and pass the Candidate ID!
Merge Response:
"We've encountered an error while sending this request to the SmartRecruiters API. Please contact [email protected] if this problem persists."
Also possible that the Candidate might already exists. You can check by using the filters in your logs and finding that candidate with a 201 created response. Or, you can check via GET /Candidates Request.
OR it is possible that the JSON was incorrectly formatted. Check that your
modelis formatted correctly withremote_user_idincluded. Also, check the Field Support by Platform for that integration to see what is required for that integration.
Merge Response:
"We can't access this with your current permissions. Check https://app.merge.dev/issues for more information"
Check that the API Key / Credentials have the correct Read/Write permissions for Candidate.
Merge Response:
"The {object} could not be found."Check that the Remote User, Job, or any passed parameters exist in the 3rd party.
Merge Response
JSON Body is incorrectly formatted.
Check that your
modelis formatted correctly withremote_user_idincluded.Check the Field Support by Platform for that integration to see what is required for that integration.