Oracle Recruiting Cloud (ORC) Jobs Feed Implementation Guide

Project Scope

Purpose

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

Scope Overview 

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.

Out of Scope 

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

Integration Summary

Integration Details

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

Data Retrieval Model

Oracle Recruiting Cloud does not expose all required job data within a single endpoint. As a result, the ORC jobs feed integration uses a multi-call enrichment model in which Radancy retrieves core job requisition data and supplements it with additional API calls to obtain complete job information for career site display and downstream processing.

Authentication & Security

Supported Authentication

Oracle Fusion Cloud HCM REST APIs use Oracle’s Multi Token Over SSL security policy.

Authentication methods supported by Oracle Recruiting Cloud may include:

• Bearer token–based authentication (issued via the Oracle Identity Domain / IAM configuration)
• JSON Web Token (JWT)–based authentication (tenant-dependent)
• Basic Authentication (legacy / tenant-dependent)

Radancy will align to the authentication method supported and approved for the customer’s ORC tenant. The same authentication method is used consistently across all ORC endpoints used by this integration.

Bearer Token Authentication (If Enabled)

Client Requirements:

• OAuth client created in Oracle HCM Cloud
• Client ID
• Client Secret
• Token endpoint URL
• Recruiting REST API scopes

Example Token Request

API Header

JWT Authentication (Advanced / Conditional)

Oracle Recruiting Cloud may support JSON Web Token (JWT)–based authentication depending on the client’s Oracle Identity configuration.

This method requires additional setup, including:

• generation of x509 certificates
• coordination with the client to install and configure certificates
• creation and signing of JWT tokens per Oracle requirements

JWT authentication requires coordination between Radancy and the client’s Oracle team and may extend implementation timelines.

Basic Authentication (If OAuth Is Not Enabled)

The user must have Recruiting REST access and content permissions.

Base API Structure

All Oracle HCM REST requests follow this pattern:

Example:

Primary Job Feed Endpoint

Purpose

The primary endpoint retrieves the core set of job requisitions and serves as the source of truth for job records.

Endpoint Details

Query Parameters (High Level)

• expand=publishedJobs: Retrieves external posting metadata associated with the job requisition.
• q (filtering): Limits results to eligible jobs (e.g., open and externally posted).
• onlyData=true: Returns the response without the metadata envelope (formatting preference).

Filtering Rules (ORC)

Jobs are included when they meet the following conditions:

• Job belongs to a job family
• Job is open
• Job is externally posted

Sample Request (Example)

Pagination

ORC uses offset-based pagination with limit and offset. Radancy manages paging internally to retrieve all eligible records.

Secondary Job Data Enrichment

Oracle Recruiting Cloud does not return all job-related data in the primary job requisitions response. Additional job data may be retrieved to support career site display and Radancy products under contract. Radancy will identify required and optional job fields based on product needs. The customer may be asked to confirm field mappings or enable Oracle configuration to expose specific job-related data. Enriched job data may include candidate-facing job content, organizational attributes, location details, and compliance-related information.

References:

Oracle Recruiting Cloud API Documentation

Oracle Recruiting Cloud Authentication Documentation

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.