Purpose
The scope of this integration guide covers a one-way data synchronization from the SAP SuccessFactors ATS through Radancy’s Applicant Importer and consuming services: CRM, Employee Referrals, Insights & Analytics. The terms Applicant or Candidate can be used synonymously across ATS and Radancy systems, unless specifically stated.
Integration Security
Our standard integration utilizes SAP’s ODATA API, and the authentication workflow supports Basic Auth or OAuth2.0. When we are standing up an integration, we prefer to begin with using a staging environment so that the data available is test data rather than live candidate data. Therefore, we normally expect two sets of credentials over the full integration lifecycle. We begin by requiring the credentials for the staging environment. Once the integration is vetted on staging, we will progress forward to the production environment. Production credentials are required to enable the live integration.
The data in the staging environment should mirror the data collected in the production instance so that we can ensure the mappings are working as desired. We require applicant data, and job data in the sandbox for proper UAT.
Note: We will require the client’s ODATA API (datacenter) endpoints for Staging and Production. For basic authentication, Radancy will require its own integration username, password and customer’s companyID. For OAuth2.0 authentication, the customer will need to provide the following: token URL, service URL, Company Value, API Key and Private Key from Downloaded X.509 Certificate. Radancy will provide the customer’s Radancy applicant or employee referral instance URL during the registration process for OAuth2.0 authentication.
IP Whitelisting
The following Radancy Server IP addresses are required to be whitelisted within your SAP SuccessFactors instance: Action Center > API Center > OData IP Allowlisting
[North America Hosting]
- 3.214.163.179
- 3.217.163.207
- 3.217.100.148
[EU Hosting]
- 3.124.173.206
- 3.121.60.93
- 3.124.111.6
[Developer Workstation]
- TBD based on resource assignment
API Calls
Our integration (Scheduled Import) is based on a predetermined interval (ex. Once every 24hrs). Using the current date time as end time, and then based on frequency, determine start time. For example, if frequency is hourly, the start time will be the current date time - 1 hour.
Get new/update job applications and candidate details
Endpoint: GET “ /JobApplication”
Invoke with HTTPPost with start/end date range filter.
Related SAP SuccessFactors link for HTTP call: https://api.sap.com/api/RCMJobApplication/path/get_JobApplication
This API call with return a list of new/updated job applications within start/end time range. Radancy will pull candidate details as well. Radancy will use the following query within our API call:
odata/v2/JobApplication?$skip=0&$top=50&$filter=lastModifiedDateTime gt datetimeoffset'2024-10-
16T00:15:30Z' and lastModifiedDateTime lt datetimeoffset'2024-10-
26T05:15:30Z'&$select=lastModifiedDateTime,jobAppStatus/appStatusName,applicationId,jobReqId,job
Requisition/jobReqLocale,jobRequisition/departmentCode,candidate/candidateId,candidate/candidateI
d,candidate/firstName,candidate/lastName,candidate/cellPhone,candidate/address,candidate/primaryE
mail,candidate/country,candidate/state,candidate/city,candidate/zip,candidate/outsideWorkExperience
,candidate/education,homePhone,nonApplicantStatus,gender,source,address2,startDate,hireDate,ethni
city,jobRequisition/country,jobRequisition/jobReqLocale,offerLetter/jobStartDate,offerLetter/status&$e
xpand=jobAppStatus,candidate,candidate/education,candidate/outsideWorkExperience,jobRequisition/j
obReqLocale,ethnicity/picklistLabels,candidate/state/picklistLabels,jobRequisition,ethnicity,offerLetter
Note: The raw resume for a candidate is not found within the JobApplication API. The only reference to retrieving the raw resume path is the “resumeUploadDate” within the API. There could be an endpoint within a client’s SAP SuccessFactors instance (https://{datacenter}/odata/v2/Candidate({candidate_id})/resume) for raw resume retrieval and its response will contains file content based on byte array of a resume.
Radancy Applicant Model
The data pulled from the APIs will be mapped against Radancy’s standard applicant model for use within your Radancy TAC platform. A sample of our model is displayed below with added context for the value or purpose of the individual attributes.
| Requested Data | Purpose |
| Applicant ID | ATS unique identifier |
| Start Date | Nullable DateTime. Applicant’s start date (Hired state) |
| Address (Address, city, state, country, ZIP) | Physical location |
| Applications | Can be one or multiple for an individual |
| Application Id | Individual application identifier |
| Req ID | Associated job id (per application) – this will provide a link from the applicant profile to the job in CRM for all active jobs |
| Title | Job title – to display in CRM |
| Status | Current Status – needed for each application in a profile |
| Updated | Indicator of the date/time for the change in status allows for assessing priority |
| Job Information | Job req info |
| Business Unit | |
| Department | |
| Function | |
| Position Level | |
| Job Category | |
| Job City | |
| Job State | |
| Job Postal Code | |
| Job Region | |
| Job Country | |
| Custom Fields | Optional, ad hoc usage – lets discuss if you have needs |
| Educations | Applicant education experiences, this information will populate in the prospect profile in CRM |
| School Name | |
| Major | |
| Degree Obtained | |
| Date Range | Years attended |
| Email Address | Necessary unique identifier in our applicant system |
| First Name | |
| Last Name | |
| Phone Numbers | Phone numbers related to candidate profile, can have multiple fields for different phone number types |
| Professional Summary | |
| Certification | Any known certifications |
| Work Experiences | Experience history of prospect will add content to profile in CRM |
| Company Name | |
| Title | Position/job title |
| Work Description | Many more skills can be derived if we get better descriptions from the applicant's profile (if available) |
| Date Range | Start and end dates for experience |
| Social Network Links | LinkedIn, Facebook, GitHub, etc. |
| Military Service Info Resume Data (Raw Resume) |
Branch of service, rank, dates Resume Data (Raw resume) We can consume, display and parse this for data enrichment |
*Note – We understand the data available in your ATS will not necessarily encompass all these attributes. However, Radancy will work with you to identify the final mapping of your collected data against our standard model. We can also utilize resume documents/attachments to enrich applicant profiles within the CRM application. The ability to parse resumes will be dependent on the integration type available (API). Only the most recent application’s associated resume document for the applicant will be saved/stored for recruiting/sourcing use cases.