Event
Meet us in London on 8 October

One connection on your side. Any system on the other.

Kini is the managed connectivity layer between ATS, agencies and job boards. You connect once, we take over monitoring and maintenance.

Workspace
Every customer in one place
Connections
Any ATS, any path
Operating layer
Monitored and recovered
Why it breaks
Every system speaks its own language.
One ATS has a modern API, the next only exports XML, a niche job board sends applications by email. A unified API only covers the ones that speak REST.
Kini Core
Kini Core connects 65+ ATS and the job boards behind them through one managed layer. You connect once. We run what sits behind it.
See Kini Core
Integrations break quietly.
A field gets renamed or a token expires, and applications stop arriving. Nobody notices until a customer opens their account to zero jobs.
Operating layer
The operating layer is the work after go-live: watching the data, recovering from failures, telling you what happened. It runs under every Kini Core integration.
See Operating layer
Recruiting data is messy.
Custom fields, free-text locations and broken markup from every source. Somebody has to clean it up.
Data processing
Kini maps, cleans and checks each record in the background. Your team does not configure fields, and nobody cleans up after the sync.
See Data processing
Every new integration hits your roadmap.
Your customers keep asking for integrations you don't have yet. Each one needs engineers most teams can't spare, and every later change costs time again.
Multi-customer workspace
Create customers, store credentials securely and manage each integration under one operator account. No customer-side engineering required.
See Multi-customer workspace
Job boards are moving to performance pricing.
Postings that ran for 30 days give way to cost per click and cost per application. That only works when applications flow back into the ATS reliably.
Kini Shop
Kini Shop turns a fragmented board landscape into one channel, without negotiating a contract board by board. It builds on Kini Core and can run on its own.
See Kini Shop
Definition

What is managed recruiting connectivity?

Managed recruiting connectivity is an integration layer between ATS systems, recruiting agencies, and job boards. Unlike a unified API, it does not require the source system to speak REST: Kini adapts to whatever each system offers, while the partner keeps a single connection. It includes monitoring, recovery, and per-record sync status.

In practice: a Kini integration is shipped, monitored, and recovered by the same platform that built it. The integration is not a project. It's a running service with an owner.

Product overview

Kini Shop builds on Kini Core, and both run on the same operating layer. Use them together or either on its own.

Kini Core

One layer between ATS, agencies and job boards.

Kini Core connects 65+ ATS and the job boards behind them through one managed layer. You connect once. We run what sits behind it.

Layer stack with the source systems layer highlighted at the bottom
Source systems
65+ ATS and 1,500+ job boards. However a system can be reached. The list stays open.
Layer stack with the connection paths layer highlighted
Connection paths
API, feeds, email, crawler or custom. Kini adapts to whatever each system can do.
Layer stack with Kini Core highlighted in the middle
Kini Core
Everything arrives here. Mapped, normalized and monitored before it reaches you.
Layer stack with the operating layer highlighted
Operating layer
Monitoring, recovery and a team behind it. It runs under every Kini Core integration.
Layer stack with your platform highlighted at the top
Your platform
Exactly one connection, in the format that fits your stack. One API key per partner.
Connection paths

However a system can be reached.

API, feeds, email, crawler or custom. The list stays open: when a system needs a new path, we add one. Your side stays one connection.

Source · Modern ATS
GET /jobs/4711
{
  "title": "Project Manager",
  "city": "Hamburg"
}
Delivered to your platform
Project Manager (m/f/d)
Vektra Engineering · Hamburg
One format
Source · Personio · XML
<job>
  <title>Project Manager</title>
  <office>Hamburg</office>
</job>
Delivered to your platform
Project Manager (m/f/d)
Vektra Engineering · Hamburg
One format
Source · Niche platforms
From StepStone
Subject New application
Job Project Manager
Delivered to your platform
Anna M.
Application · Project Manager
One format
Source · Career pages
vektra.example/careers
Project Manager · Hamburg
Service Technician · Berlin
Delivered to your platform
Project Manager (m/f/d)
Vektra Engineering · Hamburg
One format
Source · Non-standard data
stellen_titel: "Filialleitung"
ort_name: "HH"
Delivered to your platform
Project Manager (m/f/d)
Vektra Engineering · Hamburg
One format
Source · No interface
No interface. Kini AI reads the job from what is there.
Delivered to your platform
Project Manager (m/f/d)
Vektra Engineering · Hamburg
One format
Operating layer

Broken data stays out.

If a source delivers empty or wrong data, Kini does not pass it on.

From the source
24
Live jobs
24
Jobs sync as usual
From the source
0
Live jobs
24
Held back
Live jobs unchanged
Reset
Send an empty list
Recovery

