Greenhouse integration · Web hooks + Harvest API v3
Screen Greenhouse applications with HireLayer
Greenhouse already parses resumes when candidates apply. HireLayer adds what it does not do: a score for every application against the job’s criteria, with an explanation per criterion, written back to the candidate as a note your recruiters see in Greenhouse.
- Trigger
- Web hook: Application created
- Greenhouse API
- Harvest v3, OAuth client credentials
- Write-back
- Note, tags, custom fields, employments
- Cost
- 2 credits per application
- 1A candidate appliesGreenhouseGreenhouse sends the new_candidate_application web hook, with the application, the job and a link to the resume.
- 2Parse the resumeHireLayerYour handler downloads the resume and sends it, with the job ID, to HireLayer Resume Scorer, which parses it first.
- 3Score against the jobHireLayerResume Scorer compares the resume with the job’s criteria and returns a score and an explanation per criterion.
- 4Write back to GreenhouseGreenhouseA note on the candidate with the score and the gaps, plus a tag such as “Strong match” for filtering.
What teams do with HireLayer and Greenhouse
Triage high-volume roles
Every application gets a score and the list of mandatory criteria it meets. Recruiters start with the strongest matches instead of reading in arival order.
Explain the shortlist
The note lists each criterion with its status and the evidence found in the resume, so hiring managers see why a candidate is ahaed.
Complete sourced profiles
For prospects added from a CV, write the parsed work history and education back with the candidate employments and educations endpoints.
Normalized skills
Map free-text skills to the HireLayer taxonomy and store them as tags or a custom field, to search candidates by skill across jobs.
Connect Greenhouse to HireLayer
This is a small service you run, for example a serverless function or an n8n workflow. A Greenhouse user with developer permissions sets it up; no partner program is needed.
- 1
Create Harvest v3 credentials
In Greenhouse, open Configure → Dev Center → API Credentials and create Harvest V3 (OAuth) credentials with the scopes your service needs (attachments, notes, tags, jobs). Your service gets a token from https://auth.greenhouse.io/token with the client credentials grant.
- 2
Add a web hook
In Dev Center → Web Hooks, create a hook for Application created pointing to your service, with a secret key. Greenhouse signs each request with HMAC SHA-256 in the Signature header.
- 3
Extract criteria once per job
When a job opens, send its description to HireLayer Job Criteria Extractor with the Greenhouse job ID as job_id. HireLayer stores the job and its criteria, for free, and every applicant to that job is then scored on the same list.
- 4
Parse, score and write back
For each web hook: verify the signature, download the resume attachment (its link expires after seven days), send it to Resume Scorer with the job ID, which parses and scores it in one call, then post a note with POST /v3/notes and apply a tag.
Where HireLayer results go in Greenhouse
Greenhouse candidates have no native skills field, and arrays sent with PATCH /v3/candidates/{id} replace the whole list: read the current values before adding to them. Resume Scorer keeps the parsed resume: read its fields for free with GET /api/v4/resumes/{application_id}.
| HireLayer field | Greenhouse Harvest v3 | Note |
|---|---|---|
| score + summary + criteria[] | POST /v3/notes (body, visibility) | What recruiters read |
| score ≥ your threshold | POST /v3/applied_candidate_tags | Create the tag once with /v3/candidate_tags |
| resume.info_candidate.job_title | title (PATCH /v3/candidates/{id}) | |
| resume.work_experiences[] | POST /v3/candidate_employments | |
| resume.educations[] | POST /v3/candidate_educations | |
| resume.skills[].skill_title | custom_fields or tags | No native skills field |
A web hook handler in TypeScript
A minimal Node.js handler: it checks the Greenhouse signature, sends the resume to Resume Scorer against the job stored with its criteria, and posts a private note. Add a queue and your retry logic.
import { createHmac, timingSafeEqual } from 'node:crypto'
const HIRELAYER = 'https://hirelayer.co'
const headers = { 'X-API-Key': process.env.HIRELAYER_API_KEY! }
export async function handle(rawBody: string, signature: string) {
// Greenhouse: "sha256 <hex>" over the raw body
const expected = 'sha256 ' + createHmac('sha256', process.env.GH_WEBHOOK_SECRET!)
.update(rawBody).digest('hex')
const valid = signature.length === expected.length &&
timingSafeEqual(Buffer.from(signature), Buffer.from(expected))
if (!valid) return 401
const { payload } = JSON.parse(rawBody)
const application = payload.application
const resume = application.candidate.attachments
.find((a: { type: string }) => a.type === 'resume')
if (!resume) return 200
// 1. Parse and score the resume in one call (about a minute), against the
// job stored once with POST /api/v4/jobs/extract-criteria and its job_id
const form = new FormData()
form.append('request', JSON.stringify({
job: { job_id: String(application.jobs[0].id) },
resumes: [{ file: 'resume', application_id: String(application.id) }],
}))
form.append('resume', await fetch(resume.url).then((r) => r.blob()), resume.filename)
const response = await fetch(`${HIRELAYER}/api/v4/resumes/score`, {
method: 'POST', headers, body: form, signal: AbortSignal.timeout(150_000),
})
// Errors come as { error: { code, message } } (no credits, unknown job): skip.
if (!response.ok) return 200
const { scores: [result] } = await response.json()
// An unreadable file fails only its own score, unbilled.
if (result.evaluation_status !== 'completed') return 200
// 2. Write back to Greenhouse (Harvest v3)
await fetch('https://harvest.greenhouse.io/v3/notes', {
method: 'POST',
headers: {
Authorization: `Bearer ${await greenhouseToken()}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
candidate_id: application.candidate.id,
body: `HireLayer score: ${result.score} (${result.verdict})\n${result.summary}`,
visibility: 'private',
note_type: 'NOTE',
}),
})
return 200
}Good to know
Harvest v3 only
Greenhouse removed Harvest v1 and v2 on August 31, 2026. Use v3 and OAuth client credentials; the old API tokens no longer work.
Answer the web hook fast
Parsing and scoring take about a minute. Acknowledge the web hook first and do the work in a queue or a background job, so Greenhouse does not retry a request that already succeded.
Greenhouse already parses resumes
Greenhouse fills basic fields when a resume is uploaded (files up to 2.5 MB). Use HireLayer for scoring, normalized skills and structured history, not to replace the built-in parse.
Not a marketplace app
HireLayer is not listed in the Greenhouse partner directory. You connect it through your own Harvest credentials, or ask us to build the connector with you.
HireLayer APIs used on this page
HireLayer and Greenhouse: questions
Does HireLayer integrate with Greenhouse?
Can I screen Greenhouse applicants with AI?
Can I connect Greenhouse without writing code?
Which Greenhouse permissions are needed?
How many credits does one application use?
Connect Greenhouse to HireLayer today
The Free plan includes 50 credits a month, no card required. Parsing a resume costs one credit, scoring one per resume evaluated, and extracting job criteria is free.
Other integrations
- LeverScore each new Lever application against its posting and write the result back as a note and tags, with Lever webhooks and the Data API.
- WorkdayScore Workday Recruiting applications against the requisition and add normalized skills, through the Recruiting web service and an integration system user.
- TeamtailorScore new Teamtailor applications against the job and save the result as a note, custom fields and tags, with an Admin API key and polling.
