Integration Architecture Overview (How ATS Data Flows Through Radancy)

Purpose

This article provides a high-level technical overview of how Radancy integrates with an Applicant Tracking System (ATS).

It is intended for technical customer contacts who are responsible for managing or overseeing ATS integrations in partnership with Radancy. The goal is to explain how data flows between systems, how Radancy products rely on that data, and what integration approaches are commonly used.

This article covers:

• How job and candidate data flows from the ATS into Radancy
• How different Radancy products depend on these data streams
• The integration methods typically used to support this data exchange

This article does not include:

• ATS‑specific setup or configuration steps
• Field‑level mappings
• Product‑specific integration instructions

Those details are documented in ATS‑specific integration guides.

High‑Level Architecture Overview

Radancy integrations with an Applicant Tracking System (ATS) are structured around two core data streams:

• Job Data – What positions are open and available
• Candidate Data – Who applied and where they are in the hiring process

These data streams operate independently but are logically connected across the overall hiring lifecycle:

• Job data defines available opportunities
• Candidate data reflects applications and hiring progress
• Application activity connects candidates to job requisitions

The ATS remains the system of record for both job and candidate data. This means the ATS controls the authoritative version of this information, even when data is displayed, distributed, or used within Radancy products.

Architecture Diagram

The diagram below provides a visual representation of how job and candidate data flows from the ATS into Radancy, and how different Radancy products rely on these data streams.

You do not need to understand every component in this diagram to work with Radancy integrations. The diagram is provided to illustrate overall data flow at a conceptual level.

Diagram Explanation

The above diagram illustrates how Radancy integrates with an ATS through two primary data flows.

Job Data Flow (ATS → Radancy)

Job data flows from the ATS into Radancy and is used across the following products:

• Career Sites
• Programmatic AdTech
• CRM
• Screening & Scheduling
• Employee Referrals
• Insights & Analytics
• Hiring Events

This data powers job visibility, distribution, and product functionality across the Radancy platform.

Candidate Data Flow (ATS → Radancy)

Candidate and application data flows from the ATS into Radancy and supports:

• CRM (bi‑directional integration)
• Screening & Scheduling (bi‑directional integration)
• Insights & Analytics
• Employee Referrals

This data enables candidate tracking, reporting, and recruiting workflows. While job and candidate data flows operate independently, they are connected through application activity, which links candidates to specific job requisitions.

Job Data Integration Methods

Job data integrations are responsible for delivering job requisition data from the ATS into Radancy.

The specific integration method used is determined during implementation based on:

• ATS capabilities
• Security requirements
• Supported Radancy connectors

Support teams cannot change integration methods without an implementation review.

Commonly Supported Integration Methods

Data Formats: XML, JSON

Required job data fields must be available through the selected integration method. Additional security or certificate requirements may apply depending on the ATS and customer configuration.

File‑Based Integration (Direct Feed Export)

In addition to API‑based integrations, job data may be delivered via secure file transfer.

• Data Formats: XML, JSON
• Transport Method: SFTP

Supported security options may include:

• PGP/GPG encryption
• SSH key authentication

File‑based integrations are typically configured during implementation and are not adjusted through standard support requests. Configuration ownership may vary depending on the engagement.

Candidate & Application Data Integration Methods

Candidate and application data integrations provide applicant-level data from the ATS to Radancy products.

This data supports downstream functionality such as CRM, Referrals, reporting, and analytics.

Candidate & Application Data Integration Methods

Candidate and application data integrations provide applicant‑level data from the ATS to Radancy products. This data supports downstream functionality such as CRM, referrals, reporting, and analytics.

Commonly Supported Integration Methods

Data Formats: XML, JSON

Candidate data availability (including status, disposition, or stage data) depends on the ATS data model and the specific integration configuration.

File-Based Integration (Direct Feed Export)

Where API‑based integrations are not supported, candidate data may be delivered via secure file transfer.

• Data Formats: XML, JSON
• Transport Method: SFTP

As with job data, file‑based candidate integrations are typically established during implementation.

Application Submission & Workflow Interactions

In addition to data retrieval, some integrations support interactions with the ATS.

Supported actions may include:

• Submitting job applications
• Updating application stages or statuses
• Supporting workflow‑related actions

How this typically works:

• Candidates apply through Radancy‑hosted application experiences
• Application data is sent to the ATS
• The ATS processes and stores application data
• Workflow updates may be reflected between systems depending on configuration

Not all integrations support all actions listed above. Supported interactions depend on the ATS and the specific integration design.

Advanced Architecture Diagram

The diagram below provides a more detailed view of integration workflows, including bidirectional interactions and product‑level data flows.

This diagram is provided for reference and may be most useful for technical stakeholders involved in integration planning or troubleshooting.

Data Flow Relationships

Radancy integrations are built on two independent but connected data streams:

• Job Data Flow – Drives job visibility and distribution
• Candidate Data Flow – Supports candidate tracking and workflows

These streams are connected through application activity, which links candidates to job requisitions within the ATS.

Key Technical Considerations

• Integration methods depend on ATS capabilities and configuration
• Data must be provided in XML or JSON format
• Secure transport methods (API or SFTP) are required
• Authentication methods vary by ATS
• Not all integration methods are supported by every ATS

Summary

Radancy integrations are designed to support flexible, scalable data exchange between an ATS and Radancy products.

By separating job data and candidate data into independent but connected streams, the platform supports job visibility, candidate tracking, reporting, and recruiting workflows across the Radancy ecosystem—while maintaining the ATS as the system of record.