Five things Kini takes care of on the way into HRlab.
HRlab takes each application against an existing job ad and in its own field format. Kini prepares every application for that format and runs the delivery for each end customer you bring. Each benefit below names one concrete part of that work.
Applications on the right HRlab job ad, in HRlab's own fields
Kini submits each application into the end customer's HRlab account and links it to the HRlab job ad by that ad's ID. Name, email, phone, street, postcode, city, country, date of birth and nationality fill HRlab's own fields, and gender is translated into HRlab's M, W and D values. Notes from the application arrive in HRlab's comments.
All PDF documents in one file, CV first
Kini hands HRlab the candidate's documents as a single PDF: the CV first, then the cover letter, then any further PDF attachments. If the merged file would pass the size limit, 10 MB by default, Kini drops documents from the end of that order until it fits. Files in other formats, such as Word documents or images, are not transferred.
The source channel recorded in HRlab
For every end customer, Kini keeps a mapping from Kini's channels, a job board or a lead form for example, to that customer's channels in HRlab. Each application is submitted with the mapped HRlab channel, so the source is recorded with the application in HRlab. Channels without an entry of their own can fall back to a default channel.
Duplicates and missing job ads handled as expected cases
When HRlab reports an application as a duplicate, or cannot find the job ad it was sent for, Kini records an expected failure instead of an error, and no retry follows. If the end customer has a fallback job set up, Kini submits the application to that job instead and marks the delivery as a fallback.
Retries and a delivery status for every application
If HRlab is briefly unreachable, or answers with a rate limit or a gateway error, Kini queues the application and tries again later. An application HRlab rejects as invalid is marked as failed instead of being resent unchanged. Every application carries its delivery status, which your system can receive by webhook or read through Kini's API.
Every field. Every entity.Exactly where it belongs.
Kini writes applications into HRlab through HRlab's API. Each one carries the candidate's details, the documents as a single PDF and the channel it came from. The field names below are the ones Kini uses in HRlab's application interface.
Applications
Documents and notes
Source channels
Every application has to name an existing HRlab job ad. Kini takes that ID from the external ID of the job in Kini, so jobs for HRlab end customers need the HRlab job ad ID as their external ID.
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 HRlab integration.
How applications reach HRlab, which documents and fields they carry, and what happens when HRlab turns one down.
Kini sends applications into HRlab. Each one carries the candidate's name, email, phone, address, date of birth, nationality and gender, any notes, the documents as one PDF and the source channel, and it names the HRlab job ad it belongs to. Kini does not change or delete records that already exist in HRlab; it adds new applications.
By the ID of the HRlab job ad. Kini reads it from the external ID of the job in Kini and sends it with every application. If HRlab cannot find that job ad, the application is marked as an expected failure, or goes to the end customer's fallback job if one is set up.
PDF documents, merged into one file. Kini puts the CV first, then the cover letter, then other PDF attachments, and keeps the file within 10 MB by default by leaving out documents from the end. If even the CV alone is larger, the application goes to HRlab without a document. Files in other formats are not sent.
Kini marks the application as an expected failure with a duplicate error and does not retry it. Your system sees that status by webhook or through Kini's API, and no action is needed on your side. Whatever HRlab already holds stays as it is, because Kini only adds applications and never edits existing ones.
As an HRlab channel. Kini keeps a channel mapping per end customer that turns each Kini channel, such as a job board, into the ID of a channel in the customer's HRlab account. Channels without their own entry can use a default. Without a matching entry, the application is submitted without a channel.
An API key from their own HRlab account. HRlab lets customers create API keys in its settings, and Kini stores the key for that end customer only. Beyond that, the job ads that applications are meant for must exist in HRlab, and the matching jobs in Kini must carry their HRlab IDs.
From its delivery status. Every application shows whether it reached HRlab, reached the fallback job, failed, failed for an expected reason such as a duplicate, or has not been sent yet. Your system can receive each change by webhook or read the status through Kini's API. Temporary errors on HRlab's side are retried automatically.
No. HRlab stays the system of record for applications and for the rest of the HR work it covers, from personnel files to time tracking and payroll preparation. Kini sits between your channels and HRlab: it prepares each application for HRlab's format, delivers it and keeps track of the result as a managed service.
Kini anonymises the personal data of an application 180 days after it was created; the application in HRlab is not affected. Data held by Kini sits in Frankfurt, and a data processing agreement can be signed with Kini. Delivery statuses and channel attribution remain available for reporting after anonymisation.
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."
