What Kini handles between Bullhorn and your channels.
In Bullhorn an agency works with job orders, candidates and job submissions. Kini reads the first and writes the other two for every end customer you connect, so recruiters keep working in the pipeline they already use.
Only the job orders an agency wants advertised
Bullhorn decides per job order whether it is still open (isOpen) and whether it may appear on a job board (isPublic). Kini publishes only job orders that are both, using the public description rather than the internal one, so client details written for recruiters never reach a candidate-facing channel.
Applicants as Bullhorn candidates, ready for the desk
Every applicant becomes a Bullhorn candidate with first name, last name, email, phone and address, and the channel they came from is stored in the candidate's source field. Recruiters search, own and contact these people like any candidate they sourced themselves, without retyping anything from an email.
A job submission on the job order they chose
Kini links each new candidate to the job order the person applied for by creating a job submission. The application therefore shows up in that job order's pipeline straight away, where the recruiter moves it through the submission statuses the agency has configured in Bullhorn.
The CV stored on the candidate record
The CV and any other document an applicant uploads are attached to the Bullhorn candidate as files, with their original name and content type. A recruiter opens the CV from the candidate record instead of an inbox, and the file stays with the person for every later submission.
A delivery status per applicant, visible to you
Kini hands every application to Bullhorn in the background and records the outcome. Your platform learns it through the sync status webhook or by polling Kini's API, and once an application has arrived, Kini returns the ID it received in Bullhorn, so both sides can point to the same record.
Every field. Every entity.Exactly where it belongs.
Four Bullhorn entities take part in the connection: job orders travel out to your channels, while candidates, job submissions and candidate files come back. Field names are spelled as in Bullhorn's REST API entity reference.
Job Orders
Candidates
Job Submissions
Candidate Files
In Bullhorn an application is not a record of its own. A JobSubmission links a candidate to a job order, so Kini writes two records for each applicant, the candidate first and the submission second.
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 Bullhorn integration.
Which job orders Kini publishes, how applicants land in an agency's Bullhorn pipeline, and what the agency provides to connect its account.
Job orders come in from Bullhorn when they are open and public. In the other direction, Kini creates a candidate for each applicant, a job submission that ties the candidate to the job order, and the uploaded files on the candidate record. Kini does not edit job orders in Bullhorn; it only reads them.
Only job orders that Bullhorn marks as open and as public. A job order the agency keeps internal, or one that has been filled or closed, stays out. When a published job order stops being open or public, Kini archives the job, and your platform receives the change through Kini's job updates.
API access to its Bullhorn account. Bullhorn's REST API uses OAuth 2.0, so the agency provides a client ID and client secret issued for its account, together with the username and password of a Bullhorn API user. Kini stores these credentials for that one account only.
Because Bullhorn models an application as a job submission between a candidate and a job order. The candidate holds the person's details and files, while the submission holds the status on one specific job. Both records are needed for the application to appear in the job order's pipeline.
Kini records the outcome rather than dropping it. A rejection the target system expects, such as a job order that is no longer published, is marked as an expected failure and needs no action. Every other failure is visible with its error through Kini's API and the sync status webhook, per application.
No. Bullhorn remains the agency's system of record for job orders, candidates and placements. Kini sits between Bullhorn and the channels where those job orders are advertised, and it returns applicants into Bullhorn. Recruiters keep their desk, their pipeline and their reporting in Bullhorn.
Kini processes application data in the EU, in Frankfurt, and offers a data processing agreement. Inside Kini, contact details, attachments, notes and screening answers are removed from an application 180 days after it was created. What Kini wrote into Bullhorn stays under the agency's control there.
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."
