How teams actually use Kini with HR WORKS.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with HR WORKS. Four scenarios where the managed integration makes the biggest difference.
Your customer connects HR WORKS themselves
You generate a Magic Link and send it to your end customer. They create an HR WORKS API access key themselves. You never touch access data, your team never touches applicant data.
Fields map themselves
HR WORKS'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 HR WORKS account. Your team never has to download, forward or re-enter applicant data. HR WORKS confirms each write through its own asynchronous job flow.
Every field. Every entity.Exactly where it belongs.
Kini syncs job postings, applicants and job applications between HR WORKS and your connected channels via the HR WORKS Public API v2, the three resources of its Applicant Management module. No intermediate storage, no manual exports, no data sitting in between.
Job Postings
Applicants
Job Applications
HR WORKS processes writes asynchronously through its own job-polling pattern, and the Applicants resource returns only applicants with at least one job application.
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 HR WORKS access key to production go-live.
Kini connects to HR WORKS via Magic Link and an access 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 creates an HR WORKS API access key themselves. Kini authenticates with that key and keeps the connection verified. You never see or store it.
Step 2Map
Kini auto-detects and pre-maps HR WORKS's job posting, applicant and job application fields, so the setup reflects the customer's own instance. 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 HR WORKS account, which stays the system of record. Kini operates and monitors the connection.
with your stack?
What makes Kini different for HR WORKS 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 HR WORKS integration.
Everything about how Kini connects to HR WORKS. From setup and authentication to data sync and GDPR compliance.
Job postings, applicants and job applications, the three resources exposed by HR WORKS's own Applicant Management module. Postings carry display name, organizational unit, contact information and active status, and job applications from your connected channels are written into HR WORKS.
Your customer creates an access key inside HR WORKS and enters it via the Magic Link. You never see or store it, and Kini authenticates with the key and keeps the connection verified from there.
No. HR WORKS stays your system of record for applicant management. Kini is the connectivity layer around it: job postings, applicants and job applications are synced between HR WORKS and your connected recruiting channels, so you extend what HR WORKS already does without replacing it.
No. The HR WORKS integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they create their own access key, and Kini handles authentication, field mapping and operation as a managed service.
It is built for GDPR-compliant use. Data that passes between HR WORKS 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."
