Jobs Integration: Overview & Data Requirements

Purpose

This article provides an overview of how job data integrations work between an Applicant Tracking System (ATS) and Radancy.
 
It is intended for technical customer contacts who manage or oversee job data integrations in partnership with Radancy. The goal is to explain how job data is retrieved from the ATS, how it is used across the Radancy platform, and what data is required to support job visibility and downstream functionality.
 
This article focuses on job‑level data and does not cover applicant or application data integrations.
 

Overview

Job integrations retrieve job requisition data from your ATS and make it available across the Radancy platform.

These integrations serve as the primary source of job data and support multiple Radancy products and features. Once retrieved, job data is:
  • Validated
  • Normalized
  • Distributed across Radancy products
Your ATS remains the system of record for job data.
 
How Job Data Is Used
 
Job data from the ATS supports the following Radancy products:
  • Career Sites
  • Programmatic AdTech
  • CRM
  • Screening & Scheduling
  • Employee Referrals
  • Hiring Events
  • Insights & Analytics
These products rely on structured job data for job display, candidate engagement, workflows, and reporting.
 
Integrations Architecture
 
Job data follows a one‑way flow:
ATS → Radancy
  • Job data is retrieved from the ATS
  • Data is processed and normalized
  • Jobs are distributed across the platform
Any changes to job data must be made in the ATS.
 
Supported Jobs Integration Types
 
General API Support Guidelines (Authentication dependent on ATS support)
Data Type: XML, JSON
Protocol/Authentication No Auth Basic Auth API Key OAuth 2.0
RSS

x

x

-

-

Web Services

-

x

x

-

SOAP

-

x

x

x

REST

-

x

x

x

*Required data fields must be available in API
Additional certificate support will require feasibility check with Radancy IT team.

Direct Feed Export

Data Type: XML, JSON
Protocol Type: SFTP
Security add-ons:

  • Support for PGP/GPG file encryption.
  • Support for SSH key.

It is recommended that Radancy creates/manages the SFTP location for the Customer/ATS to deliver files. Credentials will be provided during implementation. If instead the customer or a third party is to manage the SFTP, credentials must be provided to Radancy.

High Level Jobs Implementation Timeline

High Level Jobs Implementation Timeline    
Task Owner Date/Timeline

Kickoff call

  • Discovery and documentation exchange.
  • Define action items.
Customer/ATS/Radancy  - 
Provide API Credentials or XML job feed to Radancy Customer/ATS 5-10 business days

Validate access to API or receipt of XML job feed

  • Review required fields and data format
Radancy 5-10 business days

Create integration connectors and import test data

  • During implementation, Radancy will recommend optimizations to the test feed and/or data as necessary.
  • Display test jobs on staging preview site.
Radancy 5-10 business days

Customer UAT

  • Customer conducts testing on the staging preview site (full job posting appearance).
  • Customer to provide Radancy with feedback and revisions.
  • Repeat until customer approval is attained.
Customer/Radancy 5-10 business days

Go Live Ready

  • Customer and Radancy to coordinate migration of integration work from staging/preview to production environment in accordance with your career site launch.
Customer/Radancy  - 

*Timeline is subject to change based on implementation variables.

Job Data Requirements

Below is a list of required, recommended and optional fields. The customer/ATS must provide the fields and data in the format to be displayed on their career site. Please note that certain fields (not all are displayed on your career site) will be required/recommended to support your Radancy TAC platform (i.e. CRM, Employee Referrals, Hiring Events, Programmatic AdTech, etc.)

Field Description Required
Company Name Name of your organization Recommended
Company ID / Org ID If your ATS supports multiple instances Optional
Job Title Title of the job Yes
Job ID/Requisition Number Unique Identifier Yes
Job Category Category of job Yes
Job Description One or more fields containing all descriptive data including relevant HTML format. Include/define any separate Qualifications/Experience/Requirements/Company Profile, etc.) Yes

Primary Job Location:

  • City
  • State/Province
  • Country
  • Postal Code
Preferable in separate individual fields for city, state, country and postal code of the primary location Yes
Additional Locations

Option 1 – Single field separated by consistent unique identifiers, such as semi-colons and commas. (Preferred)
<additional locations>city, state, country; city, state, country; city, state, country</additional locations>

Option 2 – In separate fields for each additional city, state and country.
<additional locations>city,state,country</additional locations>
<additional locations1>city1,state1,country1</additional locations1>
<additional locations2>city1,state1,country1</additional locations2>

