Update a job
PATCH/api/v1/jobs/:jobId
Partial update. Only the fields present in the body change; every
provided field is re-validated with the same strict save-time rules as
create (config re-runs the full position-config contract check).
position_idmay be changed, or cleared withnull. Changing it to a value held by another of your active jobs returns409 POSITION_ID_CONFLICT.- Updating a job does not alter past runs — each run snapshots the content it executed with. The next CV DeepSearch against the updated job automatically rebuilds its cached plan (see the Jobs guide).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
The updated job.
Validation failure (INVALID_INPUT) — per-field detail in
error.details.fields. Nothing is changed.
Missing or invalid API key.
Authenticated but missing the cvdeepmatch / cvdeepsearch permission.
NOT_FOUND — no active job with this id for your client. Also
returned for archived jobs and cross-tenant ids (no existence leak).
POSITION_ID_CONFLICT — the new position_id is held by another
of your active jobs.