What Kini handles when your customers' jobs come from Phenom.
A Phenom job feed lists open positions, but it is not yet a set of clean jobs your channels can use. Kini runs that import for each end customer as a managed service. Five places where that shows.
Jobs from each end customer's Phenom feed, every hour
Kini reads the XML job feed that lists an end customer's Phenom jobs and imports every posting with its title, description, posting and apply links, contract type, category, contact person and location. The import runs on a schedule set per company, once an hour by default, so new and changed jobs reach Kini without anyone exporting them by hand.
Only the jobs that belong to your end customer
A Phenom feed can carry more jobs than one end customer needs, for example the postings of every branch of a large employer. Kini narrows it down per company: by keywords that must appear in the job title or description, by a list of cities, or by both. Only the postings that match are imported.
Closed jobs come off your channels on their own
When a posting disappears from the Phenom feed, Kini archives the job at the end of the first import that no longer finds it and takes its campaign bookings offline. If the same posting returns to the feed later, Kini reactivates the existing job and republishes those bookings instead of creating a second copy of the job.
Apply links that arrive intact
Apply links in a Phenom feed can contain characters such as spaces that strict URL checks reject, which would stop a job from being imported. Kini encodes posting and apply links before the import, so they still lead to exactly the same page. Per company, Kini can also swap part of the apply link, such as a tracking parameter.
Contract types and categories in standard values
Kini translates the contract type and category from the Phenom feed into its own standard values and keeps the original value next to the translated one. A value Kini has not seen before is recorded for mapping rather than guessed. Country names become two-letter codes, and postings without a title or reference number are held back.
Every field. Every entity.Exactly where it belongs.
Kini reads jobs from Phenom and nothing else: no candidates and no applications. Each job comes from the end customer's Phenom job feed with its text, links and classification, plus one record per location. Phenom publishes no public specification for these feeds, so the fields below are named in plain terms.
Jobs
Job locations
Phenom job feeds are set up per customer and do not all share one layout. Kini reads the same fields from the flat layout and from the layout with a nested location block, so jobs from both arrive in the same shape.
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 Phenom integration.
What Kini reads from Phenom, how often it checks, what happens when a job closes, and where candidates apply.
Jobs, and only jobs. From the end customer's Phenom job feed, Kini takes each posting's reference number, title, description, posting and apply links, contract type, category, contact person and location details. Candidates and applications are not part of this integration; they stay with the apply flow that each job links to.
No. This integration reads jobs and sends nothing back. Each imported job keeps the apply link from the Phenom feed, so candidates apply wherever the employer's Phenom setup sends them, and no applicant data passes through Kini on the way. Your team therefore has no applications from Phenom jobs to store or forward.
No. Kini imports jobs from the XML job feed that carries the end customer's Phenom jobs. Phenom's developer portal documents several APIs, among them a Jobs API for viewing and managing jobs and an Apply API through which partners submit applications. This integration uses neither of them; it works from the feed alone.
Once an hour by default. The schedule is set per company, so each end customer's feed is read at its own fixed time within the hour. New postings, changed texts and removed jobs show up in Kini after the next run, without anyone having to start the import by hand.
Kini archives it. Once an import completes without the posting, the job is set to archived, which in Kini means it is no longer available at its source, and its campaign bookings go offline. Should the posting reappear in the feed, the existing job becomes active again rather than being imported twice.
Yes. When one feed lists more jobs than an end customer should receive, Kini filters it per company. A keyword filter keeps postings whose title or description contains one of the given terms, in any capitalisation. A location filter keeps postings in the listed cities. With both set, a posting has to match both.
Where a Phenom feed lists the same posting once per location, Kini keeps each location as a job of its own. The location is part of how Kini recognises a job, so a second location does not overwrite the first. Each of these jobs carries its own city, street and postal code wherever the feed provides them.
No. Phenom describes itself as a layer that works alongside the applicant tracking system, which remains the record-keeping system. Kini replaces neither: it reads the jobs from the Phenom feed and makes them available to the channels you run through Kini. Nothing is written back to Phenom or to the ATS.
A Phenom job feed that lists the customer's jobs, and its address. Kini sets the import up per end customer with that address and, if the feed carries more than the customer's own jobs, a keyword or city filter. No Phenom login or API credentials are involved, because Kini only reads the feed.
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."
