How Kini fits into an employer's iCIMS setup.
iCIMS models people, jobs and the candidacy that links them as separate profiles. Kini reads jobs and writes the other two for each end customer you connect, within the permissions the employer grants.
Jobs selected with iCIMS's own search
Kini uses the iCIMS search interface to find the jobs an end customer wants advertised, filtered on the folders and fields the account works with. It then reads each job profile with title, location, hiring manager and job owner, so only the intended jobs reach your channels, complete with their details.
Applicants as iCIMS person profiles
Each applicant becomes an iCIMS person profile with first name, last name, email and address, filed in the folder the end customer uses for new candidates. Recruiters work with these people in iCIMS exactly as with candidates who arrived through the employer's own career site.
Linked to the job through an applicant workflow
iCIMS records every person-to-job relationship as an applicant workflow with its own status and bin. Kini creates that workflow for each application, so the candidate shows up in the job's recruiting pipeline instead of sitting unattached in the person database.
The account's field rules apply
iCIMS applies the same field visibility, required fields and security rules to API access as to its users. Kini works with the profile fields its integration user is allowed to see and fill, so an application never bypasses what the end customer has locked or made mandatory.
Locations resolved to readable places
iCIMS stores a job's location as a reference to a separate location profile rather than as text on the job. Kini follows that reference for every imported job, so your channels receive the actual place of work instead of an internal iCIMS identifier.
Every field. Every entity.Exactly where it belongs.
Three kinds of iCIMS records are involved: job profiles come in, person profiles and applicant workflows go back. Field names follow iCIMS's public API documentation.
Job Profiles
Person Profiles
Applicant Workflows
iCIMS keeps people, jobs and the relationship between them as three separate records. The relationship, an applicant workflow, carries the status of one person's candidacy for one job, and that is where recruiters track the application.
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 iCIMS integration.
How Kini finds an employer's jobs in iCIMS, where applicants end up, and what the employer's iCIMS team prepares for the connection.
Job profiles come in from iCIMS. For each applicant, Kini creates a person profile and an applicant workflow that links the person to the job. Kini does not create or change jobs in iCIMS and does not touch onboarding, events or talent pools.
An integration user. iCIMS's search interface only works for users in the Integration User group, and every field Kini reads or fills follows that user's permissions in iCIMS. The employer's iCIMS administrators therefore decide which jobs, folders and fields the connection can work with.
iCIMS distinguishes integrations built for one specific customer from integrations it defines for many customers, and it states that a partnership is not required to build one. Integrations offered to many iCIMS customers go through a review with iCIMS's developer support team before they are validated.
Because iCIMS checks required fields on every profile it creates, through the API as well as in the platform. If an end customer makes a person field mandatory that your application form did not collect, iCIMS refuses the record until that field is filled, which keeps the account's data rules intact.
No. iCIMS remains the employer's system of record for jobs, people and the hiring process. Kini connects the jobs to the channels where candidates find them and returns applicants to iCIMS, where recruiters keep working with the workflows and folders they already use.
Kini keeps a sync status for every application and updates it once iCIMS has accepted or rejected the records. Your platform follows it through the sync status webhook or Kini's API, and a successfully delivered application also shows the identifier iCIMS assigned.
In Frankfurt, in the EU, under a data processing agreement Kini offers. Kini anonymises applications 180 days after creation and removes their contact details, attachments, notes and screening answers. The person profile in iCIMS stays under the employer's own retention 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."
