Greenhouse Integration in headhuntr.io

To configure Headhuntr.io - Greenhouse Integration, you will need to create a Harvest API Key. Follow the steps in this guide to create the key and verify that the given permissions and credentials are selected when configuring the Headhuntr.io integration.

The guide has the following Steps:

1. Check permissions for your account in Greenhouse
2. Retrieve Greenhouse User ID 
3. Create a Harvest API Key in Greenhouse
4. Configure Webhooks

STEP 1: Check permissions for your account in Greenhouse

To enable the Greenhouse- Headhuntr.io integration, the user setting up the configuration is required to have the following developer’s permission:

• Manage ALL organization’s API Credentials
• Manage and configure webhooks

If you do not have the required permissions, contact a Greenhouse user in your organization with Site Admin level permissions with the permissions: Can edit another user's advanced permissions to give you access to the required permissions for your account. The user with Site Admin level permissions can give you access to the required permissions by navigating to the Configure icon >Users > Select Your Name > Permissions> Developer Permissions> Select required permissions

---

STEP 2: Retrieve Greenhouse User ID 

Headhuntr.io would also require a Greenhouse recruiting ID for all the users of the company who would be using the integration. It is required to associate the user with the data sent via integration by using the On-Behalf-Of header. The user with site admin level permissions can download the Greenhouse user IDs for the users by navigating to the Configure icon >Users >Export to Excel. Once the export to excel is clicked, a spreadsheet will be downloaded.

A. Click Configure icon > Users> Export to Excel

B. Downloaded excel with Greenhouse ID of users in the User ID column

---

STEP 3: Create a Harvest API Key in Greenhouse

The next step is to generate a Harvest API key with the required permissions for the integration. The following steps need to be followed:

• A. Navigate to Configure and select Dev Center
• B. Select API Credentials
• C. Select Create New API Key
• D. Select the following options in the Create New Credential:
  • API TYPE: Harvest
  • Partner: Headhuntr.io
  • Description: Harvest API Key for Headhuntr
• E. Select Manage Permissions
• F. Select the required permission by Headhuntr and copy the API key
• G. Save

If you do not have the required permissions, contact a Greenhouse user in your organization with Site Admin level permissions with the permissions: Can edit another user's advanced permissions to give you access to the required permissions for your account. The user with Site Admin level permissions can give you access to the required permissions by navigating to the Configure icon >Users > Select Your Name > Permissions> Developer Permissions> Select required permissions

A. Navigate to Configure and select Dev Center

B. Select API Credentials

C. Select Create New API Key

D. Select the following options in the Create New Credential window:

E. Select Manage Permissions

Click Manage Permissions to generate the Harvest API key. If you selected a partner in the Partner dropdown list, the appropriate permissions are assigned to the API key automatically. If the partner was not available in the dropdown, you can add permissions to the key in a subsequent step.

F. Choose Permissions

Headhuntr.io would require the following permissions to read the data and write/push candidates using Harvest API to the Greenhouse account. No Delete permissions are required by Headhuntr.io

• Applications (Required)
  • GET: Retrieve Application 
  • PATCH: Update Application
• Candidates (Required)
  • GET: Retrieve Candidate 
  • GET: List Candidates (Optional) 
  • PATCH: Edit Candidate (Optional) 
  • POST: Add Note   
  • POST: Add Attachment  
  • POST: Add Application  
  • POST: Add Candidate  
  • POST: Add Education  
  • POST: Add Employment  
  • POST: Add Prospect  
• Users (Required)
  • GET: List Users 
• Departments
  • GET: List Departments 
  • GET: Retrieve Department 
• Jobs (Required)
  • GET: List Jobs 
  • GET: Retrieve Job   
• Job Posts (Required)
  • GET: List Job Posts 
  • GET: Retrieve Job Post  
  • GET: List Job Posts for Job   
  • GET: Retrieve Job Post for Job  
