How teams actually use Kini with Talent360.
From multi-client agencies to in-house recruiting teams: Kini fits the way you work with Talent360. Five scenarios where the managed integration makes the biggest difference.
Your customer connects Talent360 themselves, in one click
You generate a Magic Link and send it to your end customer. They enter their Talent360 API credentials themselves, issued in their own settings. You never touch access data, your team never touches applicant data.
Fields map themselves, the rest with one click
Talent360's fields and fixed catalogs, such as languages, driver's licenses and professions, are mapped between talent.Flow and your connected channels. You fix any mismatches from a dropdown. No code, no engineer.
You never touch applicant data
Applications run through Kini straight into your customer's Talent360 account via the external-applies endpoint, with candidate data, consent and documents in place. No intermediate storage, no liability on your side.
Every field. Every entity.Exactly where it belongs.
Kini syncs job ads, candidates, applications, documents and staffing objects between talent.Flow and your connected channels via the talent.Flow REST API, using its change-feed endpoints for incremental sync. No intermediate storage, no manual exports, no data sitting in between.
Job Ads
Candidates
Applications
Documents
Talent360's REST API requires the Professional license tier. Documents transfer base64-encoded, and outbound webhooks push near-real-time change events for candidates, job ads, documents and customers.
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 talent.Flow API credentials to production go-live.
Kini connects to Talent360 via Magic Link and API credentials. Fields are mapped, the connection is tested and your integration is live.
Step 1Connect
Your customer receives a Magic Link from Kini and enters their Talent360 API credentials themselves, issued in their own Talent360 settings from the Professional license tier onward. You never see or store them.
Step 2Map
Kini maps Talent360's fields and fixed catalogs, such as languages, driver's licenses and professions, between talent.Flow and your connected channels. No manual configuration needed on your side.
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!
Applications and candidate updates flow through Kini directly into the customer's Talent360 account, which stays the system of record. Change feeds and webhooks keep everything current.
with your stack?
What makes Kini different for Talent360 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 Talent360 integration.
Everything about how Kini connects to Talent360. From setup and authentication to data sync and GDPR compliance.
Jobs as job ads, candidates, applications, documents, customers, offices and users. Talent360's API also supports staffing-specific objects such as customer contacts and staffing requests, so the connection covers recruiting and staffing data in one place.
Talent360 exposes change-feed endpoints per day, per day and hour, and per date range for candidates, documents, job ads and customers, suited to incremental sync. Outbound webhooks add near-real-time event notifications on top of the feeds.
No. talent.Flow is Talent360's core ATS system, covered by this integration. talent.Reach is a related candidate-facing product, and bewerbung.jobs is Talent360's own public job board where Active job ads are published.
No. The Talent360 integration is pre-built, so there is no development project on your side. You send your customer a Magic Link, they enter their own API credentials, and Kini handles mapping and operation. Note that Talent360's REST API requires the Professional license tier to activate.
No. Talent360 (talent.Flow) stays your system of record. Kini is the connectivity layer around it: job ads, candidates, applications and documents are synced between talent.Flow and your connected recruiting channels through one API, so you extend what Talent360 already does without replacing it.
It is built for GDPR-compliant use. Data that passes between Talent360 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."
