Skip to main content

Greenhouse

Connect Greenhouse with Adway

Updated over 2 months ago

Only a token (api key) is required for integrating with Greenhouse API.

Adway's integration with Greenhouse Recruiting provides a streamlined and secure connection, enhancing the efficiency of your recruitment workflows.

How the Integration Works

Our integration leverages Greenhouse's Harvest and Job Board APIs, enabling seamless data exchange between Adway and Greenhouse. This integration includes:

  • Job Management: Automatically synchronize job postings from Greenhouse to Adway, enabling quicker and more accurate job advertising.

  • Candidate Management: Easily create and update candidate profiles and applications directly within Greenhouse from Adway, ensuring your database is consistently up-to-date.

  • Document Handling: Efficiently upload candidate documents, such as CVs, directly into Greenhouse, streamlining your recruitment process.

Technical Details

  • Secure Connectivity: Adway uses API token authentication (Harvest API key) to securely access Greenhouse's API.

  • Custom Integration: Our integration is fully custom-built, designed specifically to optimize the connection between Adway and Greenhouse.

  • Data Transfer: The data exchanged includes critical recruitment information such as candidate details, job specifics, and associated documents.

Data Exchange

We utilize specific endpoints provided by Greenhouse's APIs:

  • Job Synchronization (GET): Endpoints such as GET /v1/job_posts and GET /v1/jobs retrieve job postings, including job title, location, description, and hiring team data to ensure effective job advertising.

  • Candidate Synchronization (POST): Endpoints such as POST /v1/candidates are used to create candidate profiles and applications. We exchange data such as candidate name, contact information and upload files like CVs and attachments.


Connecting Adway and Greenhouse

Generating an API Key in Greenhouse

To use the API, you’ll need a Harvest API key. Here's how to generate one:

  1. Follow the instructions in the Greenhouse documentation to create a new Harvest API key.

  2. During the creation process, select "Adway" or "Unlisted Vendor" as the partner.

  3. You must have the appropriate permissions to create API keys.

    API Keys location

After creating the key, make sure to:

  • Verify that the following permissions are selected for the Adway integration:

    • Applications: GET: Retrieve Application, GET: List Applications

    • Candidates: GET: Retrieve Candidate, PATCH: Edit Candidate, POST: Add Candidate, POST: Add E-mail, POST: Add Note, POST: Add Attachment, POST: Add Application, POST: Add Education, POST: Add Employment

    • Job Openings: GET: List Openings For a Job

    • Job Posts: GET: List Job Posts, GET: Retrieve Job Post for Job, GET: List Job Posts for Job

    • Jobs: GET: Retrieve Job, GET: List Jobs, GET: Get hiring team

Getting your Job Board Identifier

To ensure jobs are synchronized correctly, you will also need your Job Board identifier.

  1. Navigate to Configure > Job Boards & Posts.

  2. Click the ellipsis icon next to the relevant job board.

  3. Select Edit Board Settings.

  4. Scroll to the URL field to find the Job Board identifier.

Job Board identifier location

Connecting the Greenhouse account to your Adway account

To connect your Greenhouse account to your Adway account, follow these steps:

  1. Navigate to the "Connectors" section in the Adway interface.

    Connectors Page

  2. Select "Greenhouse" as the system and choose the appropriate routine.

    Select ATS Step

  3. Enter your Harvest API key and Job Board identifier in the corresponding field.

  4. Enter user ID of a user with appropriate permissions to submit candidates.

    Authenticate ATS Step

  1. Save the changes.

  2. To verify the setup, check job fetching and mapping under the "Mapping" tab, or manually initiate a data fetch by clicking the "Run" button.

    Connector Workbench Configuration

This integration provides a smooth and secure user experience, making recruitment marketing and candidate management effortless and efficient.

API Key should have at least permissions to Applications, Candidates, Jobs, Job Posts, and Sources. Applications and candidates should have read/write permission, while the rest of the resources can be read-only.

Did this answer your question?