All Collections
Alva Labs and Greenhouse integration
Alva Labs and Greenhouse integration

This is a step by step guide on how to complete the integration between Alva and Greenhouse

Pernilla Ahl avatar
Written by Pernilla Ahl
Updated over a week ago

Note: As a mutual customer of Greenhouse and Alva, you have two integration options. Feel free to speak to your Onboarding Specialist or Customer Success Manager about which is right for you.

Though, in general, we recommend using our [new] integration because it allows for Hiring Sync (the ability to sync user access between Greenhouse and Alva) and doesn't require candidates to be added to the job in Greenhouse in order for the job position to be created/synced in Alva.

If you have been recommended to use this integration or are simply looking to manage your existing integration, feel free to continue with the following steps.

1. Configure user setup permissions in Greenhouse Recruiting

In order to enable the Greenhouse Recruiting / Alva Labs integration, you will need the developer permission Can manage ALL organization’s API Credentials.

Step 1: Contact a Greenhouse Recruiting user in your organization with Site Admin level permissions with the additional user-specific permission Can edit another user's advanced permissions.

Step 2: Have the user with Site Admin level permissions edit your user account's permissions by navigating to the cogwheel (1) that signifies settings. Then the user with Site Admin level permissions needs to click Users (2). He/she will then arrive at a new page where he/she needs to locate and click on your name.

Step 3: The user with Site Admin level permissions should scroll down to the User-Specific Permissions panel on your user page and expand the Developer Permissions dropdown menu (1) and then tick the box next to "Can manage ALL organization’s API Credentials"(2). When finished, click "Save" (3).

2. Getting an API-Harvest key from Greenhouse

Step 1: In the Greenhouse website, click on the cogwheel (1). Next click on Dev Center (2). Then click on "API Credential Management" (3).

Step 2: Click "Create New API Key".

Step 3: A dialogue box will appear. In the field connected to "API Type" (1) select the option "Harvest". In the field connected to "Partner (if applicable)" (2) select Alva Labs then click "Manage Permissions" (3).

Step 4: A new dialogue box will appear. Copy the API Key (1). Then click "Close" (2). Write Alva in the description field.

Step 5: Tick the box located just to the left of applications as shown in the screenshot below. Then scroll down and click "SAVE".

3. Getting an API Key from Alva Labs

Step 1: In Alva, go to your company Settings (1). If you can't access them, either ask an employee in your organization with the access level "admin" or reach out on Alva's Intercom. Next click on "Integrations" (2). Then click "Add integration" (3).

Step 2: Click on "Add" next to Greenhouse.

Step 3: Paste the Harvest API Key that you copied from step 4 in the previous section of the guide. Then click "Enable" (2).

Step 4: An Alva API Key will appear. Click on the eye-icon (1) in order to reveal the API Key (2) which you then copy.

Note: API Keys allow access to sensitive data and must be kept secret. If an API Key is shared in an email and your email is intercepted by a malicious third party or your email account is hacked, the hacker would be able to view and access your API Key.

4. Sending the Alva API Key to Greenhouse support

Step 1: Click HERE in order to open a ticket in greenhouse.

Step 2: Write that you would like to get a "SENDSAFELY" link to send your Alva API Key and the Greenhouse support team will then respond with a link.

Step 3: Safely send your Alva API Key to Greenhouse support.

Thank you for reading this guide! You are now done with setting up the integration between Alva and Greenhouse. You can now send and review Alva tests directly through Greenhouse. If you want to know how to do that click HERE.

Please contact or your Customer Success Manager for troubleshooting assistance regarding the integration.

Did this answer your question?