List applications
Applications represent a candidate's journey on a specific job — the bridge between a candidate (person) and a job. Each candidate can have one application per job (and prospect applications can be jobless or attached to multiple prospective jobs). Scope the list with one of the parent-id arrays — candidate_ids, job_ids, job_post_ids, source_ids, referrer_ids, stage_ids, or prospective_job_ids — to filter by the matching foreign key. Pass ids directly to fetch specific applications by id (max 50 per request).
Request
- Base URLhttps://harvest.greenhouse.io
- URLhttps://harvest.greenhouse.io/v3/applications
- Auth
- OAuth 2Authorization code: https://auth.greenhouse.io/authorizeClient credentialsToken URL: https://auth.greenhouse.io/token scopes: harvest:applications:list
- or HTTP bearer
Query parameters
Cursor link for pagination from previous page response header. Do not use any other parameters when using this.
Number of results per page
Comma separated list
Comma separated list
Return only applications attached to these job (hiring plan) ids. This is the application's current job, not any prospective placement — use prospective_job_ids for that.
Return only applications that have a prospective placement on one of these job (hiring plan) ids. Prospective jobs are jobs a candidate is being considered for before being moved onto them; use job_ids to filter by the application's current job.
Comma separated list
Comma separated list
Return only applications attributed to these referrer ids. A referrer is the Greenhouse Referrer record (see GET /v3/referrers) — not a user id. Look up the referrer id for a user via that endpoint first.
Return only applications whose current stage matches one of these stage IDs. These are application-stage IDs — the same value returned as stage_id on each application — not job interview stage definition IDs (IDs from GET /v3/job_interview_stages will not match).
Return only applications whose current job interview stage matches one of these stage IDs. These are job interview stage definition IDs (IDs from GET /v3/job_interview_stages).
Comma separated list of fields to return
Filter by the application's lifecycle status, using the same values as the status field on each application. in_process returns applications still in process; rejected, hired, and converted filter by terminal state. active is a deprecated alias for in_process.
Filter applications by current stage name (exact match, case sensitive). Useful when you want to slice by stage without first looking up its id.
Return only applications whose application custom field value matches this single-select or multi-select option id.
Filter by the application's last_activity_at, which usually reflects activity across all of the candidate's applications. Pass any combination of gte, lte, gt, lt as ISO-8601 date-times (e.g. last_activity_at[gte]=2026-01-01T00:00:00Z&last_activity_at[lte]=2026-04-01T00:00:00Z).
When true, return only prospect applications; when false, only non-prospect (candidate) applications. Omit to include both.
Response
Successful
Changes
No recorded changes to this operation across all 1 revision of this API.