---
title: "Move an application to a different stage within the same job or transfer to another job"
method: POST
path: "/v3/applications/{id}/move"
tags: ["Applications"]
---

# Move an application to a different stage within the same job or transfer to another job

`POST /v3/applications/{id}/move`

Advance the candidate to a new interview stage. `from_stage_id` is required and must match the candidate's current stage — it acts as a guard against stale move requests. Provide `to_stage_id` to move within the same job, or `to_job_id` to transfer the application onto a different job (the candidate lands on that job's first interview stage). A successful move fires any configured stage transition rules, including automated emails sent from `email_from_user_id` (or a global address when supplied via Greenhouse configuration).

## Path parameters

- `id` integer, required

## Request body

- object
  - `from_stage_id` integer, required
  - `to_stage_id` integer
  - `to_job_id` integer
  - `email_from_user_id` integer

## Response `204`

Successful (No Content)

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `422` — Unprocessable Content

---

[API](https://skmtc.net/greenhouse/apis/auth-api.md) · [All operations](https://skmtc.net/greenhouse/apis/auth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/greenhouse/auth-api/versions/9517a2e54640/schema)