List Greenhouse scheduled interviews and fetch interviewer availability for scheduling coordination
domain: greenhouse.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
GET https://harvest.greenhouse.io/v1/scheduled_interviews to list all upcoming scheduled interviews; filter by job_id, application_id, or created_after/created_before query parameters to scope results.
Each scheduled interview object contains an interviewers array with the Greenhouse user_id, name, and scorecard_submitted status for each interviewer.
To check interviewer availability within Greenhouse (if using the Interview Kit feature), GET /v1/users/:user_id to retrieve the user's profile and linked calendar connection status.
Cross-reference the interviewers against GET /v1/users to build a complete roster with email addresses for external calendar coordination.
To create a scheduled interview, POST /v1/scheduled_interviews with application_id, interview_id, status, and interviewers array containing user_id entries.
Update a scheduled interview (e.g., reschedule) with PATCH /v1/scheduled_interviews/:id providing updated start, end, and location fields.
Known gotchas
Greenhouse does not expose calendar availability slots via the Harvest API; for real-time interviewer availability, you must integrate with Google Calendar or Microsoft 365 directly and match against interviewers by email.
The interview_id in a scheduled interview refers to the interview step definition in the interview plan, not the scheduled_interview_id; these are different IDs and should not be used interchangeably.
Deleting a scheduled interview does not notify interviewers; send calendar cancellations separately if interviewers were previously invited via calendar integration.
Give your agent this knowledge — and 6,400+ more routes
One MCP install gives any agent live access to the full route map across 2,100+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp