What Kini takes care of for jobs from sopea.
Your end customer creates and closes job ads in sopea. Kini reads them from there and prepares them for the channels you distribute to. Five parts of that work Kini handles, with no export for your team to build or maintain.
sopea jobs in Kini, imported on a schedule
Kini reads each end customer's open job ads from sopea on the schedule set for that customer, by default once an hour. When a change should reach Kini sooner, your team can trigger an extra import through Kini's API. Nobody on your team exports jobs from sopea by hand or builds a connection for each new customer.
One job for every location on a job ad
A sopea job ad can list several locations. Kini creates a separate job for each of them, with its own location name, street and house number, postcode and city, so each location can be booked as a job of its own. A job ad without any location still arrives in Kini as a single job.
The full job ad text, with its sections intact
For every job, Kini opens the published sopea job ad page and takes over its text blocks in their original order. The title heading is kept as a subheading, and text that sopea formats as a heading but reads as a full sentence becomes a normal paragraph. The description keeps its sections without stray headings.
Pay, contact and employer details travel with each job
Kini also takes over what sopea lists with the job ad: the salary range with currency and period, the contact person's name and phone number, the start date, the contract period and the job ad image. Employer name, website and logo are stored with each job, which matters where one sopea account runs job boards for several company units.
Closed in sopea, archived in Kini
sopea stays the place where jobs are opened and closed. When a job ad is no longer in the end customer's sopea job list, Kini archives the job after the next completed import and rebuilds that customer's job feeds. If the same job ad comes back later, Kini reactivates the existing job rather than creating a duplicate.
Every field. Every entity.Exactly where it belongs.
The sopea integration is inbound. Kini reads the end customer's list of open job ads from sopea as a feed, opens each published job ad page for its text, and stores the result as Kini jobs. sopea publishes no public specification for this feed, so the fields below carry plain labels rather than sopea's own field names.
Jobs
Locations
Salary, contact and employer details
One sopea job ad with several locations turns into several Kini jobs that share a single external ID. Expect one result per location when you look a sopea job up by that ID.
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 sopea integration.
What Kini reads from sopea, how often it does so, and what happens to a job when it changes or closes in sopea.
Job ads, and what sopea lists with them: the job title, the full job ad text, the job ad and application links, each location with its address, the organisational unit, work schedule, employment type, contract period, start date, salary range, contact person and employer details. Kini only reads this data and writes nothing back to sopea.
No. The integration is inbound: Kini imports jobs from sopea and creates no candidates or applications there. Each job keeps the application link sopea provides, so candidates who use it apply in sopea directly. Applications that reach Kini through another channel, such as a job board's own apply flow, are not written into sopea by this integration.
By default once an hour, on a schedule set for each end customer. Your team can also trigger an extra import through Kini's API when a change in sopea should arrive sooner. Every import reads the complete list of open job ads, so new, changed and closed jobs are all picked up in the same run.
Once a job ad no longer appears in the sopea job list, Kini archives the job after the next completed import and rebuilds the end customer's job feeds. In Kini, archived means the job is no longer available at its source. If the job ad returns to sopea later, Kini reactivates the existing job instead of creating a second one.
It creates one Kini job per location. Each of these jobs carries its own location name, street and house number, postcode and city, while title, text, salary and contact details stay identical across them. Because they all come from the same sopea job ad, they also share its external ID in Kini.
Kini maps them onto its own standard values: the organisational unit onto a job category, and sopea's employment type values onto work schedule and employment type. The original sopea value is kept next to the standard one. Where no mapping exists yet, the standard field stays empty instead of being filled with a guess.
No. sopea stays the system of record: your end customer creates, edits and closes job ads in sopea, and sopea's own career portal is not touched. Kini only reads the job list and the published job ad pages, then makes those jobs available to the channels you distribute to through Kini.
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."