When retries fail, a person looks.

Retries first, then a replacement path. If that fails too, our team takes over.

Delivery failed
Retrying with backoff
Switching to a replacement path
Kini team is on it
Workspace

Sync status per record, per customer.

One operator account for all your end customers: their credentials, mappings and sync status in one place, white-label on your own domain.

One operator account for all your end customers

Credentials and mappings kept per customer

White-label on your own domain

portal.youragency.com

Open a customer

Application
Anna M.
Synced
Job
Project Manager (m/f/d)
Synced
Application
Lena H.
Synced

Sync status per record

Job import
Empty list from source
Held back
Application
Jonas W.
Synced
Job
Consultant (m/f/d)
Synced

Sync status per record

Application
Paul N.
Retrying
Job
Cook (m/f/d)
Synced
Application
Mia F.
Synced

Sync status per record

Application
Hannah K.
Synced
Job
Night Nurse (m/f/d)
Synced
Application
Felix B.
Synced

Sync status per record

Security

Built in Europe. GDPR-first.

Data processing on EU servers. Applicant data is deleted or anonymised after 180 days.

EU servers
GDPR-first
Applicant record
Stored in the EU
Stored in the EU
Deleted or anonymised
Kini Shop

Core and Shop, one system.

Kini Shop builds on Kini Core. Choose from 1,500+ job boards and promote jobs with one click or as a campaign. Both run on the same operating layer.

One click
Store Manager (m/f/d)
1 job from Personio
0
job boards live
1,500+
job boards live
Reset
Promote with one click
Campaign
3
Q4 hiring
3 jobs from Personio
Draft
0%
0%
Running
64%
41%
Reset
Start campaign
Onboarding

Live in minutes once we have the credentials.

Your customer gets a Magic Link with a guide for creating credentials in their ATS. If someone gets stuck, we join the call.

Your Agency via Magic Link
to Vektra Engineering
Guide included
Replay

Connect your ATS so your jobs and applications sync. A step-by-step guide shows you how to create the credentials.

Connect your ATS
Personio connected
First jobs syncing
Deep dive

Five parts make up the platform. Each one is operated by us, and all of them run on the same layer.

Kini Core
API
Feeds
Email parsing
Crawler
Kini AI
Webhooks
Data processing
Advanced data mapping
HTML sanitization
Duplicate handling
Multi-customer workspace
Magic Link
White-label
Operating layer
Anomaly detection
Recovery in two stages
Real errors only
Sync status per record
GDPR-first
Kini Shop
Premium job ads
Campaign management
ATS job import
Quick Apply
Your existing contracts
Kini Core

A unified API only works if the other system speaks REST. Kini Core doesn't need it to. We adapt to whatever each system can do, and you keep a single connection on your side.

Source systems · our job

However a system can be reached. The list stays open.

API

Documented APIs, where a system offers them.

Feeds

Structured XML or JSON feeds. XML is how Personio exchanges jobs, for example.

Email parsing

Applications arrive at dedicated inboxes, sorted by job board, and Kini turns them into structured records.

Crawler

Where there is no API or feed, Kini crawls the published jobs from the career page.

Custom

Mappings and field transformations for systems that don't fit a standard.

Kini AI

When a system offers no interface at all, Kini AI does the adapting.

Next path
New systems get a new path, not a new project for you.
Kini
Kini Core

Everything arrives here. Mapped, normalized and monitored before it reaches you.

Your platform

API

One REST integration. Jobs out, applications in.

Feed

One structured XML or JSON feed, if that fits your stack better than an API.

Webhooks

Add webhooks to get events pushed to your endpoint: job updates, application sync status and booking status.

Operating layer

The operating layer is the work after go-live: watching the data, recovering from failures, telling you what happened. It runs under every Kini Core integration.

Job import
Vektra Engineering · ATS
Empty list

Source returned an empty job list

Held back
Live jobs
Unchanged
Project Manager
Live
Service Technician
Live
Electrical Engineer
Live

Broken data stays out

If a source delivers empty or wrong data, Kini does not pass it on. Your customers don't open their account to zero jobs because something upstream broke.

Empty or wrong data is held back

Live jobs stay unchanged

No accounts with zero jobs

Sync volume
Brandt & Partner · ATS
Live in production
Flagged
Sync volume dropped
Flagged
Failed syncs above normal

Anomaly detection

Unusual sync volumes and failed syncs get flagged while they happen. Anomaly detection runs live in production.

Unusual sync volumes get flagged

Failed syncs flagged as they happen

Runs live in production

Application
AI Engineer (m/f/d)
Delivery failed
Retrying with backoff
Delivered via replacement path
Sync status
SUCCESS_FALLBACK

Recovery in two stages

