Skip to main content
PATCH
Patches a published, open job — same field keys and types as PATCH /job-drafts/{jobId} (the authoritative key list is draft.updateKeys in capabilities). For unpublished drafts use the draft endpoint instead; this one requires the job to be OPEN. Every edit to a live job is re-moderated. If moderation rejects the edited content, the update is still applied but the job is unpublished back to DRAFT — fix the flagged content and publish again. Requirements: jobs:write scope + the public_api_job_publishing feature. The job must be yours and OPEN.

Request

string
required
The published job’s ID.
Body: a JSON object with one or more job fields — identical schema to the draft update endpoint. Unknown keys → 400 with zod issue details.

Response

boolean
true on success.
string
The job ID.
string
OPEN — the job stayed live.
object
{decision: "ALLOW", reasons: []} when the edit passed moderation.

Errors