Triplebyte was founded on the belief that the current technical hiring process doesn’t do enough to help engineers show their strengths. Triplebyte's founders started Triplebyte to help engineers find great jobs by assessing their abilities without relying on the prestige of their resume credentials.

Greenhouse Recruiting's integration with Triplebyte allows users to source, access, engage, and track candidates from Triplebyte. 

Note: This integration is currently only available for select accounts on Triplebyte. If you do not have access to the integration and feel that is a mistake, please contact you Triplebyte account manager, or email

In this article, we will cover: 


Enable the Greenhouse Recruiting / Triplebyte Integration 

The first step is to link Greenhouse and Triplebyte. To do this, visit your Triplebyte Hire dashboard:

Expand the Integrations menu on the left-hand side and click ATS


Click Connect Greenhouse.

You will be redirected to the Greenhouse Recruiting website. Follow the prompts to approve the integration. 


You will then be redirected back to Triplebyte. If everything went well, you should see a green box that says Greenhouse Linked, as shown in the image below.

You will then have the option to configure when you want candidates to appear in Greenhouse Recruiting.


All the candidate information provided on Triplebyte will be made available directly in Greenhouse Recruiting: Name, email, phone, resume, etc.

Create Harvest API Key for the Greenhouse Recruiting / Triplebyte Integration

To set up Greenhouse Recruiting integrations with Triplebyte, Triplebyte will most likely need access to a Harvest API Key.

To create a Harvest API key for the integration, click the Configure icon Configure.png 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 Triplebyte.


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

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

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



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 Triplebyte 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 Harvest 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 permissions listed below at the following link are selected:

Object Permission
Activity Feed
> GET: Retrieve Activity Feed
Used to sync notes and communications with candidates
> GET: List Applications
Used to find the matching Greenhouse record for a candidate’s application
> GET: Retrieve Application
Used to sync application status Greenhouse updates back to Triplebyte
> PATCH: Update Application
Used to show Triplebyte test scores and custom answers in Greenhouse
> POST: Add Attachment to Application
Used to show details of Triplebyte test scores in Greenhouse
> POST: Add Application to Candidate/Prospect
Used to push Triplebyte candidates to Greenhouse and attach to a given role
> POST: Add Candidate
For pushing candidates that are attached to a role on the Triplebyte side which has an analogous ATS role
> POST: Add Prospect
For pushing candidates that have no role on Triplebyte or have a role that is not on the ATS side
> GET: List Candidates
Used to find the matching Greenhouse record for a Screen candidate
> GET: Retrieve Candidate
Used to sync application status in Greenhouse with Triplebyte
> PATCH: Edit Candidate
Used to update candidate details and test scores to Greenhouse
> POST: Add Note
Used to sync notes on candidates
> POST: Add E-mail Note
Used to sync candidate communications
Jobs > GET: List Jobs
Used to sync job reqs with Triplebyte, and to attach jobs with tests in Triplebyte Screen
> GET: Retrieve Job
Used to post jobs easily on Triplebyte and to keep job posting updated
Job Posts
> GET: List Job Posts
Used to enable easy job postings on Triplebyte
> GET: Retrieve Job Post
Used to sync details of job postings
Job Stages
> GET: List Job Stages
Used to sync application stages, configure workflows based on candidate stage, and display hiring funnel insights
> GET: List Offers
Used to display hiring funnel insights and to improve tests based on candidate success rates
> GET: List EEOC
Used to improve candidate experience by avoiding duplication of EEOC questionnaire
> GET: List Departments
Used to identify departments linked to jobs
> GET: List Users
Used to set up the link with Harvest and send updates to Greenhouse with the correct context
Scheduled Interviews
> POST: Create Scheduled Interview
> GET: Retrieve Scheduled Interview
> PATCH: Update Scheduled Interview
> DELETE: Delete Scheduled Interview


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

Your Harvest API key for the Greenhouse Recruiting / Triplebyte integration is created and configured. Copy the Harvest API key to provide to Triplebyte in the next step. 

Use the Greenhouse Recruiting / Triplebyte Integration

Once you have the integration set up, you will be able to send candidates to Greenhouse Recruiting at various times during the candidate connection process, depending on whether or not the candidate is currently a part of the FastTrack program or not. 

FastTrack candidates: 

  • When you make a call request: The candidate will be pushed to Greenhouse after you request an intro call with the candidate
  • When the candidate accepts your call request: The candidate will be pushed to Greenhouse only once the candidate accepts your intro call request
  • When you manually push from the candidate profile: The candidate will be pushed to Greenhouse only once you push the from the candidate profile (see screenshot below)

Non-FastTrack candidates (previously referred to as Source candidates):

  • When the candidate accepts your call request: The candidate will be pushed to Greenhouse only once the candidate accepts your request to be introduced
  • When you manually push from the candidate profile: The candidate will be pushed to Greenhouse only once you push the from the candidate profile (see screenshot below)


Once the Greenhouse integration is set up, you can manually push candidates through by selecting Push to Greenhouse from the candidate control card, once the profile is opened up.