How teams actually use Kini with Cockpit.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with Cockpit. Four scenarios where the managed integration makes the biggest difference.
Your customer connects Cockpit themselves, in one click
You generate a Magic Link and send it to your end customer. They enter their Cockpit API key themselves. You never touch access data, your team never touches applicant data.
Fields map themselves, the rest with one click
Cockpit's matchfields, workflow statuses and metadata fields are auto-detected and pre-mapped. You fix any mismatches from a dropdown. No code, no engineer, no development ticket.
You never touch applicant data
Candidate data runs through Kini straight into your customer's Cockpit account. No intermediate storage, no forwarding, no liability on your side. Multi-department agencies stay cleanly separated per tenant.
Every field. Every entity.Exactly where it belongs.
Kini syncs data between Cockpit and your connected channels via the RecruitNow PublicAPI v2, which exposes resources such as Companies, Candidates and Departments. No intermediate storage, no manual exports, no data sitting in between.
Companies
Departments
Candidates
RecruitNow's PublicAPI v1 is scheduled for deprecation as of Release 59 (15 July 2026). Integrations target PublicAPI v2, authenticated with an X-Api-Key header and, for multi-department agencies, an X-Tenant-Id header.
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.
From Cockpit API key to production go-live.
Kini connects to Cockpit via Magic Link and an API key. Fields are mapped automatically, the connection is tested and your integration is live.
Step 1Connect
Your customer receives a Magic Link from Kini and enters their Cockpit API key themselves, plus a tenant ID for multi-department agencies. You never see or store the credential.
Step 2Map
Kini auto-detects and pre-maps Cockpit's fields, matchfields and workflow statuses between Cockpit and your connected channels. No manual configuration needed.
Step 3Test
A test job and a test candidate run automatically through the full flow. Kini checks field mapping and sync behaviour before anything goes live.
Step 4Go-live!
Data flows through Kini directly into the customer's Cockpit account, which stays the system of record. Kini operates and monitors the connection.
with your stack?
What makes Kini different for Cockpit customers.
Other tools connect. Kini manages. In practice that covers GDPR, field mapping, job board compatibility and everything that breaks when nobody is watching.
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 Cockpit integration.
Everything about how Kini connects to Cockpit. From setup and authentication to data sync and GDPR compliance.
Cockpit is connected with an API key, and multi-department agencies additionally provide a tenant ID. Both are entered by your customer via the Magic Link, so you never see or store the credential. The PublicAPI v2 authorizes calls through the X-Api-Key header.
RecruitNow announced that PublicAPI v1 is deprecated as of Release 59 (15 July 2026). Integrations should use PublicAPI v2.
No. Cockpit stays your system of record. Kini is the connectivity layer around it: vacancies and candidate data are synced between Cockpit and your connected recruiting channels through one API, so you extend what Cockpit already does without replacing it.
No. The Cockpit integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they enter their own Cockpit API key, and Kini handles mapping, operation and monitoring as a managed service.
It is built for GDPR-compliant use. Data that passes between Cockpit and your connected channels is processed by Kini in Frankfurt, Germany, under a data processing agreement (DPA). Kini deletes or anonymizes personal applicant data 180 days after an application is created.
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."
