SmartRecruiters Standard Jobs Feed Implementation Guide – Posting API

Project Scope

Purpose

This document defines the requirements and process for implementing a Jobs Feed integration between SmartRecruiters 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 SmartRecruiters to Radancy. This document covers job requisition data only. Applicant data is out of scope and is handled separately if contracted.

Integration Options Overview

SmartRecruiters supports two job integration methods:

1. Posting API (API Key)
   • Used for publicly available job postings
   • Standard approach for career site integrations
2. Jobs API (OAuth 2.0)
   • Used when OAuth authentication is required
   • Supports scoped access via SmartRecruiters credentials

This document covers the Posting API (API Key) integration. If OAuth is required, please refer to the Jobs API integration guide.

Integration Summary

Integration Details

• Integration Type: API-based job feed
• Integration Method: SmartRecruiters REST API (Posting API)
• Data Direction: SmartRecruiters → Radancy
• Data Format: JSON
• Authentication: API Key (X-SmartToken header)
• Refresh Frequency: Up to four imports per day (standard), configurable based on client requirements and job volume

Data Retrieval Model

The SmartRecruiters jobs integration uses a multi-call retrieval model to obtain complete job posting information from the SmartRecruiters Posting API.

Radancy first retrieves a list of available job postings using the SmartRecruiters postings endpoint. For each posting returned, Radancy performs additional API calls to obtain the full job posting details, including job description content, location details, and application URLs.

This approach ensures that all required job information is collected before ingestion into the Radancy platform for career site display and downstream processing.

High-Level Integration Workflow

The SmartRecruiters integration follows a two-step API retrieval model.

Step 1 – Retrieve Job Postings List

Radancy retrieves the list of job postings.

Endpoint:

This request returns:

• Job posting metadata
• Job title
• Job reference number
• Posting ID

Step 2 — Retrieve Job Posting Details

Radancy then retrieves full job content for each posting.

Endpoint:

This request returns:

• Job description
• Job advertisement content
• Apply URL
• Company information
• Location information

This multi-call enrichment model allows Radancy to retrieve complete job data for career site display.
The importer platform then:

1. Merges job metadata and job content
2. Normalizes fields
3. Publishes job records to the Radancy ingestion pipeline.

Authentication & Security

SmartRecruiters APIs use API Key authentication.

Required Header

Note: SmartRecruiters Posting API does not support OAuth authentication.

Required Credentials & Configuration

To enable the SmartRecruiters jobs integration, clients must provide the following API credentials and configuration details.

Example Configuration

Optional headers may also be configured (example: language headers).

SmartRecruiters API Endpoints Used

1. List Job Postings

Endpoint:

Example Request:

Example parameters:

Example Request:

Example Response:

2. Get Posting Details

Endpoint:

This endpoint retrieves full job data including:

• Job advertisement content
• Job description
• Apply URL
• Company details
• Location information

This request is executed for each posting returned by the postings list endpoint.

Job Eligibility Logic

A job is considered active and eligible for import when:

1. It is returned by the /postings endpoint
2. It matches the configured destination filter

Example configuration:

This ensures that only externally published jobs are imported.

Jobs can also be filtered using:

This enables separate imports for internal and external career sites.

Jobs that are no longer returned by the configured postings endpoint will be removed from the Radancy platform during subsequent imports.

Pagination Handling

SmartRecruiters APIs use offset-based pagination.

Supported parameters:

Example:

Response fields used for pagination control:

• totalFound
• limit
• offset

The importer continues making requests until all pages of results have been retrieved.

Import schedules are configured to comply with SmartRecruiters API rate limits and platform best practices.

Job Identifier Handling (Multi-Location Support)

By default, SmartRecruiters job data includes a refNumber field, which may be shared across multiple job postings (for example, when a job is posted in multiple locations).

To ensure each job is processed uniquely, Radancy uses the id field as the primary job identifier.

• refNumber → may be duplicated across postings
• id → unique per job posting

Result:

• Prevents duplicate job failures
• Ensures all job locations are properly captured

Example:

A single job posted in multiple locations may:

• Share the same refNumber across postings
• Have a different id values per posting

Using id ensures each location is processed as a separate job.

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.