First, retries with backoff. If the primary path fails for good, Kini delivers another way, for example through Kini AI. Each application shows its sync status.

Retries with backoff

Delivery over a replacement path

Sync status for each application

Lindhoff Hotels
softgarden
FAILURE
Re-sync customer
or
Escalated
Kini team
Kini team is on it
Mapping adjusted
Resync started

A person looks at it

Escalation to a human is part of the service, not an exception. You can handle things yourself, and our team steps in when you need it.

Escalation is part of the service

Handle things yourself if you like

Our team steps in when you need it

Alerts
Webhook
Email
Real errors only
FAILURE · ATS unreachable
Sent
EXPECTED_FAILURE
Filtered

Alerts that mean something

A defined catalog of events, delivered by webhook or email and set per partner and end customer. A closed position is not a broken sync, so you can subscribe to real errors only.

Delivered by webhook or email

Set per partner and end customer

Subscribe to real errors only

Kini dashboard
Sync cadence per customer
Mertens Pflege
Synced
Lindhoff Hotels
Failure
Re-sync
Brandt & Partner
Synced
Your product
via webhook
End customers
email and dashboard

Status for every side

Partners get status updates by webhook and can show them in their own product. End customers see it by email and in the dashboard. Sync cadence is set per customer.

Webhook updates for partners

Email and dashboard for end customers

Sync cadence set per customer

Note: notification emails come from Kini, not from your brand.

Reliability isn't a feature. It's the platform. And when the platform can't fix it, a person does.

Data processing

Kini maps, cleans and checks each record in the background. Your team does not configure fields, and nobody cleans up after the sync.

Field mapping with fallback

Kini maps custom fields, translates values like employment types, normalizes locations and sources, and carries screening questions across. Nothing is silently dropped.

Source
ATS
employment_type
"Vollzeit"
FULL_TIME
location
"Frankfurt a. M."
Frankfurt am Main, DE
screening_questions
3 questions
carried across

Clean HTML, normalized data

Job descriptions get sanitized HTML. Candidate data gets normalized. The ATS receives data it can actually use, not markup debris.

Job description
Sanitized
−<p style="font:Arial"><br><br>Your tasks:</p>
+<h3>Your tasks</h3><ul>…</ul>
Phone number
Normalized
−+49 (0)171-…
++49171…

Duplicates handled

When the ATS already knows the candidate, Kini marks the application as an expected failure, not a broken sync. Nobody on your side has to chase it.

Anna M.
via StepStone
SUCCESS
Anna M.
via Indeed
EXPECTED_FAILURE
DuplicateApplicationError
No action needed

Gaps filled with a fallback

Missing values are filled from other data or a set default, so an incomplete application still arrives complete enough to process.

Application
first_name
Anna
email
anna.m@example.com
phone
not provided
Fallback
Status
Ready to process
Multi-customer workspace

Agencies, job boards and ATS providers serve many end customers, each with their own systems, credentials, mappings and quirks. Kini keeps them apart, and in one place.

portal.youragency.com
White-label
Customers
Vektra Engineering
Personio
Brandt & Partner
JOIN
Nordwind Logistik
softgarden
Lindhoff Hotels
Recruitee
Mertens Pflege
Custom ATS
Add customer
Vektra Engineering
Connected via Personio
Live
Credentials
Stored securely
Mapping
Managed by Kini
Last sync
just now
Brandt & Partner
Connected via JOIN
Live
Credentials
Stored securely
Mapping
Managed by Kini
Last sync
1 min ago
Nordwind Logistik
Connected via softgarden
Live
Credentials
Stored securely
Mapping
Managed by Kini
Last sync
2 min ago
Lindhoff Hotels
Connected via Recruitee
Live
Credentials
Stored securely
Mapping
Managed by Kini
Last sync
4 min ago
Mertens Pflege
Connected via Custom ATS
Live
Credentials
Stored securely
Mapping
Managed by Kini
Last sync
just now
Magic Link sent, guide included

For agencies, job boards and ATS providers

Create customers, store credentials securely and manage each integration under one operator account. No customer-side engineering required.

Under your brand, not ours

The workspace and the shop run white-label: your own custom domain, your own branding. Your customers see your product. Kini is the layer underneath.

For end customers

Secure onboarding via Magic Link: customers pick their system and enter credentials. No shared spreadsheets, and if a customer would rather be walked through it, someone will.

You decide who talks to the end customer

Kini can stay entirely in the background, or step forward and handle onboarding and support conversations directly with your customer. Your call, per partner.

Kini Shop

Kini Shop turns a fragmented board landscape into one channel, without negotiating a contract board by board. It builds on Kini Core and can run on its own.

Premium job ads

