> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aperium.apps.hillspire.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Greenhouse

> Connect Aperium to Greenhouse Recruiting through the Harvest V3 API, with each user supplying their own credentials.

The Greenhouse integration gives agents read access to your Greenhouse Recruiting data — jobs, candidates, applications, offers, approvals, and org structure — over the [Harvest V3 API](https://harvestdocs.greenhouse.io/docs/authentication), plus approval-gated writes for job and org management. It is a **per-user** connector: each user supplies their own Greenhouse API credentials, and every call runs with that user's Greenhouse permissions and audits as them.

<Note>
  Unlike most tenant-wide connectors, Greenhouse has **no shared admin credential**. Each user enters their own client ID and secret. There is nothing for an admin to configure once for everyone.
</Note>

## What you'll need

For **each user** who will use Greenhouse:

* A Greenhouse **Harvest v3 (OAuth)** API credential — its **client ID** and **client secret**, created under **Dev Center → API Credentials** in Greenhouse.
* That credential must belong to a Greenhouse **Site Admin** (the V3 list endpoints require it).
* The user's Aperium email must match their Greenhouse primary email — Aperium resolves the Greenhouse user identity by primary email when the credential is saved.

## Setup (each user does this once)

<Steps>
  <Step title="Create a Harvest v3 credential in Greenhouse">
    In Greenhouse, go to **Dev Center → API Credentials** and create a **Harvest v3 (OAuth)** credential under a Site Admin account. Copy its client ID and client secret.
  </Step>

  <Step title="Add the credential in Aperium">
    Open the **Integrations** page, find the **Greenhouse** tile, and open its personal credential form. Enter your **client ID** and **client secret**. The token endpoint is a fixed Greenhouse value and is pre-filled — leave it as is.
  </Step>

  <Step title="Save and verify">
    On save, Aperium resolves your Greenhouse identity by primary email. A save is rejected if there is no match, or if the account is deactivated or not a Site Admin. Once connected, ask an agent to list open jobs or pending offers to confirm the tools work.
  </Step>
</Steps>

## What agents can do

**Read (17 searches)** — jobs, openings, job posts, interview stages, offers, approval flows, approver groups, approvers, candidates, applications, users, user roles, departments, offices, sources, custom fields, and close reasons. Question-shaped reports such as offers pending approval or job-approval status are expressed as filters and joins over these searches.

**Write (10 tools, approval-gated)** — create and update jobs, create and update openings, update job posts, create departments and offices, grant a job permission, and add a job hiring manager or owner. Every write pauses for human approval before it runs and executes with the invoking user's Greenhouse permissions. Destructive operations (delete / archive) and approval-trigger writes are out of scope.

## Notes

* **Single account.** Greenhouse does not support linking multiple accounts per user.
* **Totals honesty.** Bounded corpora report exact totals; candidates and applications are cursor-paged with no server total, so their counts are reported as unknown unless a filtered stream fully exhausts.