RepVue is a career influencer platform where sales pros discover, research, and apply for roles at the world's most well known sales orgs.  Sales pros gain access to RepVue by submitting an objective rating of an org where they’ve worked.  RepVue is leveraging this dataset to drive attraction and retention of talent for b2b sales orgs via talent competitor and comp benchmarking as well as premium site promotional opportunities and is a source of candidates for the world’s most well known sales brands.

This document will serve as a reference guide and overview for RepVue customers who are utilizing the RepVue - Greenhouse integration.  This integration is designed to allow a seamless recruiting experience for employers who leverage Greenhouse as their ATS.  Recruiters will be able to leverage their existing workflows to engage candidates when this integration is utilized.

Greenhouse Recruiting’s integration with RepVue allows employers to seamlessly push jobs into the RepVue system, update the status of those jobs and access RepVue candidates via Greenhouse.  In this article, we will cover how to:

  • Configure User Setup Permissions in Greenhouse Recruiting
  • Create a Harvest API Key for the Greenhouse/ RepVue Integration
  • Additional information about the Greenhouse/ RepVue Integration

Configure User Setup Permissions in Greenhouse Recruiting

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

Contact a Greenhouse user in your organization with Site Admin level permissions with the additional user-specific permission Can edit another user's advanced permissions to apply the API credential management permission to your account. Have the user with Site Admin level permissions edit your user account's permissions by navigating to the Configure icon   > Users > Your Name).

The user with Site Admin level permissions should navigate to the Permissions panel on your user page and expand the Developer Permissions dropdown menu. 

Select Can manage ALL organization’s API Credentials so that a check is in the checkbox. When finished, click Save.

Repeat as necessary for any other user that should have access to set up the integration.

Create a Harvest API Key for the Greenhouse/RepVue Integration

To create a Harvest API key for the integration, click on the Configure icon  in the upper right-hand corner. Navigate to Dev Center on the left-hand panel.

From the Dev Center page, click API Credential Management.

From the API Credential Management page, click Create New API Key to generate the API key for RepVue.

In the Create New Credential dialog box, make the following selections:

  • API Type: Harvest
  • Partner: RepVue
  • Description: RepVue Harvest API Key

When finished, click Manage Permissions to generate the Harvest API key and automatically assign it the appropriate permissions required by RepVue.

In the subsequent dialog box, click Copy to save your API key to your clipboard. Store the API key in a secure location to provide to RepVue in the next step. Click I have stored the API Key once you have copied and saved the key.

Note: You cannot access the full API key again after clicking I have stored the API Key. If you lose your API key and need to access it later, you must create a new API key, provide it to the integration partner, and then revoke access to the original key.

On the subsequent page, confirm the following permissions are assigned to your new API key:

On the Manage API Key Permissions page, please select all boxes available.  When finished, click Update.


If any of the permissions above are not checked, place a check in the box next to the appropriate permission. Click Save when finished.

Your Harvest API key for the Greenhouse/ RepVue integration is created and configured. Provide your Harvest API key to you RepVue onboarding team so they can set up the integration.

Additional information about the RepVue Integration with Greenhouse

There are four integration points for the Greenhouse / RepVue integration: accessing jobs, creating candidates, updating candidates and updating jobs.

Accessing Jobs

RepVue pulls ‘job posts’ from Greenhouse inot RepVue (

RepVue is leveraging the ‘get job posts’ Harvest API call:

We pull the following fields

  • ID (the job post ID)
  • Title (the job post title)
  • Content (the content of the job post, aka description)
  • Location name (the location of the greenhouse job)
  • Job ID (the ID of the job)

We only pull in job posts one time, and each job post will create a ‘job’ in the RepVue system with a default status of new.  We look for new job posts once per hour via this API call.

Creating Candidates

RepVue will create candidates in the Greenhouse system when a user clicks ‘Apply via RepVue’ for a job that has been posted for a Greenhouse  <> RepVue shared customer (

RepVue is leveraging the ‘post candidates’ call from the harvest API:

RepVue provides the following fields to Greenhouse:

  • First Name
  • Last Name
  • e-mail address (‘other’ is used for email type)
  • Linkedin URL
  • Job ID

Additionally, the ‘applications’ field is required as part of the ‘post candidates’ call to Greenhouse, and we should be sending the following inside the ‘Add application to candidate’ post when we post a new candidate:

  • job_id
  • source_id

When RepVue creates candidates in Greenhouse, we receive a response with the following information:

  • Candidate ID
  • Application ID

The timing of when a user ‘Applies via RepVue’ and a candidate is created in the Greenhouse system is typically under 15 minutes.

Updating Candidate Status

When a candidate is successfully created in the Greenhouse system, it will default to ‘engagement’ status in the RepVue system.  RepVue is checking candidate status regularly to track rejections and hires via the integration (

RepVue is accessing the candidate status via the candidates call in the Harvest API:{id}

RepVue provides the Greenhouse candidate ID along with the Greenhouse application ID(s), and receives the following information:

  • Status (application status)
  • Stage name (‘current_stage’ in greenhouse)

For the ‘Status’ field there are three potential responses from Greenhouse:

  • Rejected: and for any application with a greenhouse status of rejected, RepVue sets the RepVue connection status to declined
  • Active:  for any application with a greenhouse status of active, RepVue sets the RepVue connection status to engaged (note that ‘new’ connections created via RepVue will default to ‘active’ when created so the expected behavior is that the application status of active will trigger an update in the RepVue system for the connection status to change from ‘new’ to ‘engagement’ in the RepVue system until it is subsequently set to rejected or hired).
  • Hired: for any application with a greenhouse status of ‘hire successful’ the RepVue connection status will be updated to ‘hire successful’

This update will occur hourly

Updating Job Post Status

Job posts that are pulled down will also need to be removed from RepVue.  RepVue is checking job post status regularly via the integration (

RepVue checks all jobs in the RepVue system with a status of ‘active’ or ‘new’ in the Greenhouse system via the API for the job post status, leveraging the job posts call in the Harvest API:{id}

If the LIVE status is FALSE for a job post, the RepVue job status will be set to ‘archived’ (which automatically pulls the job off of the RepVue job board.

If the LIVE status is TRUE for a job post, no action is taken.

We check job post status hourly.

Need help?

Please contact your designated RepVue account representative (or for troubleshooting assistance regarding the integration.