How Kini connects eRecruiter in both directions.
eRecruiter hands jobs out through an XML job feed and takes applicants and applications in through its API. Kini works both routes for every end customer you connect. The five cards below show what that covers.
Jobs straight from eRecruiter's job feed
eRecruiter generates an XML job feed on the applicant portal for publishing jobs to third-party applications. Kini reads the end customer's feed, by default once an hour, and imports every job with its title, subtitle, location, job profile, employment type, career level and the responsible recruiter's name and email, together with the job and apply links eRecruiter provides.
Ad text kept in its parts
eRecruiter's feed carries a job ad as separate texts: company description, job description, requirements, additional text and footer. Kini keeps these apart and labels them as introduction, tasks, candidate profile and other information, in that order. A channel can then place each part where it belongs instead of showing one undivided block of text.
Jobs that leave the feed are archived
Every read of the eRecruiter feed is compared with the jobs Kini still holds as active from earlier reads. A job no longer in the feed is marked as archived in Kini once the newer read has completed. Positions closed in eRecruiter therefore do not linger as active jobs, and nobody has to close them again by hand.
Complete applicant profiles, documents included
For every application, Kini creates an applicant profile in eRecruiter with name, email, mobile number, gender, date of birth and address. The CV goes into the profile's CV slot and the photo becomes the profile photo. Further files are added as documents typed as cover letter, certificate or other, and the application then links the profile to the job.
The source of every application in eRecruiter
Kini writes the channel each application came from into eRecruiter's Referrer field. eRecruiter's own API guide recommends filling that field, since it can drive statistics on which sites applicants come from. If the end customer's eRecruiter already records sources under its own labels, a mapping set per end customer turns Kini's channel names into those labels.
Every field. Every entity.Exactly where it belongs.
Four kinds of data move between eRecruiter and Kini. Jobs arrive through eRecruiter's XML job feed, while applicant profiles, their documents and the applications go out through eRecruiter's API. Key fields are spelled the way eRecruiter's feed and API documentation spell them.
Jobs
Applicants
Documents
Applications
eRecruiter uses two routes. Kini reads jobs from the XML job feed of the end customer's applicant portal rather than from the API, and writes applicants and applications through the API. Each end customer therefore provides a feed URL in addition to API access.
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 eRecruiter integration.
Answers on the eRecruiter job feed, on applicant profiles and documents, on application sources and delivery, and on what each end customer sets up.
Jobs come in from eRecruiter with title, subtitle, location, job profile, employment type, career level, responsible recruiter and the job ad text. In the other direction, Kini sends applicants with their contact and address details, their CV, photo and other documents, and an application that links each applicant to the job and records the source.
No. eRecruiter remains the end customer's system of record, where recruiters review applicants and run their hiring process. Kini sits between eRecruiter and the channels you connect: it picks up the published jobs, delivers each application into eRecruiter, and operates that connection as a managed service, so nobody on your side has to maintain it.
The XML job feed of the end customer's applicant portal. eRecruiter describes this feed as the way to publish jobs to third-party applications, and it lists each published job with its ad text, location and responsible contact. Applicants and applications take a different route: Kini writes them into eRecruiter through its REST API.
By default once an hour. Kini reads the end customer's eRecruiter feed on an hourly schedule, and that schedule is set separately for each end customer. New and changed jobs come in with the next read. A job that has disappeared from the feed is archived in Kini as soon as a newer read has completed.
Every file attached to the application. The CV is stored as the applicant's CV and a photo as the profile photo. Cover letters and certificates are uploaded as documents of those types, anything else as other documents. Kini takes the file format from the file's declared type for PDF, Word, RTF, JPG and PNG, and otherwise from the file name.
Not for applications that Kini delivers. eRecruiter can send a registration email when an applicant profile is created and a confirmation email when an application is created. Kini switches both off, so a candidate who applied through one of your channels does not receive an unexpected registration message from eRecruiter as well.
Each application in Kini carries a sync status that shows whether it reached eRecruiter. When eRecruiter cannot be reached, is temporarily unavailable or limits the request rate, Kini tries the delivery again automatically. Other failures are stored with the application so they can be followed up, and partners can watch the status through Kini's API or a webhook.
API access to their eRecruiter account: an API key, the mandator ID that identifies their eRecruiter client account, and the address of their eRecruiter API, which for the cloud version is usually eRecruiter's standard API domain. For jobs, Kini also needs the URL of the XML job feed on their applicant portal.
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."
