Create job

post

https://harvest.greenhouse.io/v3/jobs

Create a new job from an existing template. template_job_id and number_of_openings are required; the template supplies the interview plan, scorecards, hiring team, and approval workflow, since Greenhouse Recruiting remains the source of truth for those configurations. One opening is created for each requested slot, optionally tagged with a partner opening_ids entry. Department and offices can be set either by Greenhouse id (department_id, office_ids) or by partner external_id (external_department_id, external_office_ids) — the id and external-id forms are mutually exclusive. The legacy confidential flag cannot be set through this endpoint. Required job custom fields the template leaves blank must be supplied in custom_fields, and select values must be active options (GET /v3/custom_field_options?active=true); a 422 response lists the offending fields in errors.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

template_job_id

integer

required

Id of an existing job (typically a template) used as the source for this job's interview plan, scorecards, hiring team, and approval workflow. Required — Greenhouse Recruiting remains the source of truth for these configurations, so new jobs always inherit them from a template.

number_of_openings

integer

required

Number of openings to create on the new job. Each opening can be filled by a single hire. The total open openings across the job cannot exceed Greenhouse's internal limit of 200; requests that would exceed it are rejected.

job_post_name

string

External-facing title for the job's initial internal job post (the listing shown on the company's careers site). Defaults to job_name when omitted.

notes

string

Internal HTML notes about the job, surfaced to the hiring team in the Greenhouse UI.

job_name

string

Internal job title shown to the hiring team (e.g. Senior Backend Engineer). When omitted, the template job's name is used.

department_id

integer | null

Id of the department to assign the job to. Mutually exclusive with external_department_id.

external_department_id

string | null

Partner-supplied external_id of the department to assign the job to. Resolved to a Greenhouse department_id in the caller's organization; unknown values are rejected. Mutually exclusive with department_id.

office_ids

array of integers | null

Ids of the offices to assign the job to. A job can span multiple offices. Mutually exclusive with external_office_ids.

office_ids

external_office_ids

array of strings | null

Partner-supplied external_id values of the offices to assign the job to. Each entry is resolved to a Greenhouse office_id in the caller's organization; unknown values are rejected. Mutually exclusive with office_ids.

external_office_ids

requisition_id

string | null

Partner-supplied external identifier for the requisition (e.g. an HRIS or ATS code). Free-form string and not required to be unique across the organization.

opening_ids

array of strings | null

Optional partner-supplied identifiers for the openings being created — one entry per new opening, paired positionally with number_of_openings. Each value is stored on the resulting opening as its opening_id (a free-form string, not the Greenhouse opening id) and may be null. Greenhouse enforces an internal limit of 200 open openings per job; requests that would exceed it fail.

opening_ids

custom_fields

array of objects

Values to set on this job's job custom fields. Each entry identifies the field by custom_field_id or name_key and supplies a value whose shape matches the field's value_type (see GET /v3/custom_fields?field_type=job). Every field marked required that the template job leaves blank must be supplied here. Single-select and multi-select values must name an active option: read them from GET /v3/custom_field_options?active=true, because archived options are listed unless active=true is passed and are rejected on write.

custom_fields

ignore_custom_field_requirements

boolean

If true, skips validation that required job custom fields have a value. Useful for integrations that only intend to sync a subset of fields and rely on the template job or a later request to supply the rest. Restricted to integration service-account credentials; other callers are rejected with a 422.

ignore_approver_permission_check

boolean

If true, skips the check that a user set as a job or offer approver via custom_fields has permission to view/edit this job. Lets an integration assign an approver without first broadening that user's Greenhouse permissions. Restricted to integration service-account credentials; other callers are rejected with a 422.

Responses

401

Unauthorized

403

Forbidden

422

Unprocessable Content

Language

Credentials

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Successful