How teams actually use Kini with d.vinci.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with d.vinci. Five scenarios where the managed integration makes the biggest difference.
Your customer connects d.vinci themselves, in one click
You generate a Magic Link and send it to your end customer. They enter their d.vinci API credentials themselves. You never touch access data, your team never touches applicant data.
Fields map themselves, the rest with one click
d.vinci's screening questions, form fields and locations 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
Applications run through Kini straight into your customer's d.vinci account, with attachments and screening-question answers in place. No intermediate storage, no forwarding, no liability on your side.
One d.vinci account, 1,500+ job boards
Once connected, you choose from 1,500+ job boards, including Stepstone and Indeed, to promote d.vinci job publications, and applications come back the same way. One connected account, no second integration project.
Every field. Every entity.Exactly where it belongs.
Kini reads job publications from d.vinci, including location, category, target group and salary range, and submits applications with attachments and screening-question answers. Application status is tracked back through the same API.
Job Publications
Applications
Application Status
d.vinci authenticates API access through dedicated Dvinci-API-User and Dvinci-API-Token headers, issued by the customer's own d.vinci admin. Reading public job publications requires no credentials at all.
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 d.vinci API credentials to production go-live.
Kini connects to d.vinci via Magic Link and the customer's own API credentials. 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 d.vinci API credentials themselves, issued by their own d.vinci admin. You never see or store them.
Step 2Map
Kini auto-detects and pre-maps d.vinci's screening questions, form fields and locations between d.vinci 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 sync, mapping and screening before anything goes live.
Step 4Go-live!
Applications flow through Kini directly into the customer's d.vinci account, which stays the system of record. Kini operates and monitors the connection.
with your stack?
What makes Kini different for d.vinci 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 d.vinci integration.
Everything about how Kini connects to d.vinci. From setup and authentication to data sync and GDPR compliance.
Job publications are read through d.vinci's official Job Publication API, including location, category, target group and salary range, and applications are submitted through the Application Apply API with attachments and screening-question answers. Application status is tracked back through the same API.
Your customer enters their d.vinci API credentials via the Magic Link, issued by their own d.vinci admin, so you never see or store them. Reading public job publications requires no credentials at all.
No. d.vinci stays your system of record. Kini is the connectivity layer around it: job publications and applications are synced between d.vinci and your connected recruiting channels through one API, so you extend what d.vinci already does without replacing it.
No. The d.vinci integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they enter their own d.vinci API credentials, and Kini handles mapping, operation and monitoring as a managed service.
It is built for GDPR-compliant use. Data that passes between d.vinci 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."
