How teams actually use Kini with Greenhouse.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with Greenhouse. Five scenarios where the managed integration makes the biggest difference.
Your customer connects Greenhouse themselves
You generate a Magic Link and send it to your end customer. They connect their Greenhouse account with a Harvest API key. You never touch access data, your team never touches applicant data.
Fields map themselves
Greenhouse's fields are auto-detected and mapped in the background. No code, no engineer, no development ticket.
You never touch applicant data
Applications land directly in your customer's Greenhouse account, with source and attachments in place. Your team never has to download, forward or re-enter applicant data.
One Greenhouse account, 1,500+ job boards
Once connected, you choose from 1,500+ job boards, including Stepstone and Indeed, to promote Greenhouse jobs, and applications come back the same way. One connected account, no second integration project.
Every field. Every entity.Exactly where it belongs.
Kini syncs jobs, candidates and applications between Greenhouse and your connected channels via the Harvest API. No intermediate storage, no manual exports, no data sitting in between.
Jobs
Candidates + Applications
Operations like GET, POST, PATCH are documented per endpoint in the . The primary source for field definitions. Kini adds mapping and fallback logic on top.
From Harvest API key to production go-live.
Kini connects to Greenhouse via Magic Link and Harvest API key. Fields are mapped automatically, the connection is tested and your integration is live.
Step 1Connect
Your customer receives a Magic Link from Kini and connects their Greenhouse account with a Harvest API key. You never see or store the key.
Step 2Map
Kini auto-detects and pre-maps Greenhouse's job and candidate fields, including departments, offices and custom fields, between Greenhouse and your connected channels. No manual configuration needed.
Step 3Test
A test job and a test candidate run automatically through the full flow. Kini checks field mapping and sync behaviour before anything goes live.
Step 4Go-live!
Applications flow through Kini directly into the customer's Greenhouse account, which stays the system of record. Kini operates and monitors the connection.
with your stack?
What makes Kini different for Greenhouse customers.
Other tools connect. Kini manages. In practice that covers GDPR, field mapping, job board compatibility and everything that breaks when nobody is watching.
End-to-end GDPR consent
Every application that flows through Kini carries a consent flag, mirrored on the target system's side and traceable in audits.
Native-language custom fields
Locations, departments and sources are mapped correctly even when they use German naming conventions or regional variants, whether your customers sit in DACH or operate internationally.
Application flows for a wide range of job boards
Stepstone, Indeed, Jobrapido and regional boards each have their own required fields, screening patterns and encoding rules. Kini's mapping engine is trained for those: out of the box, not as a custom project.
Operated by the Kini team
Kini runs the connection for you, including monitoring and alerts. If a vendor changes an API or a mapping breaks, our team fixes it before it reaches your funnel. Operated from Germany.
Frequently asked questions about the Greenhouse integration.
Everything about how Kini connects to Greenhouse. From setup and authentication to data sync and GDPR compliance.
Kini syncs three objects with Greenhouse through the Harvest API: jobs are read from Greenhouse, candidates are created and updated in it, and applications are synced alongside them. Departments, offices, statuses and custom fields are mapped as part of the sync, so records arrive complete.
No. Greenhouse stays your system of record. Kini is the connectivity layer around it: jobs, candidates and applications are synced between Greenhouse and your connected recruiting channels, so you extend what Greenhouse already does without replacing it.
No. The Greenhouse integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they connect their own Greenhouse account with a Harvest API key, and Kini handles mapping, operation and monitoring as a managed service.
Your customer connects their Greenhouse account with a Harvest API key, entered on their side via the Magic Link. You never see or store the key. Greenhouse's Harvest API uses the key for authentication, and Kini operates the connection from there.
It is built for GDPR-compliant use. Data that passes between Greenhouse and your connected channels is processed by Kini in Frankfurt, Germany, under a data processing agreement (DPA). Kini deletes or anonymizes personal applicant data 180 days after an application is created.
Trusted by recruiting teamsacross europe.
From enterprise HR platforms to lean recruiting boutiques. Teams use Kini to connect their tools without involving engineering. Here's what they say.
"Kini syncs candidates from Perspective straight into our customers' ATS. That saves us manual transfers and around four hours a week."
"Kini gets enterprise customers on SAP SuccessFactors live much faster. Fewer technical hurdles in sales, around 20% more conversion."
"With Kini, we sync candidates straight into our customers' ATS through 65+ integrations. We don't need an extra full-time hire for it."
