How teams actually use Kini with Recruitee.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with Recruitee. Five scenarios where the managed integration makes the biggest difference.
Your customer connects Recruitee themselves, in one click
You generate a Magic Link and send it to your end customer. They connect their Recruitee account with a personal API token. You never touch access data, your team never touches applicant data.
Fields map themselves, the rest with one click
Recruitee's offer and candidate fields are auto-detected and pre-mapped. You fix any mismatches from a dropdown. No code, no engineer, no development ticket.
You never touch applicant data
Applications run through Kini straight into your customer's Recruitee account, creating the candidate there directly. No intermediate storage, no liability on your side. Recruitee then runs its normal application flow, including the confirmation email.
One Recruitee account, 1,500+ job boards
Once connected, you choose from 1,500+ job boards, including Stepstone and Indeed, to promote Recruitee 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 and candidates between Recruitee and your connected channels. No intermediate storage, no manual exports, no data sitting in between.
Jobs (Offers)
Candidates
Recruitee calls jobs "offers": the /offers endpoint returns the company's jobs, and creating a candidate is equivalent to an application submit, which triggers Recruitee's standard confirmation email.
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 personal API token to production go-live.
Kini connects to Recruitee via Magic Link and a personal API token. 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 Recruitee account with a personal API token created in their own Recruitee settings. You never see or store it.
Step 2Map
Kini auto-detects and pre-maps Recruitee's offer and candidate fields between Recruitee 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 Recruitee account, which stays the system of record. Kini operates and monitors the connection.
with your stack?
What makes Kini different for Recruitee 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 Recruitee integration.
Everything about how Kini connects to Recruitee. From setup and authentication to data sync and GDPR compliance.
Kini syncs jobs and candidates with Recruitee. Jobs are read through the /offers endpoint, which is Recruitee's name for job records, and candidates are created and updated with name, phone, email and CV attached. Fields are mapped as part of the sync, so records arrive complete.
Your customer generates a personal API token in their own Recruitee settings and connects it via the Magic Link. You never see or store the token. Kini uses it to operate the connection and keeps it out of your systems entirely.
Kini creates the candidate in Recruitee, which is equivalent to a candidate applying and triggers Recruitee's standard application confirmation email. The record carries name, phone, email and CV, so the application arrives complete in your customer's account.
No. Recruitee stays your system of record. Kini is the connectivity layer around it: jobs and candidates are synced between Recruitee and your connected recruiting channels through one API, so you extend what Recruitee already does without replacing it.
It is built for GDPR-compliant use. Data that passes between Recruitee 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."
