Purpose
This article provides a foundational overview of Radancy’s Core Applicant ATS Integration model.
It is intended for technical customer contacts who manage or oversee applicant data integrations between their Applicant Tracking System (ATS) and Radancy products. The goal is to establish a clear, shared understanding of what a core applicant integration includes, what may vary by ATS, and which capabilities are optional.
This article focuses specifically on applicant (candidate and application) data, not job feed integrations.
What Is a Core Applicant ATS Integration?
A Core Applicant ATS integration enables Radancy products to exchange applicant and application data with a customer’s ATS in a standardized and scalable way.
At a minimum, a core applicant integration supports:
- Pulling applicant records from the ATS into Radancy CRM
- Associating applicants with jobs and requisitions using ATS‑provided identifiers
Depending on ATS capabilities and configuration, some integrations may also support limited bi‑directional updates.
Integration Capabilities
Core Applicant ATS integrations are best understood by grouping capabilities into three categories.
1. Always Included
These capabilities are part of every core applicant integration:
- Importing applicants from the ATS into Radancy CRM
- Associating applicants to jobs and requisitions using ATS identifiers
2. ATS‑Dependent
These capabilities vary based on the ATS and its data model:
- Availability and frequency of applicant status updates
- Access to custom fields, disposition reasons, or recruiter‑defined values
- Near real‑time updates versus scheduled or batch delivery
3. Optional
These capabilities may be implemented when supported and required:
- Pushing candidate status updates from Radancy CRM back into the ATS (bi‑directional integration)
- Custom field mappings beyond standard applicant and requisition data
- Non‑standard data flows tied to customer‑specific workflows
Design Principles
Core Applicant ATS integrations are designed to be:
- Consistent across customers and ATS platforms
- Scalable as hiring volume increases
- Flexible enough to support differences in ATS capabilities and data delivery methods
Relationship to Job Feed Integrations
Applicant integrations depend on job data, but they are not the same as job feed integrations.
Key distinctions:
- Job feed integrations publish open positions
- Applicant integrations track candidate activity and application progress against those jobs
Both integrations work together but serve different purposes.