Access the latest version of Harvest API documentation at harvestdocs.greenhouse.io.

Harvest API v1 and v2 will be deprecated and unavailable after August 31, 2026. Please make sure that your existing custom integrations use the latest version of Harvest (v3) by this date and any new integrations are developed with the latest version of Harvest API.

This article is intended for people who are currently working on an HRIS integration and need to extract Greenhouse Recruiting job IDs from your template jobs. Once your organization has created template jobs in Greenhouse Recruiting, you can extract the job IDs in a few different ways – either in-app in Greenhouse Recruiting or programmatically by using Greenhouse Recruiting's Harvest API.

Retrieve a job ID in Greenhouse Recruiting

To retrieve an individual job ID in-app in Greenhouse Recruiting, select All Jobs from your navigation bar, and find the template job in your list of jobs. Click the job and note the URL shown in your browser – the job ID is the last numerical string on the URL.

Example: The Greenhouse Recruiting job URL structure is https://app2.greenhouse.io/sdash/{JOB_ID}. In the example below, the job ID is 1234567890.

Retrieve multiple job IDs in Greenhouse Recruiting

To retrieve multiple job IDs in-app in Greenhouse Recruiting, select All Jobs from your navigation bar. Select Filter to apply any necessary filters, and be sure to check Show only template jobs.

Check the box to select all resulting jobs in your list.

Click Bulk Actions and choose Download stage by job report.

The resulting report includes a list of all Greenhouse Recruiting template jobs along with the corresponding job ID in column B.

Retrieve job IDs programmatically using Harvest API

Teams building a custom integration can retrieve job IDs programmatically using Greenhouse Recruiting’s Harvest API.

To obtain job ID values needed for the template_job_id, reference the GET: List Jobs endpoint in the Harvest API documentation.

Refer to the Harvest API documentation for current endpoint behavior, response structure, and filtering options.