# Book an interview on the application with interviewers and a time

> Book an interview on the application with interviewers and a time: 0 companies fully do it, 6 with a limit, 9 carry the tag. Every listing in Recruiting & applicant tracking with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/recruiting.schedule-interview/
- Markdown: https://www.anchorterminal.com/niches/recruiting.schedule-interview/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/recruiting.schedule-interview/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/recruiting.schedule-interview/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 | 6 | 9 | 10 | 2 |

## What counts as done

A scheduled interview record on the application with step, interviewers and start and end times, created in one call, readable back, and visible to the interviewers.

How agents ask for it: schedule a 45-minute technical interview with Sam and Lee next Tuesday; book the onsite loop for these three candidates; move the interview to Thursday

## 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.)**: interviewSchedule.create books interview events with interviewers and times, interviewSchedule.info reads it back and user.search finds interviewers by email, but whether interviewers get calendar invites isn't stated.
- **Bullhorn (Bullhorn, Inc.)**: Interviews are Appointment entities created by entity PUT with attendees and times, but the docs read don't describe interview-specific fields or invites, and the fair-use permission applies.
- **Greenhouse (Greenhouse Software, Inc.)**: POST /v3/interviews records an interview already on an external calendar at a job plan slot; it sends no calendar invites, and acc-11 got 403 creating one despite a Site Admin key and acting user.
- **Lever (Employ, Inc.)**: POST /opportunities/:id/panels and /interviews create externally managed interviews with interviewers and times, readable back, but they don't send invites from Lever and the field rules sit in the closed reference.
- **SmartRecruiters (SmartRecruiters, Inc.)**: The Interview API creates, updates and deletes interviews with timeslots, location and timezone, but interviewers are added by a separate session call, so a booking is two calls, and whether interviewers are notified isn't stated.
- **Zoho Recruit (Zoho Corporation Private Limited)**: Interviews are a module whose records are created through the records API, with a Cancel Interview endpoint, but interviewer assignment and invite behaviour weren't read in the pages opened.

## Couldn't check

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

- **Gem (Gem Software, Inc.)**: Gem markets scheduling automation, but no interview-write endpoint could be read from the closed API reference.
- **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)**: The listing says interviews can be scheduled, but the interview endpoints are only in the 11 MB generated reference, which wasn't read this run.

- not this job: Breezy HR (Breezy HR, Inc. (Jacksonville, Florida), part of Learning Technologies Group plc): No endpoint creates or moves an interview; interviews appear only inside the candidate meta bundle.
- not this job: Himalayas Remote Jobs MCP (Himalayas Remote Jobs Pty Ltd): Interview tools are mock-interview practice for job seekers; nothing books an interview with an employer.
- not this job: 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): No endpoint creates an interview; candidate meetings list AI Interviewer and Notetaker records only.
- not this job: NeverApply (Kasovy LLC): prepare_interview builds a prep pack; nothing books an interview.
- not this job: Pinpoint (The Infuse Group Limited, trading as Pinpoint Software (Jersey, registration number 124135)): Interviews can be listed, fetched and have their summary updated; no endpoint schedules one.
- not this job: Teamtailor (Teamtailor AB (Sweden, registration number 556936-6668), Östgötagatan 16, Stockholm): Interviews are list and show only in the API; no endpoint creates or moves one.
- not this job: 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): /events lists calls, interviews and meetings read-only; neither the API nor the MCP tool list creates or moves an interview.

## What stops agents finishing

- interviews are read-only (Workable, Pinpoint, Breezy)
- a write needs an acting user header or JWT subject the agent does not have, and returns 403
- the interview step id is only reachable through the job's stages

## Around it

Before: scheduling.find-slot, recruiting.pipeline-read. After: email.send, scheduling.create-event.

## Where this comes from

Weight 10 of 100 in Recruiting & applicant tracking: 2 of 32 accounts (create_interview 403 through a Greenhouse MCP, and a Nango integration for resume and interview tools); weight lifted because interview booking is a buyer check and several listings have no write call for it.

As data: https://www.anchorterminal.com/api/v1/use-cases/recruiting.schedule-interview.json, or the MCP tool get_use_case with id recruiting.schedule-interview. 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
