Curviate Jobs

Curviate: job postings and applicants

Every posting starts as a draft. Drafts are free and reversible; publishing is neither. The two things that surprise agents here are that a free publish is still subscription-gated and that an update's read-back lags the write.

Command surface established against CLI 0.33.0.

Before any command

npm install -g @curviate/cli && curviate --version    # needs Node 18 or newer
curviate login --api-key <key>                        # or export CURVIATE_API_KEY
curviate account list --json                          # the acc_id for --account

• Credentials resolve flag > environment > stored profile (CURVIATE_API_KEY, CURVIATE_BASE_URL, CURVIATE_ACCOUNT).
• --profile <name> picks the stored credential set; --account <acc_id> picks which connected LinkedIn account owns the posting.
• --preview before every write, and especially before a publish. On a read command it is refused with exit 2.
• --json on anything you parse; --fields a,b,c to project; --verbose when a slim response looks suspiciously empty.
• Put global flags at the end of the command.
• Branch on the exit code, never on prose. See the table at the end.
• These are not retrieval-mode commands: --mode/--max-age are refused here with unknown flag, exit 2. job publish --mode is a different flag with the same name: it selects a publishing publishing mode and can spend real money. See curviate-profile for retrieval mode.

The commands

job create: the required set

--description (minimum 200 characters, enforced server-side), --workplace-type (ON_SITE|HYBRID|REMOTE), --location (a LOCATION parameter id, resolved via curviate search parameters --type LOCATION), --employment-status (FULL_TIME|PART_TIME|CONTRACT|TEMPORARY|OTHER|VOLUNTEER|INTERNSHIP), --apply-method (linkedin or external), plus a title and a company.

• Title: --job-title as free text, or --job-title-id for an existing LinkedIn title.
• Company: --company as free text, or --company-id.
• --apply-method linkedin requires --notification-email; --apply-method external requires --website-url.
• --skills takes comma-separated skill parameter ids and is optional.

Run curviate job create --help for the current required set before building a call.

Traps

• A publish is subscription-gated in practice, not just on the paid modes. --mode FREE (the money-free mode) still returns LINKEDIN_FEATURE_NOT_SUBSCRIBED, exit 5, on an account with no LinkedIn job-posting subscription. On that error nothing goes public and the draft stays a draft. Expect exit 5 unless you have confirmed the subscription; do not read it as a malformed request.
• publish and close are wired, never live-fired. Every test account run against this surface hit the subscription gate above before a posting ever went public, so a live 200 from either command has not been observed; close's happy path is unreachable the same way, since nothing gets published to close. The response shapes are cross-checked against the substrate's own types rather than an observed call. The read and draft surface above publish (list/get/budget/create/update, plus the three applicant reads) does not depend on that subscription and is proven.
• An update lands before the read-back reflects it. job update returning exit 0 was applied, but its own response and an immediate job get can both still show the old value, while job list (the owner view, checked minutes later) shows the update did land. Do not conclude a silent no-op from a stale-looking immediate read.
• job list --state filters client-side and says so on stderr. LinkedIn's own state filter is best-effort, so the CLI re-fetches the unfiltered page walk and drops non-matching items itself, logging what it dropped. Read stdout for data and stderr for what was dropped, and note that --all may walk far more upstream pages than the filtered item count suggests.
• job close is irreversible once the posting is listed. Preview it, and be sure.
• Price before you publish. job budget <id> costs nothing and is the only way to know what a promoted publish will spend.

A safe posting flow

curviate job create --job-title "…" --company "…" --workplace-type REMOTE \
  --location <loc_id> --employment-status FULL_TIME --description "$(cat jd.md)" \
  --apply-method linkedin --notification-email <email> --account <acc_id> --preview --json
# re-run without --preview to create the draft, then:
curviate job get <id> --account <acc_id> --json          # confirm the draft
curviate job budget <id> --account <acc_id> --json       # price it
curviate job publish <id> --mode FREE --account <acc_id> --preview --json