Connect Greenhouse to Rig

    Sync your Greenhouse recruiting data into Rig, so hiring questions sit beside headcount and cost. Rig reads it through the Harvest API with a single API key that has read access to the endpoints you choose.

    Before you start

    • You need the Can manage ALL organization's API Credentials permission under Developer permission in Greenhouse.
    • Decide which objects you want synced. A key without permission on an endpoint gets a 403 on that endpoint.

    Step 1: Create a Harvest API key

    1. In Greenhouse, go to Configure → Dev Center → API Credential Management.
    2. Create a new credential and set API Type to Harvest.
    3. Grant read (GET) permission on each endpoint you want Rig to sync. Rig reads candidates, applications, jobs, offers, scorecards, scheduled interviews, users, departments and offices.
    4. Copy the API key.

    Change permissions later
    To add or remove endpoints on an existing key, open API Credential Management and click Manage Permissions next to the Harvest key.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Greenhouse, open the card and click Connect.
    3. Harvest API key: Paste the Harvest API key you copied.
    4. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Greenhouse lands in its own greenhouse schema in your warehouse:

    • Candidates and applications: every candidate and their applications.
    • Jobs and offers: job requisitions and the offers made against them.
    • Scorecards and interviews: interviewer scorecards and scheduled interviews.
    • Org structure: users, departments and offices.

    Good to know

    • Greenhouse also has a public Job Board API for careers pages. That API cannot see candidates, so Rig uses Harvest.
    • Harvest uses HTTP basic auth over HTTPS with the key as the username and a blank password. Rig handles this for you.
    • If one stream fails with a 403, the key lacks read permission on that endpoint. Add it under Manage Permissions.
    • To disconnect Greenhouse, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Measure the hiring funnel end to end
    • Compare sourcing channels honestly
    • Connect hiring to headcount and spend

    More ideas for using Greenhouse

    Greenhouse documentation

    Was this guide helpful?