Greenhouse Jobs Feed Implementation Guide

This document defines the requirements and process for implementing a Jobs Feed integration between Greenhouse Recruiting 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 Greenhouse Recruiting 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: Greenhouse Harvest API is the standard integration method. The Job Board API is limited and not recommended for new implementations.
• Data Direction: Greenhouse → Radancy
• Data Format: JSON (transformed for downstream processing)
• Authentication: API key–based authentication over HTTPS
• Refresh Frequency: Up to four imports per day (standard), configurable

Integration Architecture

The integration retrieves job data from Greenhouse via API and processes it through the Radancy Job Importer before publishing to the Radancy platform for career site display and downstream processing.

Job data is refreshed during scheduled import cycles.

Feed Configuration

The Greenhouse integration is configured using API endpoints and client-provided credentials.

Required Inputs

For standard (Harvest API) integrations:

• Harvest API Key
  • Harvest API keys are generated in Greenhouse under Configure → Dev Center → API Credential Management and require appropriate developer permissions within the Greenhouse platform.
• Base API URL: https://harvest.greenhouse.io
• API permissions for required endpoints

For legacy / limited-use implementations (if applicable):

• Board Token (Job Board API)

Endpoint Overview

Harvest API (Standard / Recommended)

GET /jobs 

GET /job_posts

Additional endpoints may be used as needed based on required fields and configuration.

Job Board API (Legacy / Limited Use)

GET /v1/boards/{board_token}/jobs

The board token is a unique identifier for the client’s public job board in Greenhouse.

API Version Considerations

Greenhouse job feed integrations may be implemented using different API methods depending on the client’s current setup. Radancy’s standard approach is to use the Harvest API for new implementations.

Some existing Greenhouse integrations may still rely on the Job Board API for publicly available jobs. Because method, field availability, and endpoint behavior can differ by integration approach, final configuration should always be confirmed during implementation.

Data Retrieval Model

The integration uses a query-based, multi-endpoint retrieval model leveraging the Greenhouse Harvest API.

Job data is primarily retrieved from the Jobs endpoint, with additional endpoints such as Job Posts, Offices, and related resources used as needed to enrich job data.

This approach supports broader field coverage and greater implementation flexibility than public job board–only access.

Data Retrieved Includes

• job ID and title
• job status
• job posts (external postings)
• job descriptions and HTML content
• department hierarchy
• offices (locations)
• recruiter and related job metadata, where available and permitted by configuration

Field Strategy

To ensure performance and efficiency:

• a restricted field set is used
• only required fields are retrieved
• additional fields must be explicitly configured

The integration may leverage additional data processing to assemble a complete job dataset depending on client configuration.

Job Eligibility Logic

Jobs are typically considered eligible for import when the following conditions are met:

• job status is open
• job has at least one live job post
• the job post is configured for external visibility

Pagination Handling

Greenhouse APIs support pagination, and pagination behavior may vary depending on the endpoint used. The Radancy Job Importer continues requests until all available records are retrieved. Final pagination handling should be confirmed based on the selected endpoint configuration.

Authentication & Security

Harvest API (Standard / Recommended)

• Uses API credential–based authentication over HTTPS
• API credentials must include the permissions required for the endpoints in scope
• Access should be limited to only the permissions needed for the integration
• Additional authentication methods (such as OAuth) may be supported depending on client configuration

Job Board API (Legacy / Limited Use)

• Does not require authenticated API access
• Requires a board token
• Returns only externally published, publicly available jobs

Required Client Configuration

Clients must provide:

Legacy / limited-use implementations may also require:

• Board Token (for Job Board API–based integrations)

Location & Multi-Location Handling

Location Data

Locations are structured via the offices object, and a job may be associated with one or more offices depending on client configuration.

Location data is derived from office configuration in Greenhouse and may vary in structure. To support accurate mapping, it is recommended that city, state/province, and country values are clearly defined and consistently formatted within the client’s Greenhouse environment.

Multi-Location Jobs

Greenhouse supports multi-location jobs through multiple associated offices and, in some cases, multiple job posts.

Radancy’s preferred approach is to support a single requisition with multiple associated locations, where supported by the client’s configuration and data structure.

Radancy processes multi-location data based on client configuration and determines appropriate handling for display and downstream use during implementation.

Legacy Integration Method (Job Board API)

Greenhouse also provides a Job Board API that returns publicly available job postings. This method is more limited than the Harvest API and is not the standard approach for new Radancy implementations.

Key considerations:

• requires a board token
• returns only externally published jobs
• provides more limited field availability than Harvest API access
• may be relevant for certain existing or legacy client configurations

The Harvest API remains the standard and recommended method for Greenhouse job feed integrations.

References:

Greenhouse API Documentation

Greenhouse Harvest API Documentation

Known Integration Considerations

Data Variability

Field availability may vary based on configuration and permissions.

Job vs Job Post Structure

• Job = internal object
• Job Post = external/public posting

Depending on the integration method and fields in scope, both may be needed to construct the final job dataset.

Rate Limits

Greenhouse APIs are subject to rate limits and should be considered when configuring import frequency.

Public vs Private Data

• Harvest API supports broader data access, subject to permissions and configuration
• Job Board API returns publicly available jobs only

Custom Fields

Custom fields require explicit configuration and mapping.

Integration Constraints

• API permissions must be configured correctly
• Some fields may not be accessible without proper scopes
• Job post content may differ from internal job data

Job Feed Requirements

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.