Purpose & Scope
This document describes the integration architecture and data exchange requirements for integrations between Workday Recruiting (ATS) and the Radancy Talent Acquisition Cloud (TAC).
It consolidates integration requirements across multiple Radancy products and is organized around Job (Requisition) data and Applicant (Candidate/Application) data integrations.
The integrations described in this document support the following Radancy products:
- Career Sites
- CRM (including bi-directional components)
- Screening & Scheduling (S&S)
- Insights & Analytics (I&A)
- Hosted Apply
- Employee Referrals
- Programmatic AdTech
Workday typically serves as the system of record for requisitions, candidate applications, and recruiting workflow data.
Data exchange is primarily enabled through Workday RaaS (Report-as-a-Service) for data retrieval and Workday Web Services (SOAP APIs) for transactional operations
Integration Architecture Overview
Radancy integrations with Workday use a combination of data extraction mechanisms and transactional APIs to exchange recruiting data between systems.
Primary Integration Mechanisms
| Integration Method | Purpose |
| Workday RaaS (Report-as-a-Service) | Extract job requisition and applicant data |
| Workday Web Services (SOAP APIs) | Perform transactional operations in Workday |
Workday RaaS
RaaS reports expose Workday data as XML web service endpoints that can be consumed by Radancy import services.
These reports are typically used for:
- Job requisition synchronization
- Applicant and application data synchronization
- Supporting reference data required for integrations
Radancy consumes custom Advanced RaaS reports built on Workday recruiting business objects such as Job Requisition and Job Application.
Workday Web Services (SOAP APIs)
Workday Web Services are used when Radancy must perform actions within Workday as part of the recruiting workflow, such as:
- Submitting job applications
- Updating application stages
- Moving candidates through recruiting pipelines
- Adding recruiter notes or comments
Authentication
Radancy integrations with Workday authenticate using a dedicated Integration System User (ISU) configured within the customer’s Workday tenant.
Authentication uses WS-Security UsernameToken with ISU credentials when accessing Workday integration endpoints.
The ISU must be assigned to an Integration System Security Group (ISSG) with the domain permissions required to access recruiting data, custom reports, and Workday Web Services APIs.
Authentication is used for:
- Accessing Workday RaaS (Report-as-a-Service) reports used for job and applicant data extraction
- Accessing Workday Web Services (SOAP APIs) used for transactional operations
Environment Setup
Customers are expected to support integration testing and validation prior to enabling integrations in production.
Workday integrations are generally implemented using separate environments:
- Sandbox / Implementation tenant – used for integration configuration, testing, and validation
- Production tenant – used for live integrations
Where both environments are available, integration configurations (such as RaaS reports and required security permissions) should be deployed consistently across environments.
Customer Responsibilities (Workday)
For all Radancy integrations with Workday, the customer is responsible for configuring and maintaining the required integration components within their Workday tenant.
This includes:
- Designing and maintaining Advanced RaaS reports for job and applicant data
- Ensuring reports are:
- Enabled as Web Services
- Shared with the appropriate Integration System User (ISU)
- Structurally consistent across environments
Customers must provide Radancy with:
- Workday tenant name
- Integration System User (ISU) credentials for the applicable Workday environment
- RaaS report endpoint URLs (Simple XML)
- Workday Web Services endpoint (WSDL URL) for SOAP-based integrations
Example Workday Web Services endpoint:
Radancy does not create or modify reports directly within the customer’s Workday tenant. Report configuration must be completed by the customer’s Workday administrator or implementation partner.
Job (Requisition) Feed Requirements
The job feed provides job requisition data from Workday to Radancy to support multiple Radancy products.
Products Consuming Job Data
The Job feed powers the following Radancy products:
- Career Sites
- CRM
- Screening & Scheduling
- Employee Referrals
- Insights & Analytics
- Programmatic AdTech
Job Feed Direction
Workday → Radancy
Job Feed Transport & Format
| Attribute | Value |
| Transport | Workday RaaS (Report-as-a-Service) |
| Format | XML |
| Access Method | Web Service |
Job data is retrieved from Workday using a custom Advanced RaaS report built on the Job Requisition business object.
Core Job Feed Data Requirements
The Job RaaS report must include the fields necessary to support Radancy career sites and downstream TAC platform products such as CRM, Employee Referrals, Insights & Analytics, and other services.
Customers must provide these fields in the format required for display on their career site and use within Radancy systems.
Required Fields
The following fields are required for the job integration to function correctly:
- Job Title
- Job ID/Requisition number (unique identifier)
- Job Category
- Job Description
- Primary Job Location:
- City
- State/Province
- Country
- Postal Code
- Application URL
- Salary/Compensation Range
Recommended Fields (CRM, Referrals, S&S):
- Recruiter Email (required for CRM & Referrals)
- Hiring Manager Email
- Recruiter Name
- Additional Locations
- Remote Status
- Employment Type (FT/PT)
- Job Level
- Business Unit/Department
- Referral Reward
- Referral Featured Job
- Custom Fields (use-case driven)
Job field requirements and examples are documented in the Workday Jobs Integration Guide.
Job RaaS Configuration Requirements
The job feed is powered by a custom Advanced RaaS report configured within the customer’s Workday tenant.
The report must meet the following requirements:
- Report Type: Advanced Custom Report
- Primary Business Object: Job Requisition
- Output Format: Simple XML
- Enabled as Web Service
- Shared with the Integration System User (ISU)
The report must return the complete set of job requisitions intended to be published to Radancy and consumed by downstream TAC platform products.
Column Heading Overrides should be used intentionally, as these values become the XML element names consumed by Radancy.
Each job requisition should appear as a single Report_Entry element within the XML response.
Source Code / Tracking Parameters
Radancy supports the use of URL-based source tracking parameters appended to job and apply URLs to enable source attribution within Workday.
These parameters allow Workday to capture the origin of candidate applications (for example, job board, campaign, or media source) on the application or candidate record.
Example:
How It Works
- Tracking parameters are appended to outbound job or apply URLs
- Candidates enter the career site or application flow with these parameters
- Workday maps these values to Source and/or tracking fields on the application or candidate record, based on configuration within the ATS
Workday Considerations
- Source values must be defined and maintained within Workday
- Source mappings must align with the values passed via URL parameters
- Configuration is managed within Workday and is not controlled by Radancy
- Clients should work with their Workday administrator or implementation partner to configure recruiting source tracking
Considerations
- URL parameters may be lost during redirects if not preserved
- Inconsistent naming conventions may result in inaccurate reporting
- A standardized naming convention is recommended to ensure consistent tracking across sources