Retrieve a list of ATS applications
Use this endpoint to trace where candidates stand in the hiring pipeline and how they got there — every interview plan stage an application has reached and when it entered and left each one.
Token scopes: ats:read, worker:read
Authentication
Query parameters
Filter by the CURRENT interview plan stage IDs (comma-separated). Applications that have since moved to another stage are excluded — use reached_interview_plan_stage_ids for those.
Filter by interview plan stage IDs the application has EVER been in (comma-separated), including applications that have since advanced, been hired or been archived.
Return only applications that moved to their current stage strictly before this ISO 8601 datetime (stalled candidates)
Filter by archivation reason IDs (comma-separated); see GET /rest/ats/reasons with reason_group_slug=CANDIDATE_ARCHIVATION
How candidate_tag_ids are combined: ANY (default) matches candidates with at least one of the tags, ALL requires every tag
Optional expansions to embed on each item. STAGE_HISTORY adds the full stage timeline with entered/exited timestamps.
Filter by candidate tag IDs (comma-separated)
Filter by application source (comma-separated)
Filter applications by current stage category type slugs (comma-separated)
Filter applications by current stage default type slugs. Use ‘others’ for custom stages (comma-separated)
Filter applications updated after this timestamp (ISO 8601 format)
Response
Cursor to fetch the next page; null when there are no more pages