Choose from 1,500+ job boards and promote a single job with one click.

Premium job ad
Imported from Personio
AI Engineer (m/f/d)
Vektra Engineering · Munich
and 1,500+ more job boards

Campaign management

Run several jobs as a campaign on the platforms that matter, such as Indeed or Kleinanzeigen.

Campaign · Q4 hiring
Running
AI Engineer (m/f/d)
Munich
Project Manager (m/f/d)
Hamburg
Warehouse Associate (m/f/d)
Leipzig
Live
Live

White-label on your domain

The shop runs under your brand, on your own custom domain.

ATS job import

Jobs come straight out of the connected ATS. No re-entering, no second job list.

Public and classifieds channels

Publish to the Bundesagentur für Arbeit and to Kleinanzeigen alongside the classic job boards.

Your existing contracts

If your customer already has contracts with boards, Kini publishes through them. They keep their rates.

Quick Apply

A short application straight from the posting, with fewer steps between seeing the job and applying.

An in-house agency behind it

Advice and support come from people who run these campaigns themselves.

Onboarding

Every connection starts with credentials and ends with a live sync. You choose per customer how they get there, and Kini operates the connection either way.

What every onboarding takes

Each connection runs through two phases. The first one depends on your customer, the second one is on us.

Phase 1

Getting the credentials

Your customer creates credentials in their ATS. This is the part that takes time, and the part Kini guides them through with a guide in every Magic Link.

Phase 2

The technical connection

Once we have the credentials, it's minutes. Not weeks.

Two ways to get there

Send a Magic Link and let your customer connect, or set the integration up yourself in the Kini workspace.

Magic Link

You operate. Kini delivers.

You send your customer a Magic Link. They select their ATS or job board and enter credentials. Kini handles mapping, validation and the first sync.

Send
Customer connects
Live
Self-setup

You build. Kini connects.

Your team picks the integration and configures it in the Kini workspace. For technical pilots, partner setups or edge cases that need custom mappings.

Configure
Test
Live

If a customer gets stuck, Kini can bring technical support straight into the call, so the problem gets solved while everyone is still on it.

Integrations
65+
ATS
1,500+
job boards via Kini Shop
1
connection on your side
ATS
Personio
Recruitee
JOIN
Greenhouse
softgarden
SAP SuccessFactors
Job boards and channels
StepStone
Indeed
LinkedIn
XING
Kleinanzeigen
Bundesagentur für Arbeit
See all integrations
See all integrations

Your integrations.Managed by us.Live in minutes.

Syncs
Jobs
Cleaner
Out
→
Flows
Applications
Faster
In

No engineering backlog. No manual data handling. Just a working connection between your tools.

Team memberTeam member
Book a demo
Book a demo
Personio Logo
SAP SuccessFactors Logo
Workday Logo
Greenhouse Logo
softgarden Logo
d.vinci Logo
StepStone Logo
Indeed Logo
LinkedIn Logo
XING Logo
Bundesagentur für Arbeit Logo
Jobware Logo
1
Select ATS
2
Enter ATS credentials
3
Go live
Fast go-live
FAQ
What's the difference between Kini Core and Kini Shop?

Kini Core is the integration engine. It connects ATS systems, recruiting agencies and job boards, adapting to whatever each source system can do while you keep a single connection on your side, and adds an operating layer with monitoring and recovery. Kini Shop is the distribution layer that turns 1,500+ job boards into one channel. Shop usually builds on Core, and either can be used on its own.

How does Kini connect to a system?

In two directions. On the source side, Kini adapts to whatever a system offers: APIs, email parsing, crawling, structured feeds, custom mappings, or Kini AI where there is no interface at all. That list is open-ended. On your side, you build exactly one connection, an API, a feed or webhooks, with one API key per partner.

How is Kini different from a unified API?

A unified API gives you one REST endpoint across systems, but it only works where the source system speaks REST. If a system has no API, it isn't covered. Kini gives you the same single connection on your side and adapts to the source system, whatever it offers. On top of that come the operating layer with anomaly detection, automatic recovery and human escalation, the multi-customer workspace, and job board distribution through Kini Shop.

What is the multi-customer workspace?

It's how agencies, job boards and ATS providers serve their end customers from one Kini account. Each end customer has their own credentials, mappings and sync status, managed by the operator and white-label under the operator's own brand and domain. End customers connect their systems via Magic Link without engineering effort on their side.

How long does it take to get a first integration live?

Once Kini has the credentials, a first integration goes live in minutes, not weeks. What takes time is the step before: your customer has to create credentials in their ATS. The Magic Link includes a guide for exactly that, and Kini keeps those guides up to date. If they get stuck, Kini can join the call.