iCIMS Jobs Feed Implementation Guide

Project Scope

This document defines the requirements and process for implementing a Jobs Feed integration between iCIMS and Radancy Talent Acquisition Cloud (TAC).

The Jobs Feed serves as the primary source of truth for open job requisitions displayed on the Radancy Career Site and supports downstream Radancy modules.

Additional integrations may be required based on the Radancy modules under contract, including but not limited to CRM, Employee Referrals, Hiring Events, Screening & Scheduling, Insights & Analytics, and Programmatic AdTech.

This is a one-way integration from iCIMS to Radancy. This document covers job requisition data only. Applicant (candidate) data is out of scope and handled separately if contracted.

Integration Summary

• Integration Type: API-based job feed
• Integration Method: iCIMS Jobs REST APIs
• Data Direction: iCIMS → Radancy
• Refresh Frequency: Up to four imports per day (standard)
• Data Format: JSON

Authentication & Security

Supported Authentication

iCIMS Jobs APIs use HTTP Basic Authentication.

Authorization: Basic <base64(username:password)>

API User Requirements

• Dedicated iCIMS API service account
• Access to the appropriate customer portal(s)
• Permission to view job postings and configured custom fields

Network Access

iCIMS requires Radancy IP addresses to be allowlisted for API access. Radancy will provide the required IP list during implementation.

Client Requirements (iCIMS Jobs API)

To support the iCIMS Jobs API integration, the customer is responsible for providing the following information and completing the required configuration steps.

Required Information

1. Customer ID and Portal ID - Job data is retrieved based on portal configuration. One feed is required per portal.
2. API Credentials - iCIMS API username and password for a service account with appropriate permissions.
3. Job Detail Field Selection -Confirmation of which standard and custom job fields should be included in job detail API calls. iCIMS requires an explicit list of fields to be requested.
4. Field Mapping Document - A mapping table identifying each requested API field and the type of data it represents (for example, mapping a custom field ID to “Job Category”). Required for all custom fields.
5. IP Allowlisting Confirmation - Confirmation that Radancy import server IPs have been allowlisted in iCIMS.

Job Retrieval Model

Portal-Based Job Search

Jobs are retrieved based on portal visibility using the iCIMS Jobs search endpoint.

• Job visibility is controlled by iCIMS portal configuration
• Each job is identified by a unique Job ID

Job Detail Retrieval

Detailed job data is retrieved per Job ID using a separate job detail endpoint.

• iCIMS requires explicit field selection
• Only fields included in the request are returned
• Custom fields must be referenced using system-generated field IDs

Pagination & Volume Considerations

• Job search results are returned in paged responses
• Job detail calls scale with total job volume
• iCIMS enforces API usage limits per customer

Large volumes or high refresh frequency may require coordination with iCIMS.

Custom Fields & Field Mapping

iCIMS custom fields are referenced using system-generated field IDs (for example, field11130).

If custom fields are required to support career site display, search filters, or downstream Radancy modules, the customer must provide a Field Mapping Document identifying how each required field is represented in iCIMS.

This mapping is required for all custom fields and ensures data is interpreted and displayed correctly.

Job Feed 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.)

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.

High-Level Implementation Timeline

*Timeline is subject to change based on implementation variables.