OnApply as a managed job source in Kini.
OnApply lists a company's open positions on a hosted career page and adds structured data to its job ads. Kini turns both into a managed job source. Here are five things Kini takes off your team.
OnApply jobs in Kini without an integration project
Kini reads the jobs an end customer publishes on their OnApply career page, opens each job ad and imports it as a job in Kini. Kini sets this up per end customer, so nobody on your side builds a connector, and the customer does not create API keys or hand over OnApply log-in details.
Address and employer details from OnApply's structured data
OnApply adds structured data in the schema.org JobPosting format to its job ads. Kini reads the title, description, employment type and full address from it, with street, postcode, city and country, and converts the country to a two-letter ISO code. The employer's name, logo and website stay with the job as custom fields.
Category and employment type in Kini's standard values
Kini translates a job's employment type, and the career page section it is listed under, into Kini's standard values for employment type and category. The wording as it appeared on OnApply is stored too, so every value can be traced back. A value with no match yet leaves the field empty rather than guessed and is recorded for mapping.
Closed positions leave Kini and the booked channels
Each sync reads the list of jobs on the career page as it stands. A job that is no longer listed is archived in Kini, and its active campaign bookings are unpublished, which takes those ads offline instead of advertising a closed position. If the job returns to the career page, Kini reactivates it and republishes the bookings.
Applications keep their route into OnApply
Each imported job keeps two links: the job ad on the OnApply career page and the address behind its apply button. Where a channel sends candidates to that application link, they apply in OnApply's own form, and OnApply files the application in its system. Applicant data on that route never passes through Kini.
Every field. Every entity.Exactly where it belongs.
The OnApply integration is inbound. Kini reads jobs from the end customer's OnApply career page and from the structured data in each job ad. The field names below are the schema.org names that structured data uses; career page details without fixed names are listed by label.
Jobs
Job locations
Employer details
Career page details
Only jobs listed on the OnApply career page reach Kini. A job that exists in OnApply but is not shown on the career page is not imported, and taking a job off the career page archives it in Kini at the next sync.
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 OnApply integration.
What Kini takes from OnApply, how often it syncs, what happens to edited and closed jobs, and where applications go.
Jobs. For every job on the end customer's OnApply career page, Kini imports the title, description, employment type, address, the employer's name, logo and website, the header image, the career page section it is listed under, and the links to the job ad and its application form. Candidates and applications are not part of this integration.
No. This integration reads jobs and writes nothing into OnApply. Each job keeps the link to its OnApply application form, so candidates who follow that link apply in OnApply directly. Applications collected on other channels are not transferred into OnApply by this integration; speak to the Kini team before promising that route to an end customer.
No. Kini reads the published career page and the job ads on it, so the integration needs no API key, password or user account in OnApply. Kini configures the import for each end customer from the address of their career page. Your customer keeps publishing jobs in OnApply exactly as before, and nothing changes in their account.
On a schedule Kini sets for each end customer. Partners can also request a job sync through Kini's API at any time, up to once a minute per company, and the company record shows when the last job sync finished. Changes on the career page therefore reach Kini with the next sync rather than instantly.
Once the job no longer appears on the career page, the next sync sets its status in Kini to archived, so systems reading jobs from Kini see that it is gone. Bookings of that job that belong to an active campaign are unpublished in the same step. A job that reappears on the career page later becomes active again.
The next sync picks up the new version. Kini compares each imported job with the version it already holds and, when the content differs, updates the job and records the time of the change. Partners that pull jobs from Kini can filter on that timestamp and fetch only the jobs whose content changed since their last sync.
No. OnApply offers a snippet, an XML or JSON feed and an API for showing its job ads on other websites. Kini works from the published career page itself and the structured data in each job ad. For your customer, that means the OnApply career page is the one place a job has to be published to reach Kini.
No. OnApply stays the system of record: job ads are created, approved and published there, and applications are managed there. Kini takes the published jobs from the career page and makes them available to your systems and to the channels you book, without changing anything in the end customer's OnApply account.
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."
