How Kini connects Eightfold to your channels.
Eightfold organises hiring around positions, candidate profiles and the applications that connect them. Kini works with all three for every end customer you connect, so applicants from your channels end up exactly where Eightfold's recruiters and matching expect them.
Positions with their location and work model
Kini imports the positions an end customer has in Eightfold with name, job description and employment type, plus the location data Eightfold stores per position: city, country and the working-location option, such as onsite, hybrid or remote. Archived or deleted positions stay out of your channels.
The position's own apply-form questions
Eightfold defines apply-form questions per position, including which ones are required and which only appear after a certain earlier answer. Kini reads them for your application flow, and the answers return to Eightfold with question ID, question and answer, so recruiters see them on the application itself.
A profile for every applicant, resume included
For each applicant, Kini creates an Eightfold profile with first name, full name, email, phone and location, and sends the CV along as the profile's resume. Because the person now exists as a profile, Eightfold can also match them against the employer's other positions, not only the one they applied for.
The application on the right position and stage
Kini places each application on the position the candidate chose and sets its stage, with your channel recorded as the application's creation source. Recruiters find the applicant in that position's pipeline in Eightfold and continue from there, without a separate import or a forwarded email.
Access limited to what the connection uses
Every Eightfold API key carries READ and WRITE permissions per entity. The end customer can give Kini's key read access to positions and write access to profiles and applications and nothing more, so the connection never touches employee data or records it does not need.
Every field. Every entity.Exactly where it belongs.
Four kinds of Eightfold records are involved: positions and their apply-form questions come in, profiles and applications go back. Each field below carries the name it has in Eightfold's API reference.
Positions
Apply-Form Questions
Profiles
Applications
Eightfold's position flag `open` only says that a position has not been archived or deleted; Eightfold's own reference notes that it is not the recruiting status. Kini therefore also reads the status Eightfold keeps for the position before it publishes the job.
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 Eightfold integration.
What Kini reads from Eightfold, how applicants arrive there, and which API key and permissions an employer prepares before the first application.
Positions and their apply-form questions come in from Eightfold. In return, Kini creates a profile for each applicant with the CV as resume, and an application on the chosen position with the candidate's answers. Kini does not change positions in Eightfold and does not read employee records.
An Eightfold API key and the email address of the API user the integration acts for. An admin generates the key in Eightfold's integration settings and assigns its permissions per entity, with separate READ and WRITE switches, before entering both values in Kini's setup form.
Read access to positions, so Kini can import jobs and their apply-form questions, and write access to profiles and their applications, so Kini can deliver applicants. Eightfold checks every request against the key's permissions and refuses anything outside them, which keeps the rest of the account closed to the connection.
Yes. Eightfold records for each apply-form question whether it is required and whether it depends on an earlier answer. Kini applies both rules in your application flow, so candidates only see questions that apply to them and cannot skip the required ones before their application is sent.
No. Eightfold remains the employer's system of record for positions, profiles and hiring decisions, including its own matching. Kini connects those positions with the channels where candidates find them and delivers the resulting applications, while recruiters keep working in Eightfold as before.
Through Kini's sync status. Kini delivers applications to Eightfold in the background and sets a status for each one, which your platform receives by webhook or reads from Kini's API. After a successful delivery, the application in Kini also carries the identifier Eightfold assigned, so both systems refer to the same record.
Kini processes it in Frankfurt, within the EU, and a data processing agreement is available. After 180 days, Kini removes the personal parts of an application, such as contact details, documents, notes and answers, from its own records. The profile written into Eightfold is governed by the employer's settings there.
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."
