Niches · Recruiting & applicant tracking

Advance, reject or annotate an application with notes and feedback

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

0companies, full fit
12companies, fit with a limit
17companies carry the tag
12share of the category's work
3first-hand accounts

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. No docs we read state these figures, so they don't count against a listing here.

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 12

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.

ListingWhy
Ashby B
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. source
Breezy HR D
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. source
Bullhorn D
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. source
Greenhouse C
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. source
Lever E
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. source
Manatal D
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. source
Pinpoint C
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. source
Recruitee D
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. source
SmartRecruiters B
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. source
Teamtailor D
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. source
Workable B
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. source
Zoho Recruit C
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. source

Couldn't check 1

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

ListingWhy
Gem F
Gem Software, Inc.
Stage and note endpoints would be in the ATS reference on api.gem.com, which robots.txt closes.

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
Himalayas Remote Jobs MCP D
Himalayas Remote Jobs Pty Ltd
No application stage exists to move; the job seeker's tracker status is the seeker's own record. source
NeverApply C
Kasovy LLC
No employer pipeline exists to move an application through. source

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.

The same as data: /api/v1/use-cases/recruiting.move-stage.json, or the MCP tool get_use_case with id recruiting.move-stage. Other jobs in this category: /api/v1/niches?category=recruiting.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.