# Advance, reject or annotate an application with notes and feedback

> Advance, reject or annotate an application with notes and feedback: 0 companies fully do it, 12 with a limit, 17 carry the tag. Every listing in Recruiting & applicant tracking with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/recruiting.move-stage/
- Markdown: https://www.anchorterminal.com/niches/recruiting.move-stage/index.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/niches/recruiting.move-stage/index.min.md (~530 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/recruiting.move-stage/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 12 | 17 | 12 | 3 |

## What counts as done

The application's stage, status and note all change, a re-read shows the new stage on the application (not only the candidate), and an unknown stage name returns an error listing valid stages.

Measured, for our own tests: the change takes one or two calls.

How agents ask for it: move Priya to onsite; reject these five with the standard reason; add my interview notes to her application; mark documents received

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Ashby (Ashby, Inc.)**: application.changeStage takes interviewStageId and archiveReason and returns the application, but candidate.createNote writes to the candidate, not the application, and whether an unknown stage error lists valid stages isn't documented.
- **Breezy HR (Breezy HR, Inc. (Jacksonville, Florida), part of Learning Technologies Group plc)**: PUT .../stage takes stage_id and returns 400 when it isn't in the position's pipeline (without listing valid stages), and notes post to the candidate's stream on that position, but the move fires stage actions and HRIS syncs.
- **Bullhorn (Bullhorn, Inc.)**: JobSubmission status is a field updated by entity PUT or POST and massUpdate covers JobSubmission, with Note entities linked through NoteEntity, but statuses are free-form per agency and the fair-use permission still gates AI use.
- **Greenhouse (Greenhouse Software, Inc.)**: POST /v3/applications/{id}/move takes from_stage_id as a stale-move guard and to_stage_id, reject records a reason, and notes accept application_id, but a 422 body listing valid stages isn't shown.
- **Lever (Employ, Inc.)**: Stages are listable and notes and feedback post to the opportunity (Lever's application) with perform_as, but the stage-change request body and its error behaviour couldn't be read from the closed reference.
- **Manatal (Manatal. No registered entity is named in the terms, the DPA or the privacy policy. Offices are listed in Singapore and Bangkok, and the terms are governed by Thai law)**: PATCH /matches/{id} with job_pipeline_stage.id moves an application and /job-pipelines lists stage ids, but notes write to the candidate or job, not the match, and an unknown stage's error isn't documented.
- **Pinpoint (The Infuse Group Limited, trading as Pinpoint Software (Jersey, registration number 124135))**: Update Application takes a stage relationship and Create Comment attaches to an application by commentable type and id, but the error for an unknown stage and the response body after a move aren't described.
- **Recruitee (Recruitee B.V. (Netherlands, company number 63881829), trading as Tellent. The contracting entity depends on the customer's location and can also be Recruitee Inc., Recruitee GmbH, Teamrise SAS or YooniQ Solutions GmbH)**: PATCH /placements/{id}/change_stage moves the application and a candidate_moved webhook fires with the stage change, but notes are on the candidate and the error for an unknown stage wasn't read.
- **SmartRecruiters (SmartRecruiters, Inc.)**: PUT /candidates/{id}/jobs/{jobId}/status moves the application on that job and status history is readable, but the variant without jobId acts on the most recently updated application, and error bodies for unknown statuses weren't read.
- **Teamtailor (Teamtailor AB (Sweden, registration number 556936-6668), Östgötagatan 16, Stockholm)**: PATCH /job-applications/{id} changes the stage relationship and notes can link to a job application, but the response to an unknown stage isn't described; the MCP tool move_application_to_stage wasn't read here.
- **Workable (Workable Software Limited (England and Wales, company number 08125469), with Workable Inc. in the US and Workable Software Single Member Private Company in Greece)**: /candidates/:id/move takes the target stage with member_id, /jobs/:shortcode/stages lists stages and disqualify takes a reason, but comments go on the candidate's timeline, not a job-specific application, and hired moves can need a requisition.
- **Zoho Recruit (Zoho Corporation Private Limited)**: PUT /{module}/status sets Candidate_Status with comments and jobids, scoped per module, but acc-29 found the status changing while the pipeline stage didn't move and comments didn't save on the application, and acc-30 saw every update fail with 4834.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Gem (Gem Software, Inc.)**: Stage and note endpoints would be in the ATS reference on api.gem.com, which robots.txt closes.

- not this job: Himalayas Remote Jobs MCP (Himalayas Remote Jobs Pty Ltd): No application stage exists to move; the job seeker's tracker status is the seeker's own record.
- not this job: NeverApply (Kasovy LLC): No employer pipeline exists to move an application through.

## What stops agents finishing

- status changes but pipeline stage does not, with a success response
- notes land on the candidate, not the application
- a personal token with full user permissions is the only write credential

## Around it

Before: recruiting.pipeline-read, meeting-capture.transcript. After: email.send, recruiting.schedule-interview.

## Where this comes from

Weight 12 of 100 in Recruiting & applicant tracking: 3 of 32 accounts (two Zoho Recruit forum threads where stage or status writes did not stick, and an interview-notes product planning a push into Teamtailor and Recruitee); weight lifted because write calls for stages are a buyer check and the test sentence includes a stage move.

As data: https://www.anchorterminal.com/api/v1/use-cases/recruiting.move-stage.json, or the MCP tool get_use_case with id recruiting.move-stage. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