• Job Stages (Optional)
  • GET: List Job Stages 
  • GET: List Job Stages for Job 
  • GET: Retrieve Job Stage 
• Sources (Optional)
  • GET: List Job Stages 
• Prospect Pool (Optional)
  • GET: List Prospect Pools  
  • GET: Retrieve Prospect Pool  
• Departments(Optional)
  • GET: List Departments  
  • GET: Retrieve Department 

G. Copy the generated API Key

In the subsequent dialog box, click Copy to save your API key. Store the API key in a secure location as it will be required when configuring the integration in Headhuntr.io. Click I have stored the API Key once you have copied and saved the key.

H. Save

On the subsequent page, confirm the correct permissions are assigned to the Harvest API key for Headhuntr, or assign the permissions yourself by clicking the appropriate checkboxes. Once, the permissions are confirmed, click Save at the bottom of the page. Once all the steps are complete, your Harvest API Key for the Greenhouse integration in Headhuntr.io is created.

---

STEP 4: Configure Webhooks

To configure webhooks for the Headhuntr.io integration, you would require the following information from Headhuntr.io.

• Endpoint URL
• Secret Key

This information will be provided to you by the Headhuntr.io Onboarding Team and can be used to configure all the required webhooks.

To configure webhooks for the integration, follow the steps listed below:

• A. Click Configure icon > Dev Center > Web Hooks
• B. Click Web Hooks from the subsequent page
• C. Enter the Name, When, Endpoint URL, and Secret Key in available fields
• D. Select Create Web hook to finish

A. Click Configure icon > Dev Center > Web Hooks

B. Click Web Hooks from the subsequent page

On the Create a New Web Hook page, provide the following information to create your first webhook.

Webhook 1

• Name: Headhuntr.io-Candidate Hired
• When: Candidate has been hired
• Endpoint URL: The Endpoint URL provided by Headhuntr.io
• Secret Key: The secret key provided by Headhuntr.io
• Error recipient email: ats@headhuntr.io

When finished, click Create Webhook and follow the same process for the additional fourteen webhooks required using the following information. 

Webhook 2

• Name: Headhuntr.io-Candidate Stage Change 
• When: Candidate has changed stage 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 3

• Name: Headhuntr.io-Candidate/Prospect Rejected
• When: Candidate or Prospect rejected
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 4

• Name: Headhuntr.io-Candidate/Prospect Unrejected 
• When: Candidate or Prospect unrejected 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 5

• Name: Headhuntr.io-Candidate/Prospect Updated 
• When: Candidate or Prospect updated 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 6

• Name: Headhuntr.io-Candidate Deleted
• When: Delete Candidate 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 7

• Name: Headhuntr. io-Prospect Created 
• When: Prospect created 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 8

• Name: Headhuntr.io-Candidate Merged 
• When: Merged Candidate 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 9

• Name: Headhuntr.io-Job Created
• When: Job Created 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 10

• Name: Headhuntr.io-Job Deleted 
• When: Job Deleted
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 11

• Name: Headhuntr.io- Job Post Created 
• When: Job Post Created 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 12

• Name: Headhuntr.io- Job Post Deleted 
• When: Job Post Deleted 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 13

• Name: Headhuntr.io-Job Post Updated 
• When: Job Post Updated 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Webhook 14

• Name: Headhuntr.io-Job Updated 
• When: Job Updated 
• Endpoint URL: The Endpoint URL provided by Headhuntr.io 
• Secret Key: The secret key provided by Headhuntr.io 
• Error recipient email: ats@headhuntr.io 

Configuration for Headhuntr.io-Greenhouse integration in Greenhouse is now complete. Navigate to Headhuntr.io (License Information>Configure ATS) and add the Harvest API Key generated from this configuration.

In the user mapping page of the configuration wizard, use the downloaded excel file and navigate to the User ID column. Copy the User ID for each user from excel and paste it into the ATS Id column of the user mapping.

Review the user mapping and activate the configuration to allow the users to start using the Integration.