How teams actually use Kini with JOIN.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with JOIN. Five scenarios where the managed integration makes the biggest difference.
Your customer connects JOIN themselves
You generate a Magic Link and send it to your end customer. They enter their JOIN API token themselves, generated in their own JOIN account settings. You never touch access data, your team never touches applicant data.
Fields map themselves
JOIN'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 JOIN account. Your team never has to download, forward or re-enter applicant data. The record ID from your customer's JOIN account is written back, so applications match reliably.
One JOIN account, 1,500+ job boards
Once connected, you choose from 1,500+ job boards, including Stepstone and Indeed, to promote JOIN 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, applications and candidate updates between JOIN and your connected channels via JOIN's v2 API, with categories, employment types and seniority levels available as reference data for mapping. No intermediate storage, no manual exports, no data sitting in between.
Jobs
Applications
Candidates
JOIN writes the ATS-side record ID back onto each application through its externalData endpoint, which keeps records matched reliably across systems.
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 JOIN API token to production go-live.
Kini connects to JOIN via Magic Link and an 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 enters their JOIN API token themselves, generated in their own JOIN account settings. You never see or store it.
Step 2Map
Kini auto-detects and pre-maps JOIN's fields, categories, employment types, seniority levels and screening questions. 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 JOIN account, with the ATS-side ID written back via JOIN's externalData endpoint for reliable matching. JOIN stays the system of record.
with your stack?
What makes Kini different for JOIN 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 JOIN integration.
Everything about how Kini connects to JOIN. From setup and authentication to data sync and GDPR compliance.
Jobs, applications, candidates, offices and reference data such as categories, employment types and seniority levels, via JOIN's v2 API. Jobs carry status, office, workplace type, salary and screening questions, and applications sync in both directions.
JOIN uses an API token per account, generated by your customer in their own JOIN settings and entered via the Magic Link. You never see or store the credential, and Kini operates the connection from there.
No. JOIN stays your system of record. Kini is the connectivity layer around it: jobs and applications are synced between JOIN and your connected recruiting channels, so you extend what JOIN already does without replacing it.
No. The JOIN integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they enter their own JOIN API token, and Kini handles mapping, operation and monitoring as a managed service.
It is built for GDPR-compliant use. Data that passes between JOIN 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."
