What Kini handles when it imports jobs from Jobcluster.
Jobcluster hands out a customer's published jobs through a job export that it sets up for that customer. These are the steps Kini takes to turn that export into complete, current jobs in Kini.
Jobs from the One-Click-Recruiter, read for each end customer
Recruiters publish jobs in Jobcluster's One-Click-Recruiter, and Jobcluster hands them out through a job export. Kini reads that export separately for every end customer you bring, on a schedule set per customer and once more when the customer is activated in Kini. The imported jobs then behave like jobs from any other source in Kini's API.
The ad text kept in its sections
Kini reads the parts of a Jobcluster ad one by one: company introduction, tasks, candidate profile, benefits and contact. Each part becomes its own description section with its heading, and Kini also assembles one combined description. Where a part is empty in the general text but filled in the ad's StepStone version, Kini uses the StepStone text instead.
A postcode on the job, even when the field is empty
Each Jobcluster job comes in with its address: location name, street, postcode, city, country and coordinates. Kini turns the country into a two-letter ISO code. When the postcode field is empty, Kini takes the four- or five-digit postcode at the start of the job's place-of-work entry, so the job still carries a postcode.
Working time and home office in Kini's standard values
Jobcluster's export gives the working time as codes. Kini translates them into full-time, part-time and mini-job, and a job that offers more than one keeps all of them. The home office flag becomes remote or on-site. Kini then maps these values and the employment type onto its own standard values, so they line up with jobs from your other sources.
Unpublished in Jobcluster, archived in Kini
Jobcluster recruiters publish and unpublish jobs with one click. A job that is missing from the next export is archived in Kini, and any active booking of that job inside a campaign is unpublished. If the same job appears in the export again, Kini reactivates the archived record instead of creating a second one and republishes those campaign bookings.
Every field. Every entity.Exactly where it belongs.
The Jobcluster integration is inbound only. Kini reads each end customer's job export from the One-Click-Recruiter and imports the jobs it contains, and nothing is written back to Jobcluster. Jobcluster publishes no specification of this export, so the fields below are described in plain terms rather than by their element names.
Jobs
Ad sections
Location
Employer details
Jobcluster builds each customer's export to that customer's requirements and can include every field of its job ad form or only some of them. Kini imports what the export contains, so a section or field that a customer's export leaves out stays empty in Kini.
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.
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 Jobcluster integration.
What Kini reads from Jobcluster, how often it checks for changes, what happens to unpublished jobs and where applications go.
The published jobs of each end customer, read from Jobcluster's job export. Each job arrives with its title, the ad text split into sections, the address, working time, home office flag, start date and employment type, the application link and contact email, and employer details such as name, logo, header image and keywords.
Jobcluster Deutschland describes itself as recruiting software: the One-Click-Recruiter for multiposting, a Bewerbermanagementsystem for applicants, and career portals. It also runs its own regional job boards. Kini's integration connects to the software side. It reads the jobs a customer publishes in the One-Click-Recruiter, much as Kini reads jobs from an ATS.
No. The Jobcluster integration covers jobs only, and Kini does not create candidates or applications in Jobcluster. Each imported job keeps the application link from Jobcluster's export and, where the contact section names one, an application email address. Where candidates end up after following that link is decided on the Jobcluster side.
No. The integration runs one way, from Jobcluster into Kini, and Kini sends nothing back to Jobcluster. Jobcluster's own regional job boards, and the channels it offers through the One-Click-Recruiter, are booked in Jobcluster itself. This integration does not book or publish anything there.
On a schedule set for each end customer, and once when the customer is activated in Kini. A sync can also be started on demand through Kini's job sync trigger, which accepts one request per minute for each company. Every run reads the whole export, so new, changed and removed jobs are picked up in the same pass.
It drops out of the export, and the next import notices the gap. Kini archives the job and unpublishes any of its active bookings that belong to a campaign. Should the job return to the export later, Kini reactivates the existing record rather than importing a duplicate, and its campaign bookings are republished.
Access to that customer's job export from Jobcluster. Jobcluster sets up job feeds and interfaces to each customer's requirements, so the customer may first need to ask Jobcluster's service team to provide the export. Kini then configures the import for that customer and reads the export from the address Jobcluster provides.
No. Recruiters keep writing, publishing and unpublishing their ads in Jobcluster's One-Click-Recruiter, and Jobcluster stays the system of record for those jobs. Kini reads what is published, keeps it current in Kini and archives jobs once they leave the export. Kini changes nothing in the customer's Jobcluster account.
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."
