What Kini handles for employers on Ashby.
Ashby gives every job posting its own application form and expects job boards to submit applications through it. Kini works that way for each end customer you connect, from the posting to the submitted form.
Published postings, with compensation only where allowed
Kini imports published Ashby job postings with title, department, team, location, workplace type, employment type and the HTML description. Ashby also states per posting whether it is listed and whether compensation may be shown to applicants, so salary details appear in your channels only where the employer permits it.
The posting's real application form
Every Ashby job posting carries its own application form definition: sections, fields, which fields are required and which only appear under certain conditions. Kini rebuilds that form in your channel, so candidates answer exactly what the employer asks on its own Ashby careers page.
Submitted the way Ashby expects from job boards
Ashby asks job boards to submit applications through the posting's application form rather than by creating candidates directly. Kini follows that route, so each applicant lands on the right posting with the form's answers, and any blocking rules the employer configured in Ashby still apply.
Resume uploaded ahead of the submission
Files such as the resume are uploaded to Ashby first and then referenced in the submitted form. Ashby recommends this route for forms with file fields because it is faster and more reliable, and it keeps a large CV from holding up the application itself.
Consent and campaign data on the application
Where the employer's form asks for data consent, Kini passes the candidate's acknowledgement in the matching field. Your campaign parameters travel along as UTM data, so recruiters see on the application in Ashby both what the candidate agreed to and which campaign brought them in.
Every field. Every entity.Exactly where it belongs.
The connection uses three parts of Ashby: job postings and their application form definitions come in, form submissions go back. Field names follow Ashby's API reference.
Job Postings
Application Form Definitions
Application Form Submissions
Ashby identifies form answers by field path, not by question text. Standard fields such as name, email and resume have fixed system paths, while every custom question has its own path in the posting's form definition, which Kini maps for each posting.
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.
Step 1Connect
Step 2Map
Step 3Test
Step 4Go-live!
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 Ashby integration.
Which Ashby postings Kini publishes, how applicants are submitted to them, and what access an employer grants in Ashby.
Published job postings and their application form definitions come in from Ashby. Kini sends back completed application forms with the candidate's answers, the resume, consent where the form asks for it, and UTM data for the channel. Kini does not edit postings in Ashby or read interview and offer data.
An Ashby API key with read access to jobs and write access to candidates. Ashby assigns read and write permissions per module to every key and rejects any request the key is not permitted to make, so the rest of the employer's Ashby account stays closed to the connection.
Ashby offers dedicated job feeds to partners, in JSON or XML. Once an Ashby customer enables the partner's integration in Ashby's admin settings, its published postings appear in that feed. Setting up such a feed for Kini is arranged with Ashby's integrations team.
Ashby reports whether a submission was blocked by one of the employer's blocking rules, together with the message meant for the candidate. Kini records that outcome on the application, so your platform knows the submission did not enter the pipeline and why.
No. Ashby stays the employer's system of record for postings, candidates, interviews and hiring decisions. Kini connects the published postings to the channels where candidates find them and submits the resulting applications to Ashby, where the recruiting team continues as usual.
Each application in Kini has a sync status that is updated once Ashby has accepted or refused the submitted form. Your platform reads that status from Kini's API or receives it by webhook, without asking the employer whether the candidate arrived.
Personal data stays in Kini for 180 days after an application was created; then Kini anonymises it and removes contact details, files, notes and screening answers. Processing takes place in Frankfurt in the EU under a data processing agreement, and the application in Ashby follows the employer's own rules.
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."



























