API Reference/Endpoints

Solve a publishing checkpoint

POST/api/linkedin/gateway/linkedin/jobs/{draft_id}/checkpoint

Submits the code LinkedIn sent to confirm the member is allowed to post a job, after Publish a job posting returned a checkpoint instead of publishing. This is a separate flow from the account-connection checkpoint (Submit a checkpoint code) — this one only ever comes up mid-publish.

Authentication

Send your personal API key as a bearer token. A missing, malformed or revoked key returns 401.

Path parameters

FieldTypeDescription

draft_id *stringThe same id used in the publish call.

Body parameters

FieldTypeDescription

account_id *stringThe connected account publishing this posting.

input *stringThe verification code the member received by email or SMS.

Response fields

FieldTypeDescription

objectstringLinkedinJobPostingPublished once the code is accepted, or LinkedinJobPostingPublishCheckpoint again if a further code is needed.

job_statestringPresent once published — the posting's new lifecycle state.

type"EMAIL_VERIFICATION" | "OTP"Present if another checkpoint follows — which kind of code to expect next.

job_idstringPresent on both — the posting's id.

Keep calling this endpoint with each new code until you get back a LinkedinJobPostingPublished response — LinkedIn can chain more than one verification step for a single publish.

Errors

·401 Unauthorized. The key is missing, malformed or has been rotated.·403 Forbidden. account_id doesn't belong to this key.·404 Not Found. No draft with that id belongs to this account, or there's no checkpoint pending on it.