Greenhouse Harvest

The answers provided to the questions in the job post for this application. Array contains the text value of the question and answer. Answers are always plaintext strings. Booleans will return Yes or No.

An array of attachments to be uploaded to this application. See Add Attachment for parameters.

The ID of the candidate who is applying for this job.

The ID of the user who will receive credit for this application.

The current stage that this application is in.

Contains a hash of the custom fields configured for this resource. The properties in this hash reflect the active custom fields as of the time this method is called.

The ID of the job stage this application will be created in. Only applicable when create Aplication from Candidate (without field `prospect`).

The ID of the job you want to create an application to for this candidate. Only applicable when create Aplication from Candidate (without field `prospect`).

An optional array of Job IDs to consider this prospect for. Only applicable when create Aplication from Prospect (with field `prospect` equal `true`).

An array containing the job that the candidate applied for.

This contains the same information as custom_fields but formatted in a different way that includes more information. This will tell you the type of custom field data to expect, the text name of custom field, and the value. The key of this hash is the custom field’s immutable field key, which will not change even if the name of the custom field is changed in Greenhouse.

The contents of the location question on a job post.

If true, this is a prospect application which means that the associated person is a prospect and has not yet applied for this job..

User ID of the prospect owner. Only applicable when create Aplication from Prospect (with field `prospect` equal `true`).

Prospect Pool ID. Only applicable when create Aplication from Prospect (with field `prospect` equal `true`).

Prospect Pool Stage ID. prospect_pool_id is required, and the prospect pool stage must belong to the given prospect pool. Only applicable when create Aplication from Prospect (with field `prospect` equal `true`).

The department that this prospect application is being considered for.

Department ID to consider this prospect for.

The office that this prospect application is being considered for.

Office ID to consider this prospect for. prospective_department_id is required in order to set a prospective office.

A string representing the type of referrer: 'id’, 'email’, or 'outside’

The id of the user who made the referral (not the referrer id)

The id of the source to be credited for this application

One of: active, rejected, hired, converted.

Applications

Use this field only for creating candidate with type "prospect"

Array of application IDs associated with this candidate. Can contain none, one, or several application IDs.

This is required field to create candidate with type "candidate"

The company at which the candidate currently works

The coordinator user who is responsible for this candidate.

This field is applicable for candidates with type "candidate"

Whether the candidate is private or not. One of: [“true”, “false”]

Contains the same information as custom_fields but formatted in a different way that includes more information. This will tell you the type of custom field data to expect, the text name of custom field, and the value. The key of this hash is the custom field’s immutable field key, which will not change even if the name of the custom field is changed in Greenhouse.

If the candidate is an internal applicant, this returns the Greenhouse user ID of the candidate.

Note: this field has been removed from Greenhouse and will always be null. For backwards compatibility, the field will remain in API payloads

The recruiter user who is responsible for this candidate.

Candidates

An arbitrary ID provided by an external source; does not map to another entity in Greenhouse.

The external_ids of this department’s children. Note the order of this array may not match the order of the child_ids array. If there are five children and none of them have parent ids, this array will contain five null indices.

The external_id of this department’s parent.

Departments

Interviews

The application that was used to fill this opening. This should only be set on a closed opening, null otherwise.

This is when the opening was closed; usually via the opening being filled. This should be null for opened openings.

These are the custom fields that are specific to openings. This index, along with keyed_custom_fields, may not be included if your organization does not have access to custom fields on openings.

This is the date and time this opening was created.

This is a text string used to identify the opening. This is defined by the users and may be null.

Job Openings

If false, this job post has been deleted.

The text of the job post as posted to the external job board.

The demographic question set associated with this job post

If true, this job post has been posted (or is to be posted) on an external job board.

Timestamp when this job post was first set to live.

If true, this job post has been posted (or is to be posted) on an internal job board.

The text of the job post if posted to the internal job board, if different than the external job board.

If true, this job post status is set to live.

An array of questions associated with this job post.

When submitting applications through the Job Board API, this is the name of the POST parameter used to submit questions. Custom questions are prefixed with “question_” while Greenhouse standard application questions have a consistent name for every job post.

Job Posts

The job stage's active status. true - The job stage is active, false - The job stage was deleted

An array of interview steps associated with this job stage

