What Kini does with Kenjo's recruiting module.
Kenjo covers far more than recruiting, but only its recruiting module matters for this connection. Kini reads positions there and writes candidates and applications for every end customer you connect, as the five cards below describe.
Active positions, complete with their address
Kenjo gives every position one of four statuses: Active, Draft, Closed or Archived. Kini publishes active positions only, with job title, HTML description and position type, and adds street, postal code, city and country from the office the position belongs to, so each job arrives with its full address.
Candidate and application, each in its place
Kenjo stores the person and the application as separate records. For each applicant, Kini creates a candidate with first name, last name, email and phone, then an application linking that candidate to the position they chose. The recruiter sees the person in the position's pipeline straight away.
The channel kept on both records
Kenjo has a source field on the candidate and a separate source on each application. Kini fills both with the channel the person applied through, so the end customer can tell where candidates come from whether they look at people or at individual applications in Kenjo.
CVs stored with the candidate
The CV and every other document from the application are uploaded to the Kenjo candidate as attachments. Recruiters open them where they review the candidate anyway, instead of hunting through an inbox. Kenjo also accepts files on the application itself, for documents that belong to one specific position.
The end customer's own custom fields
Kenjo lets every company add custom fields, marked with the c_ prefix, to candidates and applications. Kini maps answers from your application form onto these fields, so details the recruiting team relies on, such as availability or salary expectations, arrive in the fields they already filter on.
Every field. Every entity.Exactly where it belongs.
Kini works with four Kenjo records: positions and the offices they belong to come in, candidates and applications go back. The key fields are spelled exactly as in Kenjo's API reference.
Positions
Offices
Candidates
Applications
Kenjo keeps a position's address on the office it belongs to, not on the position. Kini reads the office for every position, so the job reaches your channels with street, postal code, city and country.
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 Kenjo integration.
Which Kenjo positions Kini publishes, how applicants are written into Kenjo, and what an end customer arranges with Kenjo before the connection starts.
Positions come in from Kenjo's recruiting module, each with the office that holds its address. Kini writes candidates, their applications and the uploaded documents back into Kenjo. Kini only reads positions and offices and does not change them, and it leaves Kenjo's employee, attendance and other HR data alone.
Those with the status Active. Positions in Draft stay out until the end customer activates them, and a position that is set to Closed or Archived is taken down at the next import, when Kini archives the job and reports the change through its job updates.
API access for its Kenjo account. Kenjo's documentation says the API has to be activated by Kenjo's Customer Success team first. After that, an admin generates an API key in Kenjo's settings and enters it in Kini's setup form, which is the only credential the connection asks for.
Yes. Kenjo accepts custom fields, prefixed with c_, when an application is created and when a candidate is updated. Kini maps your application form's answers to the fields the end customer names, so information the recruiting team filters on arrives in Kenjo as structured data.
No. Kenjo stays the end customer's system of record for positions, candidates and hiring, as well as for the rest of its HR work. Kini adds the operated connection to the channels where those positions are advertised and delivers the applications that result.
Kini keeps the application and reports why. Each application has a sync status in Kini, and your platform receives changes by webhook or by polling. An expected case, such as a position that is no longer published, is marked as an expected failure; anything else carries its error so it can be acted on.
No longer than 180 days in personal form. After that, Kini anonymises the application and removes contact details, documents, notes and screening answers. Kini processes the data in Frankfurt in the EU and offers a data processing agreement; the records written into Kenjo follow the end customer's own rules.
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."
