Greenhouse

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

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.

VariableRequiredDescription
GREENHOUSE_API_KEYYesGreenhouse Harvest API key (used as the HTTP Basic username; the password is blank). Created in the Dev Center under API Credential Management Docs.
GREENHOUSE_API_PASSWORDNoLeave empty - Greenhouse Harvest Basic auth uses the API key as username with a blank password Docs.

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

ToolAccessDescription
List Jobs<br /><code className="reference-identifier">greenhouse__list_jobs</code>ReadList jobs
List Candidates<br /><code className="reference-identifier">greenhouse__list_candidates</code>ReadList candidates
Get Candidate<br /><code className="reference-identifier">greenhouse__get_candidate</code>ReadGet candidate
List Applications<br /><code className="reference-identifier">greenhouse__list_applications</code>ReadList applications
List Users<br /><code className="reference-identifier">greenhouse__list_users</code>ReadList users
List Job Stages<br /><code className="reference-identifier">greenhouse__list_job_stages</code>ReadList job stages
Move Application<br /><code className="reference-identifier">greenhouse__move_application</code>WriteMove active application to stage
Add Candidate Note<br /><code className="reference-identifier">greenhouse__add_candidate_note</code>WriteAdd candidate note

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.