Details about the interview, including unique ID, interview prep content, and custom interview questions

True / False value for whether this step can be scheduled

Numeric field used for ordering, with the lowest values ordered first. For example, priority 0 indicates the first stage on a job

"200" Response schema

Job Stages

One of true, false. If the job is confidential or not.

Contains any custom job fields which have been defined by your organization.

An array containing the department which this job belongs to.

Lists the names and User IDs of the hiring managers, recruiters, coordinators and sourcers associated with this job. For recruiters and coordinators, there is a responsible boolean flag which indicates that the user is the responsible recruiter or coordinator for this job.

An array containing the offices this job is associated with.

Lists the openings associated with this job.

Timestamp when the opening was closed. An opening is closed when it is filled or removed.

An arbitrary ID provided by an external source; does not map to another entity within Greenhouse.

Jobs

The ID of the associated application

Custom Fields

The offer’s unique identifier

Keyed Custom Fields

Date when this offer was resolved (e.g. when it was accepted, rejected).

Date when this offer was sent to the candidate.

Date when the candidate starts. This is the date value entered in the default Start Date field on candidate’s Offer Details. This is the first field on their Offer Details, above the custom fields.

One of: unresolved, accepted, rejected, deprecated.

Status

The version number of this offer. When an existing offer is updated, a new one is typically created with an incremented version.

The version number of this offer

Offers

The external_ids of this office’s children. Note the order of this array may not match the order of the child_ids array. If there are five children and none of them have parent ids, this array will contain five null indices.

The external_id of this office’s parent.

Offices

Prospect Pools

An array containing the users who have interviews with this candidate, including, if applicable, the ID of the scorecard they completed, and the interviewer’s response_status

Indicates how the interviewer has responded to the interview invitation. One of: needs_action, declined, tentative, or accepted

The user who has an interview with this candidate

The user who is the organizer for this interview

One of: scheduled, awaiting_feedback, complete

The URL used for video interviews, such as Zoom, Google Meets, or Microsoft Teams.

	List	Find by ID	Match	Create	Update	Delete
Applications	✅	✅	➖	✅	✅	✅
Candidates	✅	✅	➖	✅	✅	✅
Job Openings	✅	✅	➖	✅	✅	✅
Scheduled Interviews	✅	✅	➖	✅	✅	✅
Users	✅	✅	✅	✅	✅	➖
Departments	✅	✅	➖	✅	✅	➖

	Jobs automatically maps to	Users automatically maps to	Job Candidates automatically maps to	Job Applications automatically maps to	Job Interviews automatically maps to
Lever	Postings	Users	Opportunities	Applications	Interviews
Breezy HR	Positions	Users	Candidates	—	—
Ashby	Jobs	—	Candidates	Applications	—
Recruitee	Offers	—	Candidates	—	—
BambooHR	Jobs	Users	—	—	—
Workable	Jobs	—	Candidates	—	—
Okta	—	Users	—	—	—
Google Workspace	—	Users	—	—	—
Deel	—	Users	—	—	—
ADP Workforce Now	—	—	—	Job Applications	—

Greenhouse Harvest integration connector

Managed authentication

Work with Greenhouse Harvest data collections

Trigger integrations on Greenhouse Harvest events

Data Record Created

Data Record Updated

Data Record Deleted

Use the same code to integrate with Greenhouse Harvest and 100+ other applications

Jobs

Users

Job Candidates

Job Applications

Job Interviews

Try our AI-powered integration development environment for free

Greenhouse Harvest integration connector

Managed authentication

Work with Greenhouse Harvest data collectionsself.__wrap_n!=1&&self.__wrap_b(":Rb556:",1)

Trigger integrations on Greenhouse Harvest eventsself.__wrap_n!=1&&self.__wrap_b(":Rbd56:",1)

Data Record Created

Data Record Updated

Data Record Deleted

Use the same code to integrate with Greenhouse Harvest and 100+ other applicationsself.__wrap_n!=1&&self.__wrap_b(":Rbl56:",1)

Jobs

Users

Job Candidates

Job Applications

Job Interviews

Try our AI-powered integration development environment for free

Work with Greenhouse Harvest data collections

Trigger integrations on Greenhouse Harvest events

Use the same code to integrate with Greenhouse Harvest and 100+ other applications