Update candidate stage
Moves a candidate to a different pipeline stage within a job.
Flexible identification: Accepts job identification by job_id or job_name, candidate identification by candidate_id, candidate_email, or candidate_name, and stage identification by stage_id or stage_name.
Job resolution: The endpoint resolves the job in this order: job_id, the job associated with candidate_id, job_name, then the person’s most recent active candidacy created within the previous 180 days. When candidate_id is provided, its associated job takes precedence over job_name.
Discovering stage IDs/names: Use GET /v1/jobs/{id} to see the full pipeline_stages array with stage IDs, names, and ordering for a specific job.
Authorizations
Authenticate with a Bearer token: API key, OAuth token, or session token.
Body
Job UUID. Highest-precedence job identifier. Get IDs from POST /v1/jobs/search.
Job title to match. Used only when job_id and candidate_id do not resolve a job. If no job is resolved, the endpoint falls back to the person’s most recent active candidacy created within the previous 180 days.
1Candidate UUID. Its associated job is used after an explicit job_id and before job_name. Provide candidate_id, candidate_email, or candidate_name.
Candidate email to look up. Used when candidate_id is not provided.
Candidate full name to look up. Fallback when email and ID are not provided.
1Target pipeline stage UUID. Provide either stage_id or stage_name. Get IDs from GET /v1/jobs/{id} → pipeline_stages.
1Target pipeline stage name (e.g. "Technical Interview"). Used when stage_id is not provided.
1