---
title: Greenhouse Integration Setup
slug: greenhouse-integration-setup
docTags: rl7p3XLQknqPB1UQ70cu_,b-RUvvYJSAyhoa4qcA_nj,G8dmC6tNw9fak7qGrSH3Z
createdAt: 2025-07-10T10:29:23.993Z
---

This article explains how to set up the Greenhouse integration, including creating Harvest V3 API credentials, configuring Greenhouse webhook events, and configuring your Greenhouse subdomain to enable direct links into your Greenhouse instance. 

:::hint{type="info"}
This route is for organizations using Ashby for Analytics only. For more on the Greenhouse migration for all-in-one organizations, see [Greenhouse → Ashby Recruiting API Migration](docId\:cRJSTuGNmwNJ59jlL3-Tp).
:::

# Step one: Configure Harvest V3 API credentials

To create your API credentials (also referred to as a Client ID and Client Secret pair) for the Greenhouse integration:

1. In Greenhouse, click the **Configure** icon > **Dev Center** > **API Credential Management**.
2. Click `Create new API credentials`.
3. Fill in the fields:

   - **API type:** Harvest V3 (OAuth)
   - **Description:** Something identifiable, e.g., "Data Sync Integration" (do not include "Ashby" in the description).

   ![The Create new credential page in Greenhouse.](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/Xdfq59m22BkK0h_u3rvaw_creating-a-new-credential-in-greenhouse.jpg)
4. Proceed to the permissions/scopes screen.

## Set the required scopes

Select read scopes on all objects. This grants "list" access, meaning Ashby can list data for each object.

You may see items such as:

- `harvest:candidates:list`
- `harvest:applications:list`
- `harvest:notes:list`
- `harvest:application_stages:list`
- `... (other endpoints)`

Save the credential.

## Copy the Client ID and Client Secret

After saving, Greenhouse displays your **Client ID** and **Client Secret**.

# Step two: Set up Greenhouse webhooks

Configure your Greenhouse webhooks to capture certain events in real time, such as candidate stage transitions, hires, and various record deletions. For more on configuring webhooks, see [Setting up Greenhouse Webhooks](docId\:HgfQAxE7EcYxqsb2WjkoR).

# Step three: Locate and configure your Greenhouse custom subdomain

Your Greenhouse instance may have a custom subdomain, such as your company name or one of Greenhouse's multiple servers.

To find your subdomain, log in to Greenhouse and view any candidate or job profile. Your URL has the form `[subdomain].greenhouse.io/...`. Once you have found your subdomain, enter it in the **Subdomain** field in your **[Admin > Integrations > Greenhouse](https://app.ashbyhq.com/admin/integrations/greenhouse)** settings.

![An example Greenhouse subdomain](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/K5la_OOFduxHsrhyv1dDB_screenshot2022-05-13at33809pm.png)

After you update your subdomain, a `View in Greenhouse` button appears when you view a candidate profile. This links directly to your candidate profiles. Additionally, [Alerts](docId\:fCkR-kKHNMJZ6vuU3kRvW) provide links to your candidate profiles for convenient access.

![The View in Greenhouse button on a candidate profile.](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/0TWcvEeYOlyFWlCyGcFkX_screenshot2022-11-21at21535pm.png)

# Step four: Enter your API credentials in Ashby

You can find your Greenhouse integration configuration in your admin section by navigating to **[Admin > Integrations > Greenhouse](https://app.ashbyhq.com/admin/integrations/greenhouse)**. This is where you enter your API credentials and subdomain.

![The Greenhouse integration page in Ashby.](https://api.archbee.com/api/optimize/0p8tQ--ZZOxRtkVp6Qr-e/g78VJPz06n0oUWkk_RlSv_greenhouse-api-migration-docs-harvest-v1-to-v3-google-docs-2026-08-14-at-90916-am.jpg)

- **Client ID:** Enter your client ID (or client key).
- **Client Secret:** Enter your generated client secret.
- **Custom Subdomain:** Enter your custom subdomain to enable linking directly to candidate profiles from Ashby.

:::hint{type="success"}
Adding the API credentials initiates your initial data sync. After your initial data sync completes, regular syncs continue once per hour to automatically ingest new data and updates. Ashby displays the last successful sync time in your Ashby user's timezone.
:::