---
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`

## Request

- Base URL: `https://harvest.greenhouse.io`
- URL: `https://harvest.greenhouse.io/v3/applications/{id}/move`
- Auth: one of:
  - OAuth 2
    - Authorization code: `https://auth.greenhouse.io/authorize`
    - Client credentials
    - Token URL: `https://auth.greenhouse.io/token` scopes: `harvest:applications:move`
  - HTTP bearer

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.dev/greenhouse/apis/harvest-api.md) - [All operations](https://skmtc.dev/greenhouse/apis/harvest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/greenhouse/apis/harvest-api/revisions/822822e3f771?raw)