Skip to main content
PUT
/
ats
/
applications
/
{application_id}
/
stage
Move application to stage
curl --request PUT \
  --url https://api.kombo.dev/v1/ats/applications/{application_id}/stage \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Integration-Id: <x-integration-id>' \
  --data '{
  "stage_id": "3PJ8PZhZZa1eEdd2DtPNtVup"
}'
{
"status": "<string>",
"data": {},
"warnings": [
{
"message": "<string>"
}
]
}
This endpoint requires the permission Set application stage to be enabled in your scope config.

Example Request Body

{
  "stage_id": "3PJ8PZhZZa1eEdd2DtPNtVup"
}

Authorizations

Authorization
string
header
required

Create an API key on the Secrets page in the Kombo dashboard.

Headers

X-Integration-Id
string
required

ID of the integration you want to interact with.

Path Parameters

application_id
string
required

The Kombo ID of the application you want to move to a different stage.

Body

application/json

PUT /ats/applications/:application_id/stage Request body

stage_id
string
required

The Kombo ID of the stage to move the application to. This stage must be allowed for the job that the application is connected to. Get available stages from the stages property on the job, not from the deprecated application-stages endpoint.

remote_fields
object

Additional fields that we will pass through to specific ATS systems.

Response

PUT /ats/applications/:application_id/stage Positive response

status
string
required
Allowed value: "success"
data
object
required
warnings
object[]
required

These are the interaction warnings that are shown in the dashboard. They are meant to provide debug information to you. We recommend logging them to the console.

I