Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: Basic auth.
  • Connection: HTTP Basic auth with GREENHOUSE_API_KEY as the username and GREENHOUSE_API_PASSWORD as the password.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Get Greenhouse access: You need a Greenhouse Recruiting account; ask your Greenhouse admin for access or request a demo/sandbox at https://www.greenhouse.com. Creating API keys requires the ‘Can manage ALL organization’s API Credentials’ developer permission.
  2. Create a Harvest API key: In Greenhouse, go to Configure (gear icon) → Dev Center → API Credential Management → Create New API Key, choose type ‘Harvest’, and grant only the endpoints you need (Jobs, Candidates, Applications).
  3. Store the key: Add GREENHOUSE_API_KEY=<your key> to your .env file and leave GREENHOUSE_API_PASSWORD empty. The Harvest API uses HTTP Basic auth with the key as username and a blank password.
  4. Find your user ID for writes: Write requests must include an On-Behalf-Of header with the numeric ID of the Greenhouse user performing the action (look it up via the Harvest Users endpoint or the Greenhouse UI).

​
Provider notes

  • Each API key is restricted to the endpoints granted at creation - a 403 usually means the key lacks that endpoint
  • All write endpoints (POST/PATCH/DELETE) require the On-Behalf-Of header for auditing
  • List endpoints return plain JSON arrays and paginate via per_page/page with RFC 5988 Link response headers
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as greenhouse__list_jobs with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.