What Kini handles between Heyrecruit and your channels.
Heyrecruit organises jobs by company location and expects every application for a specific job and location. Kini handles both directions for each end customer you bring. Five places where that makes the clearest difference.
Active Heyrecruit jobs, read on a schedule
Kini reads the jobs an end customer's Heyrecruit account lists as active, page by page, on a schedule set for that end customer. Each job arrives with its title, description, employment type, department and full address including coordinates, taken from the job text in its default language. A partner can also start a job sync on demand.
One job per location, one application per location
In Heyrecruit, a single job can be published at several company locations. Kini creates a separate job for every location where the posting is active and keeps track of which location it belongs to. When a candidate applies, Kini submits the application for exactly that job and location, so it lands where the recruiting team expects it.
Documents filed under Heyrecruit's own categories
Heyrecruit sorts application documents into categories. Kini sends every attachment with the category Heyrecruit expects, so CVs, cover letters and photos land in their matching slots and anything else is filed as other. File name and file type travel with each document, and recruiters open a complete application instead of an unsorted pile of files.
The source channel handed over with every application
Kini passes the channel an application came from to Heyrecruit's referrer field, which Heyrecruit's API documents as the traffic source identifier. Channel names can be mapped per end customer, so the value arriving in Heyrecruit matches the source names their team already uses. That keeps it traceable which channel produced which application.
Duplicates recognised, every delivery tracked
Heyrecruit rejects a second application from the same email address for the same job. Kini records that as an expected outcome rather than an error and marks the application accordingly. Every application carries a visible sync status, and temporary problems on the Heyrecruit side, such as rate limits or unreachable servers, are retried automatically.
Every field. Every entity.Exactly where it belongs.
Three kinds of data move between Heyrecruit and Kini. Jobs come in from Heyrecruit's job list, and applications go out through Heyrecruit's apply interface together with their documents. The key fields use the spelling of Heyrecruit's REST API documentation.
Jobs
Applications
Application Documents
Heyrecruit publishes one job at several company locations. Kini imports a separate job for every location where the posting is active and sends each application back to the location it was submitted for, so the same Heyrecruit job can appear in Kini more than once.
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 Heyrecruit integration.
How Kini reads jobs from Heyrecruit, how applications and their documents reach it, and what an end customer's Heyrecruit account needs for the connection.
Two flows. Kini reads active jobs from Heyrecruit, with title, description, employment type, department and location, and makes them available to your connected channels. In the other direction, Kini submits applications to Heyrecruit with the candidate's name, email address, phone number, documents and the source channel, each one for the right job and location.
No. Heyrecruit stays the end customer's system of record for jobs and applicants. Kini sits between Heyrecruit and the channels where candidates apply: it takes the jobs from Heyrecruit, delivers the applications back into it, and operates that connection as a managed service, so there is no second applicant system to maintain.
Kini reads the Heyrecruit job list on a schedule configured for each end customer, and a partner can trigger an extra job sync for an end customer on demand. Applications travel the other way as they arrive: each one is submitted to Heyrecruit on its own, without waiting for the next scheduled run.
Kini turns it into one job per location where the posting is active, each with that location's address. Candidates therefore apply to a specific location, and Kini submits their application to Heyrecruit for the same job and location. Locations where the posting is switched off in Heyrecruit are left out of the import.
Every attachment the candidate submitted through the channel. Kini sends each file with its name and file type and assigns one of Heyrecruit's document categories: CV, cover letter, photo, or other for everything else, certificates included. The candidate's contact details and the source channel travel in the same application.
Heyrecruit accepts one application per email address and job and turns down a repeat. Kini recognises that answer and gives the application the status expected failure, with the reason recorded as a duplicate, instead of treating it as an error. The candidate is already in Heyrecruit for that job, so nobody on your side has to act.
Yes. Kini submits the channel name with every application in Heyrecruit's referrer field, the field Heyrecruit's API provides for the traffic source. If an end customer's team uses its own names for sources, Kini can map each channel to that name before the application is sent.
Every application in Kini carries a sync status: success, failure, expected failure or not yet sent. You can receive status changes through Kini's sync status webhook or read them through the API. If Heyrecruit is briefly unreachable or limits requests, Kini retries the delivery automatically instead of dropping the application.
Access to the Heyrecruit API. For the flows on this page, Kini reads the job list and submits applications, and Heyrecruit's documentation lists both among the rights an API app has by default. Reading applicant details is a separate right that Heyrecruit does not switch on by default. Part of the API access data is issued only by Heyrecruit's support.
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."
