Moving and Rejecting Candidates

You can take automated action in the ATS by moving an application to a stage or rejecting it. These actions work on any application that Kombo has synced — regardless of whether it was originally created through Kombo or already existed in the ATS before the customer connected.

Moving Application Stage

To move an application, you need the application ID and the stage ID to move it to.

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.

• Enable the Set Application Stage scope in your scope configuration.

Use the Move Application Stage endpoint with the target stage:

{
  "stage_id": "3PJ8PZhZZa1eEdd2DtPNtVup"
}

If you’re implementing screening, you’ll typically save the target stage ID during the screening trigger stage setup.

Reject Applications

Use the Reject Application endpoint to reject an application.

• Enable the Reject Applications scope in your scope configuration.

To get possible rejection reasons, use the Get Rejection Reasons endpoint. Then pass the reason and an optional note:

{
  "rejection_reason_id": "3PJ8PZhZZa1eEdd2DtPNtVup",
  "note": "Candidate was a great culture fit but didn't bring the hard skills we need."
}

Rejecting an application may trigger automated workflows in your customer’s ATS (e.g., sending a rejection email to the candidate). Make sure your customer is aware of this before enabling automated rejections.