Recommended
Application URL ATS application URL Yes
Job Posting Date Date job was created in ATS Yes
Job Status Open/Closed/Filled Recommended
Job Shift 1/2/3/Evening/Weekend Recommended
Job Type Type of job; FT/PT/PD Recommended
Job Level Senior, Manager, Entry, etc. Recommended
Language Language requirements Recommended
Facility Name If multiple physical locations Recommended
Brand/Division/Department If multiple brand/division/department names Recommended
Business Unit If multiple business units Recommended
Salary Salary info; Min – Max Yes
Remote Status Yes/No – enhances candidate search experience on career site; a primary job location is still required Recommended
Job Profile Standardized job title templates. Optional
Recruiter Name Name of Primary Recruiter Recommended
Recruiter Email Email of Primary Recruiter. Required for CRM/Referrals Yes
Hiring Manager Email Email of Hiring Manager Optional
Sourcer Email Email of Sourcer Optional
Referral Reward Description of the reward to be earned for a successful hire Recommended
Referral Featured Job Yes/No Recommended
Custom Fields Customer to provide use case description Optional

Notes:

Referrals: If all correlated fields are included in the jobs feed integration, jobs are automatically published within the Employee Referrals dashboard (ready to refer). If any jobs are missing required data, they will instead be listed under “draft” status requiring manual intervention by the customer (recruiter) to complete. Once completed, the job can then be published and “enabled” to begin referring. If any data is not available from your ATS, it is possible for Radancy to apply conditional logic to streamline workflow processes.

  • Fields can be defaulted to a standard selected value (e.g., Reward plan is for all jobs “$500”)
  • Fields can be conditionally mapped based on other fields (e.g., if experience level is “Entry”, Reward plan is “$100”, if experience level is “Advanced”, Reward plan is “$500”)

Please contact your assigned Digital Project Manager or Integration Specialist.

Data Processing & Behavior

Job Lifecycle

Job visibility is controlled by the ATS:

  • Jobs appear when included in the job feed
  • Updates are reflected during refresh cycles
  • Jobs are removed when no longer included

Refresh Frequency

  • Job data is refreshed on a scheduled basis
  • Standard frequency is typically multiple times per day
  • Frequency may vary based on configuration

Example Job Feed Structure

All test job requisitions should reflect live job data and format. For testing purposes, it is recommended that there be sample size of at least five to ten jobs in the ATS feed during implementation.

Sample XML

<?xml version="1.0" encoding="utf-8" ?>
<source>
<job>
<title><![CDATA[Customer Success Representative]]></title>
<date><![CDATA[3/21/2020 12:15:03 AM]]></date>
<referencenumber><![CDATA[3958]]></referencenumber>
<apply_url><![CDATA[https://acmecareers-acme.ats.com/jobs/3958]]></apply_url>
<company><![CDATA[Acme]]></company>
<city><![CDATA[Glendale]]></city>
<state><![CDATA[California]]></state>
<country><![CDATA[United States]]></country>
<postalcode><![CDATA[91204]]></postalcode>
<additional locations><![CDATA[city, state, country; city, state, country; city, state, country]]>
</additional locations>
<description><![CDATA[<p style="margin: 0px;">Acme is transforming how companies connect with candidates through our SaaS talent acquisition platform. As a Customer Success Representative at Acme, you’ll work collaboratively to ensure the satisfaction and retention of our customers by providing exceptional customer service and support of our cloud-based platform. Interacting daily with your customers and teams, you’ll help execute data-driven strategies that fully maximize ROI across our Acme platform. Your elevated customer relations skills, resourcefulness, and ongoing eagerness to learn will drive success in this role. This entry level role is your gateway to many different career paths at Acme.</p><p style="margin: 0px;"> </p><p style="margin: 0px;">Studies have shown that women and people of color are less likely to apply for jobs unless they believe they meet every one of the qualifications in a job description. Our top priority is finding the best candidate for the job and if you are interested in the position, we would encourage you to apply, even if you don’t believe you meet every one of the qualifications below…</p>]]></description>
<jobtype><![CDATA[Regular Full-Time]]></jobtype>
<category><![CDATA[Customer Success]]></category>
<salary />
<education />
<industry />
<experience />
<remotetype />
</job>
</source>

If there are any questions regarding the job feed integration process or feasibility, please contact feeds@radancy.com

Key Considerations

  • Required fields must be consistently provided
  • Data structure impacts downstream functionality
  • Formatting inconsistencies may affect display
  • Missing data may limit product capabilities

Summary

Job data integrations provide the foundation for job visibility and platform functionality within Radancy. By ensuring structured, consistent data and supporting multiple integration methods, these integrations enable scalable job distribution, candidate engagement, and reporting across all products.

Was this article helpful?
0 out of 0 found this helpful