v1
latestOpenAPI 3.1.02026-07-261770816.7 KBCreate job post
Create a new job post by duplicating an existing one. The new post is attached to the same parent job as the template (template_job_post_id) and published to the supplied job_board_id. Use this to spin up additional language, geography, or board variants of a job's listing without re-entering the content, application questions, or settings. To create the first post on a job, post a template from another job and adjust the resulting post; this endpoint does not create a post from scratch.
Request body
Id of an existing job post to duplicate. The new post is created on the same parent job as the template and copies its content, questions, and configuration. The template post itself is unchanged.
Public-facing title for the new post. Defaults to the template post's title when omitted.
HTML body of the post shown to candidates. Sanitized server-side — only a limited element/attribute allowlist (including iframe, video, source) survives. Pass null or omit to inherit the template's content.
If true, create the post on the organization's internal job board (employees only). If false or null, the post is external. Must be consistent with job_board_id — internal job boards only accept internal posts.
Initial publication status. Use live to publish immediately or draft to save as an unpublished working copy. Defaults to draft.
Id of the demographic question set to attach to the new post for DE&I reporting. Pass null to opt out of demographic questions.
Id of the job_board to publish the post to. A single post belongs to one board at a time; resolve available boards via GET /v3/job_boards.
Response
Successful
Public-facing title shown to candidates on the job board (e.g. Senior Backend Engineer, Remote). Distinct from the internal job.name — a single job can have several posts with different titles, one per board, language, or geography.
If true, the post lives on an internal job board and is visible only to existing employees signed in to the internal board. If false, the post is external and lives on a public-facing job_board. Set by the board the post is associated with at create time.
If true, the post has not been deleted. Deleted posts are excluded by default; pass active=false on the list endpoint to retrieve them.
If true, the post is published (job_application_status is live) and its job board is also live. A post on an unpublished board is not live — its public_url returns a 404 until the board is enabled.
If true, the post is currently featured on the organization's internal job board and surfaces in the weekly internal-jobs email. Only internal posts can be featured, and at most three can be featured at a time.
Timestamp the post first transitioned to live, in ISO 8601. null for posts that have never been published.
HTML body of the post shown to candidates on the job board. For internal posts this returns the internal_content instead. Sanitized server-side — only a limited element/attribute allowlist (including iframe, video, source) survives. null while the post is still being scaffolded.
HTML body shown on the internal job board when the post is also configured as internal. null for external-only posts. Same sanitization rules as content.
ISO 639-1 locale of the post, used to render the candidate-facing application form in the matching language (e.g. en, fr, ja). null when no locale has been chosen.
Canonical public URL of the post on its job board, including the gh_jid tracking parameter. null when the post has no associated job board or the board has no public URL configured.
Id of the demographic question set surfaced to candidates on this post for diversity, equity, and inclusion (DE&I) reporting. null when the post does not collect demographic data.
Id of the parent job (requisition) this post belongs to. A single job can have multiple posts; the job is the source of truth for the hiring team, openings, and interview plan.
Id of the job_board this post is published to. Resolves to either an external (careers site, syndicated board) or internal job board depending on internal. Each post belongs to exactly one board at a time.