Overview
Radancy integrations connect your Applicant Tracking System (ATS) with Radancy products to support job visibility, candidate applications, and data exchange across the Radancy platform.
Your ATS serves as the system of record for job requisitions, candidate data, and recruiting workflows. Radancy integrates with your ATS to retrieve and use this data while maintaining the ATS as the primary source of truth.
These integrations enable Radancy products to operate alongside your ATS and support a connected, consistent hiring experience.
Radancy integrations support multiple products, including:
- Career Sites
- CRM
- Screening & Scheduling
- Insights & Analytics
- Employee Referrals
- Programmatic AdTech
This article is intended for technical customer contacts who manage or oversee integrations in partnership with Radancy. It explains what Radancy integrations do, the types of data involved, and how integrations are typically implemented at a high level.
For a deeper technical explanation of how data flows between systems, see: Integration Architecture: Job vs. Candidate Data Flow
How Radancy Integrations Work
Radancy integrations support the exchange of job and candidate data between your ATS and Radancy products.
Depending on the product and configuration, integrations may:
- Retrieve job data from the ATS to power job visibility and distribution
- Retrieve candidate and application data from the ATS to support tracking, reporting, and recruiting workflows
- Support recruiting workflows such as screening, scheduling, and referrals
- Enable candidates to apply through Radancy‑hosted application experiences as part of the candidate journey
These integrations allow Radancy products to use ATS data without replacing the ATS as the system of record.
Integration Types
Radancy integrations are commonly grouped by the type of data they support.
Job Data Integration (ATS → Radancy)
Job data integrations provide job requisition data from your ATS to Radancy. This data powers job visibility and distribution across Radancy products.
Common integration approaches include:
- API‑based integrations
- Report‑based feeds
- XML or JSON data feeds
Typical job data includes:
- Job title and description
- Job ID or requisition number
- Location (city, state/province, country)
- Apply URL
- Job metadata (department, category, employment type, etc.)
Radancy products that rely on job data:
- Career Sites
- CRM
- Employee Referrals
- Screening & Scheduling
- Insights & Analytics
- Programmatic AdTech
Programmatic AdTech uses job data to distribute and advertise open roles across external channels.
Candidate & Application Data Integration
Candidate and application data integrations enable Radancy products to access and work with candidate and application information from your ATS.
Depending on the product, this may include:
- Synchronizing candidate and application data from the ATS
- Supporting candidate tracking and reporting
- Enabling workflows such as screening and interview scheduling
- Supporting referral tracking and attribution
- Enabling candidates to apply through Radancy‑hosted application experiences
Typical candidate and application data includes:
- Candidate contact information
- Resume and attachments
- Application responses
- Application status and updates
Radancy products that rely on candidate and application data:
- CRM
- Screening & Scheduling
- Insights & Analytics
- Employee Referrals
Integration Process Overview
Radancy integrations follow a structured implementation process designed to ensure accurate data flow, proper configuration, and successful delivery.
This section provides a high‑level overview of the process. Detailed tasks, timelines, and responsibilities are confirmed during implementation.
1. Project Kickoff & Alignment
- Define integration scope and requirements
- Align on timelines, stakeholders, and responsibilities
2. Requirements & Feasibility
- Validate ATS capabilities and integration approach
- Confirm required data structure and fields
- Identify dependencies or limitations
3. Access & Environment Setup
- Provide required credentials and system access
- Configure integration environments (testing and production)
4. Integration Build (Testing)
- Configure the integration in a test environment
- Establish data flow and mappings
5. Validation & Quality Assurance
- Validate data accuracy and formatting
- Resolve issues prior to customer testing
6. Customer Testing
- Review job data and application workflows
- Confirm requirements are met
7. Production Deployment
- Deploy the integration to production
- Perform final validation
8. Go‑Live
- Integration is activated in the production environment
- Job and/or application data is live and processing as expected
9. Post‑Go‑Live Stabilization
- Monitor performance and data accuracy
- Address any initial issues
Implementation Timeline
Implementation timelines vary based on integration complexity, ATS capabilities, and customer readiness.
Typical timelines:
- Job data integrations: 4–8 weeks
- Candidate and application integrations: 8–16 weeks
Actual timelines are confirmed during implementation planning.
Roles & Responsibilities
Customer Responsibilities
- Provide required credentials and system access
- Configure ATS components (reports, APIs, permissions)
- Ensure data is accurate and complete in the ATS
- Participate in testing and validation
- Communicate changes to ATS configuration that may impact integrations
Radancy Responsibilities
- Configure and implement the integration
- Apply data mappings and transformations
- Validate data flow and structure
- Support testing, troubleshooting, and go‑live
Monitor initial post‑launch performance
Data Ownership & Accuracy
Your ATS remains the source of truth for all job and candidate data.
Data provided by the ATS is used across Radancy products to support job visibility, candidate tracking, and reporting. To ensure optimal integration performance:
- Maintain accurate and complete data in your ATS
- Make updates at the source system whenever possible
Integration Frequency
Job data is refreshed regularly to support up‑to‑date job visibility.
Standard schedule:
- 4 imports per day (standard)
Refresh frequency may be configurable based on client requirements, ATS capabilities, and job volume.
Common Considerations
- Changes in ATS workflows, statuses, or permissions can impact integrations
- Data accuracy and completeness in the ATS directly affect integration quality
- Delays in access, configuration, or testing may impact implementation timelines
Next Steps
For more detailed information, refer to:
- Integration Architecture: Job vs. Candidate Data Flow
- ATS‑Specific Integration Guides