Search candidates across the agency's hiring pipelines.
Results include each candidate's person, job, and current workflow stage.
Use the structured owner and stage filters for pipeline questions; do not put recruiter names, ownership, job status, or stage labels in the Lucene query.
person_owned_by_idsmeans candidates assigned to those users.job_owned_by_idsmeans candidates on jobs managed by those users.
If "a recruiter's candidates" is ambiguous, clarify which ownership meaning the user intends, or query both separately and label the results.
Resolve user, workflow-stage, and job-status IDs with their respective list tools, then pass them here.
For example, "who is close to an offer that this recruiter is representing" should use the recruiter's user ID with person_owned_by_ids, active job_status_ids, the relevant final interview/offer workflow_stage_ids, and exclude_rejected: true.
The optional query is only for candidate/person text such as name, title, company, skills, location, or email.
It supports Lucene field-qualified terms, ranges, and boolean operators.
Scroll pagination is supported.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
