jobs.update

Apply a partial update to a job posting this account owns, only included fields change.

Prerequisites

  • A Curviate API key, passed as apiKey when you construct the client. Quickstart shows how to create one.
  • A connected LinkedIn account. This resource is account-scoped: the account_id is injected automatically by the account-scoped accessor, so you pass it once to curviate.account(...) and every call below inherits it. Quickstart covers connecting one, and accounts.list returns the account_id of each account already connected.

Signature

update(jobId: string, body: UpdateJobBody): Promise<UpdateJobResult>

Example

import { Curviate } from "@curviate/sdk";
 
const curviate = new Curviate({
  apiKey: "cvt_live_...",
  baseUrl: "https://api.curviate.com",
});
 
const result = await curviate.account("acc_YOUR_ACCOUNT_ID").jobs.update("job_YOUR_JOB_ID", { job_title: { id: "YOUR_ID" } });
console.log(result.id);

Parameters

NameTypeRequiredDescription
jobIdstringYesThe job posting's numeric id, e.g. 4100000000 (from the LinkedIn job URL or a search/jobs result). A full URL is not accepted here.
job_titleobjectNoThe job title, reference an existing LinkedIn job title by id, or supply a free-text name.
companyobjectNoThe hiring company, reference an existing company by id, or supply a free-text name.
workplace_typestringNoWorkplace arrangement.
locationstringNoA LOCATION parameter id from GET /v1/{account_id}/search/parameters.
employment_statusstringNoEmployment type.
descriptionstringNoFull job description (minimum 200 characters). Content passes through verbatim, never stored.
apply_methodobjectNoHow candidates apply, through LinkedIn (with a notification email) or an external site.
skillsarrayNoOptional skill parameter ids from GET /v1/{account_id}/search/parameters.
screening_questionsarrayNoOptional screening questions attached to the posting.
rejection_settingsobjectNoOptional automatic-rejection configuration.

Returns

Resolves to UpdateJobResult. Top-level fields: object, id, title, company, location, state, is_repost, is_application_limit_reached, industries, created_at, description, views_count, applications_count, screening_questions, workplace_type, employment_status, budget, published_at, expires_at, closed_at, listed_at, hiring_team, safety_warning.

Error codes

CodeWhat it means, and what to do
UNAUTHORIZEDThe API key is missing, malformed, or revoked. Check the key you passed to the client.
INVALID_REQUESTA parameter failed validation. The message names the offending field; fix the request rather than retrying it.
RATE_LIMIT_ACCOUNTThis account's own quota is exhausted. Wait for the window in the Retry-After header, then retry.
RATE_LIMIT_TENANTThe tenant-wide quota is exhausted across all accounts. Slow the whole workload, not just this call.
PLATFORM_RATE_LIMITLinkedIn is throttling this account. Back off well beyond the hinted delay; sustained pressure risks the account.
PLATFORM_ERRORAn upstream failure, usually transient: retry once with backoff before treating it as a real error. Check the response first, though. When it carries retry_likely_to_succeed: false and retry_hint: {kind: "never"}, retrying cannot help and backing off only delays the real answer.
ACCOUNT_NOT_FOUNDNo connected account with that id belongs to this tenant. List your accounts to get a current id.
INTERNALAn unexpected server error. Retry once; if it persists, it is ours, not yours.
NO_ACTIVE_SEATThe targeted account is not on an active seat. Buy or attach a seat in Billing, then retry.
PAYLOAD_TOO_LARGEThree limits can trigger this. The platform's own ceiling on total request size is the lowest and the one you are most likely to hit: it starts rejecting at roughly 1 MB, so a handful of photo-sized images is refused even though it clears everything below. Above that, this API caps one attachment at 5 MiB of file content and the whole request body at 9 MiB. Attachments travel base64-encoded, which inflates them by about a third, so a 5 MiB file costs roughly 6.7 MiB of the body budget. Send fewer or smaller attachments; retrying unchanged will not help.
RESOURCE_NOT_FOUNDThe id in the path does not exist, or is not visible to this account. Re-read it from the list endpoint that produced it.

Every code above is a stable CurviateError.code you can branch on. The full list, the response envelope, and retry semantics are in the Error codes reference.

Next steps

  • jobs.list: List the connected account's own classic job postings.
  • jobs.listApplicants: List applicants to a job posting this account owns, a read; POST carries the filter body, matching the convention.
  • jobs.get: Retrieve one classic LinkedIn job posting's full detail.
  • SDK Quick Start: installation, the client, account scoping, and pagination.