What Kini takes care of for employers on Breezy.
In Breezy, candidates belong to a position and move through that position's pipeline. Kini feeds those pipelines from your channels for every end customer you connect, starting from the positions the employer has published.
Published positions with location and salary
Breezy positions run through draft, pending, published, closed and archived. Kini imports the published ones with name, description, type, department, category, city, country, remote setting and salary range, so each job reaches your channels with the details the employer entered in Breezy.
Applicants added as applications, not as sourced profiles
Breezy treats a candidate added with the origin applied like an application from its own careers page: the position must be published, and the stage actions the employer configured run as usual. Kini adds every applicant this way, so automatic emails and moves behave exactly as the recruiting team set them up.
Missing required answers completed by the candidate
If a position's application form requires details that your channel did not collect, Breezy still accepts the application and emails the candidate a link to complete them. An application is therefore not lost because one required detail was missing, and the recruiter receives the complete record.
Resume and further documents on the candidate
Kini uploads the resume to the new candidate and attaches further files, such as certificates or a separate cover letter, as documents. Recruiters open everything from the candidate's profile in Breezy instead of hunting through an inbox, and the files stay with the candidate on that position.
Duplicates caught on the position
Breezy refuses to add a candidate who already exists on the same position. Kini records that refusal as an expected outcome rather than an error, so your platform sees that the person is already in the pipeline and nobody has to remove a duplicate by hand.
Every field. Every entity.Exactly where it belongs.
Kini works with three parts of Breezy: positions come in, candidates and their files go back to the position they applied to. Field names are spelled as in Breezy's API reference.
Positions
Candidates
Resumes and Documents
Breezy authenticates API access with the email address and password of a Breezy user rather than with a separate key. The connection therefore runs as one Breezy user, and the companies that user belongs to decide which positions Kini can see.
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 Breezy HR integration.
Which Breezy positions Kini publishes, how applicants are added to them, and what happens when an application is incomplete or a duplicate.
Published positions come in from Breezy. Kini adds each applicant to the chosen position as a candidate with name, email, phone, address, cover letter and source, and uploads the resume and other documents. Kini does not create or change positions in Breezy and leaves scorecards and interviews alone.
With the login of a Breezy user. Breezy's API signs a user in with email address and password, and that user's company membership decides which positions are available. The employer therefore sets up a user for the connection that belongs to the right Breezy company.
Breezy still takes the application. For a candidate added as applied whose details do not cover the position's required form fields, Breezy emails the candidate a link to complete them before the record is finalised, so the application reaches the recruiter once the candidate has filled the gap.
Breezy rejects the second candidate on the same position. Kini marks such a rejection as an expected failure with the reason duplicate, which needs no action on your side: the person is already in that position's pipeline in Breezy, with their first application.
No. Breezy stays the employer's system of record for positions, candidates and the hiring pipeline. Kini publishes the positions to the channels where candidates find them and adds the resulting applicants in Breezy, where the hiring team continues as before.
For 180 days in personal form. After that period, Kini anonymises the application and deletes contact details, documents, notes and screening answers from its copy. Kini processes the data in Frankfurt within the EU and offers a data processing agreement; Breezy keeps its records under 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."
