How Kini works with the Umantis Bewerbermanagement.
Umantis publishes jobs through its job market and XML exports, and it accepts applications through its import interface. Kini runs both directions as a managed service for every end customer on Umantis. Five places where that makes the clearest difference.
Applications arrive as regular Umantis applications
Kini sends every application from a connected channel through the application import that Umantis provides for its Bewerbermanagement. Name, salutation, email, address, phone and the candidate's notes arrive as a normal Umantis application, linked to the Umantis job by its job ID. Kini marks the application as delivered only once Umantis confirms the import.
CV, cover letter and photo in the right document fields
Kini packs the candidate's files into the ZIP archive that the Umantis import expects and names each one in its matching field: the CV as Lebenslauf, the cover letter as Bewerbungsschreiben, the photo as the person's photo. Further files, such as certificates, go into the additional document fields. The document mapping can be adjusted per end customer.
The source channel on every application
Kini writes the channel an application came from, such as the job board the candidate used, into the application's status remark in Umantis. Where an end customer tracks sources somewhere else, Kini writes it into the Umantis fields they name instead, and can translate Kini's channel names into the source labels the customer already uses.
Entry status and fixed field values per end customer
New applications enter Umantis with the status Bewerbungseingang, unless an end customer works with a different entry status, which Kini then sets instead. Kini can also fill further Umantis import fields, such as user-defined lists or texts, with a fixed value per end customer. Umantis expects list values to match an entry of its selection list exactly.
Jobs from the Umantis job market or XML export
Kini reads the end customer's jobs from the external job market of their Umantis Bewerbermanagement, or from an XML export that Umantis offers for job boards, whichever the customer uses. Because each Umantis XML export has its own layout, Kini sets it up per customer. Jobs that leave the Umantis listing are archived in Kini after the next complete run.
Every field. Every entity.Exactly where it belongs.
Kini exchanges four kinds of data with Umantis. Jobs come in from the job market or an XML export, and candidates, applications and their documents go out through the Umantis application import. Field names below are spelled as Umantis documents them for that import.
Jobs
Candidates
Applications
Documents
Kini connects the Umantis Bewerbermanagement in two ways. This integration uses the Umantis SOAP import for applications and the job market or an XML export for jobs. Kini's connection through the Umantis ATS API, is a separate integration with its own Abacus Umantis page.
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 Umantis integration.
How this integration differs from the Abacus Umantis page, how jobs reach Kini, how applications and documents get into Umantis, and what happens when an import does not go through.
By the interface, not by the system behind it. Umantis, part of the Abacus Group since 2023 and now branded Abacus Umantis, runs its Bewerbermanagement as recruitingapp solutions. This integration reaches them through the SOAP import and the job market or XML export. The Abacus Umantis page covers Kini's connection to the same solutions through the Umantis ATS API.
Jobs come into Kini from the end customer's Umantis job market or XML export and go on to the connected channels. In the other direction, Kini imports applications into Umantis: the candidate's contact details and address, the link to the Umantis job, an entry status, the source channel and the attached documents.
Through the SOAP import that Umantis documents for its Bewerbermanagement. Kini builds one application import per candidate, with the documents in an accompanying ZIP archive, and sends it to the end customer's Umantis solution. Umantis answers with a result message, and Kini records the application as delivered only when that message confirms the upload.
Once an hour by default. The schedule is set per end customer, so it can be changed when a customer needs a different rhythm. After each complete run, jobs that are no longer listed in Umantis are archived in Kini, and Kini campaign bookings for those jobs are set to unpublished.
Umantis looks the person up before it creates anyone new. Its application import identifies applicants by email address, or by last name, first name and postcode, and Kini always sends the email address. A candidate who is already in Umantis is therefore found by that address instead of being entered a second time.
The CV, the cover letter, a photo and any further files the candidate uploaded. Kini sends them in a ZIP archive together with the application and assigns each file to its Umantis field: CV, cover letter and personal photo, with everything else in the additional document fields. The mapping can be adjusted where an end customer's setup differs.
Yes. By default, Kini writes the channel, for example the job board the candidate applied through, into the application's status remark in Umantis. For an end customer who records sources elsewhere, Kini writes it into the Umantis fields they choose and can translate its channel names into the labels that customer already uses.
It can. The Umantis import can send a status email to the address set up in the Umantis solution after each completed import. Kini requests this email by default, and it can be switched off per end customer when the recruiting team does not want a message for every imported application.
Kini marks the application's sync as failed instead of reporting it as delivered, so it can be followed up rather than lost. Connection problems and temporary server errors are retried automatically. Every application keeps a visible sync status in Kini, which shows whether it reached Umantis.
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."
