Curviate Premium

Curviate: Sales Navigator and Recruiter

Sales Navigator and Recruiter are no longer gated by a separate Curviate add-on: there is one paid subscription and one seat, and these commands carry no extra Curviate paywall. What can still refuse them is LinkedIn's own subscription on the connected account, and, where a workspace has not opted into beta operations, the beta gate.

Every command here is badged beta. That badge is a truth claim about stability, not a refusal: the beta-gated set is empty at launch, so these commands are callable today. If that changes, the refusal is BETA_NOT_ENABLED and the fix is entirely yours; see Gates below, including what that refusal actually looks like at this CLI version.

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

• curviate profile subscription --json reads what LinkedIn grants the connected account: has_premium and the plan. A free account is a valid result, not an error. It tells you nothing about your Curviate seat, and it is the read to do before assuming a Recruiter command will work.
• --profile <name> picks the stored credential set; --account <acc_id> picks which connected LinkedIn account's seat is used. A tenant can hold one subscribed account among several.
• --preview before every write. It renders the resolved request without sending. 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 with unknown flag, exit 2, with one exception that is not retrieval either. recruiter job publish has a required --mode FREE|PROMOTED|PROMOTED_PLUS, the same publishing flag job publish carries, and PROMOTED/PROMOTED_PLUS spend real money. A retrieval value there is refused at exit 2.

Gates: what can refuse these commands

Read error.code; three causes share exit 5 and their fixes have nothing in common.

Beta consent is an act a person performs, so no CLI command grants it persistently: someone turns on "Allow beta operations" in Settings, or a caller sends PATCH /v1/tenant/beta over REST.

For one call, use the global --beta flag. It allows beta operations for that invocation only and persists nothing; --beta=false withholds consent explicitly. A malformed value is a usage error, exit 2. So an unattended run that must not depend on a workspace setting can pass --beta per call rather than requiring someone to have flipped the toggle first.

Validate the request shape first

An INVALID_REQUEST / exit 2 on a premium command says nothing about entitlement. Request validation runs before every entitlement check, so exit 2 means the request itself is malformed, whatever your seat, subscription or beta-consent state. Fix the request.

The converse holds regardless of version: a well-formed request that is refused is refused by a gate, and exit 2 is never one of those answers. Which gate you can name depends on the client: LINKEDIN_FEATURE_NOT_SUBSCRIBED arrives readable at exit 5, while the seat and beta refusals arrive as INTERNAL at exit 1 on this version (see Gates). Either way the split holds: exit 2 is a shape problem, and an entitlement problem is never exit 2.

Earlier guidance here said the opposite: that an exit 2 on a premium command was worth reading as a hidden entitlement failure. That was wrong. The observation behind it was real, but those requests were malformed in a way the caller could not see, and the entitlement was blamed for it.

sales-nav

Sales Navigator filter ids are not interchangeable with the classic ones from curviate search parameters; resolve them through sales-nav search parameters.

recruiter

A project is the organising unit: a project holds one job posting, one pipeline and one talent pool. recruiter job create opens a new project; recruiter project-job create attaches a draft to a project that already exists.