Skip to main content
Screening customers may also want to take automated action in the ATS by moving an applicant to a stage OR by rejecting the applicant automatically from their platform. You can also allow the recruiter to take these actions directly from your platform by implementing these actions with Kombo.

​
Moving Application Stage

When moving an application to a different stage within a customers ATS you will have to have identify the stage in which your customer would like the application to be moved to. In the Set Screening Trigger Stage you will have saved the stage id for the next stage in the application process after screening.
Always get stage IDs from the stages property on jobs, not from the deprecated /application-stages endpoint. Many ATS systems have job-specific stages. Using global stage IDs will often result in “Stage not found” errors.
  • To move an application in Kombo you need to set the scope configuration of Set Application Stage to enabled.
You can move an application in Kombo to a specified stage using the Move Application Stage Endpoint. In the request body you need to specify the specific stage you want to move the applicant too. 
{
  "stage_id": "3PJ8PZhZZa1eEdd2DtPNtVup"
}

​
Reject Applications

It is possible to reject candidates using the Reject Application Endpoint. In order to reject an application you will also need a rejection_reason_id which is available in your customers ATS. To get possible rejection reasons and rejection_reason_id you can use the Get Rejection Reasons Endpoint. Here you can add a note and a rejection_reason_id as to why the candidate is rejected in the body of the request. 
{
  "rejection_reason_id": "3PJ8PZhZZa1eEdd2DtPNtVup",
  "note": "Candidate was a great culture fit but didn't bring the hard skills we need.",
}
Be careful when using the reject candidate endpoint, as this may start an automated rejection process in your customer’s ATS.