What Kini does with job postings from BITE.
BITE holds the vacancy, the posting text and the application form. Kini takes the published postings from there and prepares them for job board bookings, without touching the applicant side. These six points describe what that covers.
BITE postings from the job interface or a job feed
Kini reads an end customer's BITE postings in one of two ways: page by page through BITE's job posting interface, or from a BITE job feed the customer provides. Either way, Kini then fetches the full record of every posting from BITE, so each job arrives with title, description, address and links rather than as a bare list entry.
The work location address as entered in BITE
BITE asks for the complete work location address, which it needs for Google for Jobs and for its applicant map. Kini takes street, postcode, city, country and coordinates from every posting and uses BITE's job site as the location name. Countries are stored as two-letter ISO codes, and a feed job without any address is not imported.
Every language version as its own job
BITE lets employers publish postings for one vacancy in as many languages as they need. Kini imports each of those postings as a separate job and sets its language from the posting in BITE, stored as a two-letter language code. A German and an English version therefore reach your channels as distinct jobs and can be booked on their own.
Candidates apply in BITE itself
Each job Kini reads from BITE keeps two links: the posting and the application link BITE provides for it, which normally opens the posting's online application form. Candidates who follow that link apply in BITE, so the application is created in your customer's BITE account directly. Kini writes no candidate or application data into BITE.
Postings that go offline are archived
When a posting no longer comes back from BITE, Kini archives the job after that sync, takes its active campaign bookings offline and reports the change through its job update events. If the posting returns in a later sync, Kini reactivates the same job, and the campaign bookings taken offline go back through validation for republishing.
Employment type in Kini's standard values
BITE records a posting's employment type using values predefined by Google. Kini translates it into its own standard values for working time and, from job feeds, employment type: full-time, part-time, fixed-term and apprenticeship. In a feed, a title containing Ausbildung or Azubi also marks an apprenticeship. Unknown values stay empty and are recorded for mapping, with the original kept.
Every field. Every entity.Exactly where it belongs.
The integration covers two kinds of BITE data: the job posting and the address of its work location. Data flows one way, from BITE to Kini. Field names below follow the spelling of BITE's own API reference.
Job postings
Work location
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 BITE integration.
What Kini reads from BITE, how often it syncs, where candidates apply and what happens to a posting that goes offline.
Kini reads the job postings an end customer publishes in BITE: title, description, language, employment type and the work location with street, postcode, city, country and coordinates, plus the posting link and the application link. From a BITE job feed it also takes the contact person and keywords. Kini writes nothing back to BITE.
No. This integration does not write candidates or applications into BITE. Each job carries the application link BITE provides for the posting, and candidates who follow it apply in BITE, so the application is created in your customer's BITE account without passing through this integration. BITE remains where your customer reviews and manages applicants.
By default once an hour, on a schedule Kini sets for each company. A partner can also trigger a job sync on demand, at most once a minute per company, when a new or changed posting should not wait for the next run. Each sync updates the job Kini already holds for a posting instead of adding a second one.
In BITE, a posting is live only while it is set to Active and inside its validity period, and it leaves the career page when that period ends. Once a posting no longer comes back from BITE, Kini archives the job, takes its active campaign bookings offline and sends an archived event to partners subscribed to job updates.
BITE can hold postings for the same vacancy in any number of languages. Kini treats each of them as its own job and sets the job's language from BITE as a two-letter code, such as de or en. Channels and bookings therefore work with one language version at a time instead of a record that mixes languages.
The work location address stored on the posting in BITE: street, postcode, city and country, plus coordinates where BITE provides them. BITE's job site field becomes the location name, and the country is stored as a two-letter ISO code. When a job from a BITE job feed carries no address at all, Kini does not import it.
Yes. Where an end customer provides a BITE job feed, in XML or JSON, Kini reads the jobs listed in it and fetches each posting's full record from BITE. The feed adds the application link and the contact person's name and email, and supplies description and header image when the posting record lacks them.
No. Your customer keeps running recruiting in BITE: vacancies, postings and every applicant stay there. Kini only reads what BITE publishes, prepares it for job board bookings and follows it until the posting disappears. Applications go through the link BITE provides, and nothing in your customer's BITE account is changed by 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."
