Greenhouse Harvest

Greenhouse Harvest is a comprehensive recruiting platform that streamlines the hiring process through applicant tracking, interview scheduling, candidate evaluation, and team collaboration tools, helping organizations build better teams with data-driven recruitment strategies.

Power end-to-end data operations for your Greenhouse Harvest API with Nexla. Our bi-directional Greenhouse Harvest connector is purpose-built for Greenhouse Harvest, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Greenhouse Harvest or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Greenhouse Harvest workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Greenhouse Harvest credential, you need to obtain a Harvest API key from your Greenhouse account. The API key is required to authenticate with the Greenhouse Harvest API.

To obtain your Harvest API key, you need to have a Greenhouse account with admin access. Once you have access to your account, you can fetch your API key from your Greenhouse account in Configure >> Dev Center >> API Credential Management. The API key is used for Basic authentication, where the API key is sent as the username in the Authorization header for all API requests to the Greenhouse Harvest API. For detailed information about API key setup and authentication, refer to the Greenhouse Harvest API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Harvest API Key	Yes	Yes	Your Greenhouse harvest API key. You can fetch it from your Greenhouse account in Configure >> Dev Center >> API Credential Management

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Greenhouse Harvest

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Greenhouse Harvest API key in the Harvest API Key field. This is the API key you obtained from your Greenhouse account in Configure >> Dev Center >> API Credential Management. Greenhouse Harvest uses Basic authentication, where the API key is sent as the username in the Authorization header for all API requests to the Greenhouse Harvest API.

   Keep your API key secure and do not share it publicly. The API key provides access to your Greenhouse account data and should be treated as sensitive information. You can view and manage API keys in your Greenhouse account in Configure >> Dev Center >> API Credential Management. For detailed information about obtaining and managing API keys, see the Greenhouse Harvest API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Greenhouse Harvest connector tile, then select the credential that will be used to connect to the Greenhouse account, and click Next; or, create a new Greenhouse Harvest credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Greenhouse Harvest endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch all Records of a Resource

Fetch all records of any resource. Use the advanced tab for fetching a filtered list of records.

• Select the resource type you want to fetch from the Resource Type dropdown menu. Available resource types include Applications, Candidates, Degrees, Disciplines, Jobs, Job Posts, Job Stages, Offers, Offices, Schools, Scheduled Interviews, and Users. The default value is candidates if not specified. The resource type determines which type of data will be retrieved from your Greenhouse account.
• The endpoint uses GET requests to https://harvest.greenhouse.io/v1/{resource_type}?page=1&per_page=500 where {resource_type} is the Resource Type you select. The endpoint URL is automatically constructed based on the Greenhouse Harvest API base URL and the resource type.
• The endpoint uses link header pagination (iteration.type: link.header) through the link header mechanism. The response data path is $[*], which extracts all items from the root-level array in the API response.
• The endpoint fetches 500 records per page by default and automatically follows the link header to fetch additional pages until all records have been retrieved.

This endpoint retrieves all records of the specified resource type from your Greenhouse account. Available resource types include Applications, Candidates, Degrees, Disciplines, Jobs, Job Posts, Job Stages, Offers, Offices, Schools, Scheduled Interviews, and Users. The endpoint supports pagination through the link header, which allows you to retrieve large datasets efficiently. When a response includes a link header with a rel="next" value, Nexla automatically uses it as the URL for the subsequent request to fetch the next page of results. You can use the advanced tab for fetching a filtered list of records. For detailed information about available resource types and the API response format, see the Greenhouse Harvest API documentation.

Fetch one record of a Resource

Fetch a specific record a resource.

• Select the resource type you want to fetch from the Resource Type dropdown menu. Available resource types include Applications, Candidates, Degrees, Disciplines, Jobs, Job Posts, Job Stages, Offers, Offices, Schools, Scheduled Interviews, and Users. The default value is candidates if not specified. The resource type determines which type of data will be retrieved from your Greenhouse account.
• Enter the ID of the specific record you want to fetch in the Resource ID field. This should be the unique identifier for the record you want to retrieve. The default value is 0 if not specified.
• The endpoint uses GET requests to https://harvest.greenhouse.io/v1/{resource_type}/{resource_id} where {resource_type} is the Resource Type you select and {resource_id} is the Resource ID you provide. The endpoint URL is automatically constructed based on the Greenhouse Harvest API base URL, the resource type, and the resource ID.
• The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $, which extracts the entire root-level object from the API response.

This endpoint retrieves a specific record of the specified resource type from your Greenhouse account. Available resource types include Applications, Candidates, Degrees, Disciplines, Jobs, Job Posts, Job Stages, Offers, Offices, Schools, Scheduled Interviews, and Users. You must provide the unique identifier (Resource ID) for the record you want to retrieve. The endpoint returns a single record matching the specified resource type and ID. For detailed information about available resource types and the API response format, see the Greenhouse Harvest API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Greenhouse Harvest data sources can also be manually configured to ingest data from any valid Greenhouse Harvest API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Greenhouse Harvest API endpoints typically follow the pattern https://harvest.greenhouse.io/v1/{endpoint_path} and return data in JSON format. The endpoint requires Basic authentication via the Authorization header, where the API key is sent as the username; this is handled automatically by your credential configuration. For detailed information about Greenhouse Harvest API endpoints and available APIs, see the Greenhouse Harvest API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Greenhouse Harvest data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.