What Kini does between Lever and your channels.
Lever organises hiring around postings and the opportunities that candidates create when they apply. Kini reads the postings and submits applications to them for every end customer you connect, as the cards below describe.
Published postings with team, location and commitment
Lever separates published postings from unlisted, closed, draft and pending ones. Kini imports published postings with title, HTML description, team, department, location, commitment and workplace type, plus the structured address where the account keeps one, so every job reaches your channels with the details recruiters entered.
Applications through Lever's own apply route
Kini submits every application to its posting through the apply endpoint Lever provides for custom application forms. Lever creates the candidate and the application in one step, so the applicant appears in the posting's pipeline exactly as if they had applied on the employer's own Lever job site.
The posting's application questions, in Lever's order
Before a candidate applies, Kini reads the posting's application questions: personal information, links, custom question sets and file fields. Your form shows these fields in the order Lever defines, and the answers go back as the custom questions Lever expects rather than as unstructured text.
Resume uploaded before the application
Lever takes files as separate uploads that the application then references. Kini uploads the resume and any further document first and links them in the submission, so the CV sits on the candidate in Lever and recruiters open it there instead of in a forwarded email.
Channel source and contact consent included
Every application carries your channel as its source tag in Lever. Where the candidate agreed to hear about future roles, Kini passes that consent in the field Lever provides for it, so recruiters can filter by source and see what the candidate agreed to on the application.
Every field. Every entity.Exactly where it belongs.
Three Lever objects take part: postings and their application questions come in, applications go back. Field names follow Lever's API documentation.
Postings
Application Questions
Applications
Lever only accepts applications for postings in the state published or internal, which Lever's app shows as unlisted. An application for a closed, draft or pending posting is refused, so Kini takes a posting down from your channels once it leaves the published state.
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 Lever integration.
Which Lever postings Kini publishes, how applications are submitted to them, and how an employer authorises the connection.
Published postings and their application questions come in from Lever. Kini sends back applications with personal information, resume, answers to the custom questions, links and the channel as source. Kini does not create or edit postings in Lever and does not touch interview feedback or offers.
Postings in the state published. Lever also lets candidates apply to unlisted postings through a direct link, but those are kept off public job sites by design, so Kini leaves them out as well. Closed, draft and pending postings stay out, and a posting that is closed later is taken down.
Through OAuth. Lever's documentation reserves API keys for customers building internal workflows and asks integrations to authenticate with OAuth instead. An admin of the employer's Lever account therefore authorises Kini once, and Kini then acts only within the access granted there.
Not by default. Lever's documentation states that it sends no application confirmation email for applications submitted through its API unless the request asks for one. Whether candidates from your channels get Lever's confirmation is therefore a setting per end customer, not something left to chance.
No. Lever stays the employer's system of record for postings, candidates, interviews and hiring decisions. Kini connects the published postings with the channels where candidates find them and hands the resulting applications to Lever, where recruiters continue in their usual pipeline.
From the sync status Kini keeps per application. It changes once Lever has accepted the submission or refused it, and your platform reads it from Kini's API or receives it by webhook. Once delivered, the application in Kini also carries the ID Lever returned for it.
Kini handles it in Frankfurt, inside the EU, and offers a data processing agreement. Contact details, files, notes and screening answers are stripped from Kini's copy of an application 180 days after its creation, while the candidate in Lever follows the employer's own retention settings.
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."
