@curviate/cli 0.46.1 → 0.48.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (46) hide show
  1. package/CHANGELOG.md +199 -1
  2. package/README.md +124 -77
  3. package/dist/{account-O5UX5UAH.js → account-WKQHMM7P.js} +41 -31
  4. package/dist/{chunk-BGZW6B7G.js → chunk-5I6JJJIV.js} +1 -0
  5. package/dist/{chunk-76E3O6HY.js → chunk-76SWLAZ6.js} +13 -0
  6. package/dist/chunk-AYKKXGTR.js +1141 -0
  7. package/dist/{chunk-TC4ZPUWI.js → chunk-CVMSQ3OF.js} +19 -80
  8. package/dist/{chunk-HOQ7EUHJ.js → chunk-FDJMAF7D.js} +1 -0
  9. package/dist/chunk-GQKC6E5K.js +36 -0
  10. package/dist/{chunk-FXF5FF3W.js → chunk-MKGVNDMJ.js} +10 -2
  11. package/dist/chunk-NNV2OYEF.js +23 -0
  12. package/dist/{chunk-UJOTQPL6.js → chunk-OHXYFICP.js} +47 -14
  13. package/dist/{chunk-2FECYCAC.js → chunk-Q63IIPL2.js} +3 -3
  14. package/dist/chunk-TSOIZBBU.js +41 -0
  15. package/dist/{chunk-DGIDAO2H.js → chunk-Y7K4UBFC.js} +1 -1
  16. package/dist/{chunk-LD6WPZZM.js → chunk-YFXLXION.js} +39 -34
  17. package/dist/chunk-ZYURL5VK.js +83 -0
  18. package/dist/cli.js +77 -97
  19. package/dist/{comment-BKGVJYS2.js → comment-7IQ6ZOJF.js} +30 -25
  20. package/dist/{company-F2AZTDPK.js → company-RD7RDGSA.js} +58 -53
  21. package/dist/{config-K4G3VSBA.js → config-EYBNYRGK.js} +13 -5
  22. package/dist/{connect-TX6PT7NV.js → connect-HVXT67A6.js} +42 -38
  23. package/dist/core-6XYGUNAY.js +46 -0
  24. package/dist/{doctor-USTZQ75D.js → doctor-HUXQERLQ.js} +9 -5
  25. package/dist/document-AUUCGST2.js +27 -0
  26. package/dist/draft-DFO22K6Q.js +463 -0
  27. package/dist/examples-64YT5V5K.js +53 -0
  28. package/dist/{exit-codes-TMAIV7EM.js → exit-codes-AW6KHDDN.js} +1 -1
  29. package/dist/{feed-ANBPRGFQ.js → feed-JWP6ANPI.js} +15 -11
  30. package/dist/{group-HFF7LDDQ.js → group-SIQFJEZV.js} +17 -13
  31. package/dist/{inbox-XQMGW6RT.js → inbox-MMIMCA5O.js} +23 -19
  32. package/dist/{inboxes-CILMIVVD.js → inboxes-RND3D4C7.js} +18 -14
  33. package/dist/{job-TOJDDJ2P.js → job-ACFKBLFK.js} +31 -27
  34. package/dist/{login-OHAHNBRW.js → login-ZOB5KVKQ.js} +10 -5
  35. package/dist/{message-WCBNBPAJ.js → message-OFK6UVXR.js} +10 -8
  36. package/dist/{notification-CJ3LEHFL.js → notification-KKGAZU7M.js} +19 -15
  37. package/dist/{post-OQWJRL4B.js → post-A5SBCFB2.js} +36 -31
  38. package/dist/{profile-GT6ZD37M.js → profile-4SOOQZ4K.js} +52 -48
  39. package/dist/{recruiter-ZKWG6QG3.js → recruiter-YN73STDP.js} +125 -122
  40. package/dist/{sales-nav-WV3YHYD6.js → sales-nav-JXF5RY2K.js} +41 -35
  41. package/dist/{search-VAZEQ2WJ.js → search-JAL242A2.js} +68 -58
  42. package/dist/{setup-GGXMHXAF.js → setup-WICWH4JG.js} +14 -9
  43. package/dist/{webhook-5M47UX6U.js → webhook-UGKVYWBC.js} +40 -42
  44. package/package.json +2 -2
  45. package/dist/chunk-KJ24DIAJ.js +0 -60
  46. package/dist/examples-IJL3A6SZ.js +0 -18
package/README.md CHANGED
@@ -54,7 +54,7 @@ active profile, base URL, which precedence tier the credential came from
54
54
  connected accounts with their status. It exits `0` when every check passes and
55
55
  with the first failing check's code otherwise.
56
56
 
57
- `doctor` also names the workspace the credential belongs to, but only when the
57
+ `curviate doctor` also names the workspace the credential belongs to, but only when the
58
58
  key it resolved is one `curviate setup` wrote to a profile. A key from
59
59
  `CURVIATE_API_KEY` or `--api-key` may belong to another workspace entirely, so
60
60
  it is reported as unknown rather than guessed at.
@@ -110,6 +110,15 @@ Global flags available on every command:
110
110
  --timeout Request timeout in milliseconds (default: 30000)
111
111
  ```
112
112
 
113
+ Every LinkedIn action (profiles, companies, jobs, invitations, search, inboxes,
114
+ messages, posts, comments, Sales Navigator, Recruiter, groups, feed, LinkedIn
115
+ notification cards, drafts) is under `curviate core`: one action now, from one
116
+ account. `curviate core` lists them. Setup, accounts and webhooks stay at the top
117
+ level. Pre-0.48.0 paths without `curviate core` exit 2 and send nothing.
118
+
119
+ Documents go in files, never on the command line: `--file <path>`, or `--file -`
120
+ with a heredoc or a pipe.
121
+
113
122
  For full command reference see [docs.curviate.com](https://docs.curviate.com).
114
123
 
115
124
  ## Examples
@@ -119,15 +128,15 @@ These examples show how coding agents compose the CLI in real workflows.
119
128
  ### 1. Find people and send connection requests
120
129
 
121
130
  Search for matching profiles, preview the invitations, then send them once satisfied.
122
- `--location` on `search people` takes location **ids**, not free text; resolve a
123
- human-readable place name to an id first with `curviate search parameters --type LOCATION`:
131
+ `--location` on `curviate core search people` takes location **ids**, not free text; resolve a
132
+ human-readable place name to an id first with `curviate core search parameters --type LOCATION`:
124
133
 
125
134
  ```bash
126
- curviate search parameters --type LOCATION --keywords "Berlin" --account acc_1 --json
135
+ curviate core search parameters --type LOCATION --keywords "Berlin" --account acc_1 --json
127
136
  # {"items":[{"id":"103035651","name":"Berlin, Germany"}, {"id":"106967730","name":"Berlin, Berlin, Germany"}, ...]}
128
137
 
129
138
  # Look first, a search is a read, so it just runs (no --preview on reads)
130
- curviate search people \
139
+ curviate core search people \
131
140
  --keywords "AI engineer" \
132
141
  --location 103035651 \
133
142
  --account acc_1 \
@@ -135,12 +144,12 @@ curviate search people \
135
144
  --json
136
145
 
137
146
  # Preview a single write before sending, then pipe IDs into connect, one request per person
138
- curviate connect "$SOME_ID" --account acc_1 --note "Hi, I'd love to connect." --preview
147
+ curviate core connect "$SOME_ID" --account acc_1 --note "Hi, I'd love to connect." --preview
139
148
 
140
- curviate search people --keywords "AI engineer" --location 103035651 --account acc_1 --all \
149
+ curviate core search people --keywords "AI engineer" --location 103035651 --account acc_1 --all \
141
150
  | jq -r '.id' \
142
151
  | head -5 \
143
- | xargs -I{} curviate connect {} --account acc_1 --note "Hi, I'd love to connect."
152
+ | xargs -I{} curviate core connect {} --account acc_1 --note "Hi, I'd love to connect."
144
153
  ```
145
154
 
146
155
  ### 2. Triage the inbox and extract unread threads
@@ -155,18 +164,18 @@ human-readable sender comes from the chat's own `user.display_name` instead (pre
155
164
  1:1 chats):
156
165
 
157
166
  ```bash
158
- curviate inbox list --json --all --account acc_1 \
167
+ curviate core inbox list --json --all --account acc_1 \
159
168
  | jq -c 'select(.unread_count > 0) | {chat_id: .id, sender: (.user.display_name // .last_message.sender_id), preview: .last_message.text[0:80]}'
160
169
  ```
161
170
 
162
- `inbox list` reads one folder per call, `primary` by default. An archived chat never appears
171
+ `curviate core inbox list` reads one folder per call, `primary` by default. An archived chat never appears
163
172
  in a `primary` walk, no matter the `--limit` or how far `--cursor`/`--all` page through it;
164
- pass `--inbox archived` to reach it. `inmail` and `starred` are alternate views over chats
173
+ pass `--inbox archived` to reach it. `--inbox inmail` and `--inbox starred` are alternate views over chats
165
174
  `primary` already returns, useful as a narrower filter rather than for reachability. All six
166
- values: `primary`, `inmail`, `archived`, `spam`, `jobs`, `starred`.
175
+ values: `--inbox primary|inmail|archived|spam|jobs|starred`.
167
176
 
168
177
  ```bash
169
- curviate inbox list --json --all --account acc_1 --inbox archived
178
+ curviate core inbox list --json --all --account acc_1 --inbox archived
170
179
  ```
171
180
 
172
181
  ### 3. Warm up a prospect by reacting to their recent posts
@@ -178,9 +187,9 @@ envelope, not a bare array:
178
187
  ```bash
179
188
  PROFILE_URL="https://www.linkedin.com/in/example"
180
189
 
181
- curviate profile "$PROFILE_URL" --posts --fields id --account acc_1 --json \
190
+ curviate core profile "$PROFILE_URL" --posts --fields id --account acc_1 --json \
182
191
  | jq -r '.items[].id' \
183
- | xargs -I{} curviate post react {} --account acc_1 --reaction like
192
+ | xargs -I{} curviate core post react {} --account acc_1 --reaction like
184
193
  ```
185
194
 
186
195
  ### 4. Check entitlement before a Sales Navigator sweep
@@ -192,7 +201,7 @@ Navigator subscription) or `BETA_NOT_ENABLED` (the workspace has not opted into
192
201
  Branch on the exit code for the retry decision and read the code for the remedy:
193
202
 
194
203
  ```bash
195
- curviate sales-nav search people --keywords "VP Engineering" --account acc_1 --json \
204
+ curviate core sales-nav search people --keywords "VP Engineering" --account acc_1 --json \
196
205
  || {
197
206
  code=$?
198
207
  if [ "$code" -eq 5 ]; then
@@ -214,7 +223,7 @@ cat webhook-payload.json \
214
223
  | curviate webhook verify \
215
224
  --secret "$CURVIATE_WEBHOOK_SECRET" \
216
225
  --header "$CURVIATE_SIG_HEADER" \
217
- --body -
226
+ --file -
218
227
  ```
219
228
 
220
229
  Exit `0` means the signature is valid and the parsed event is written to stdout as JSON.
@@ -234,42 +243,75 @@ curviate account list --all --json \
234
243
 
235
244
  ### 7. Search jobs, then fetch full detail on the top result
236
245
 
237
- `job get` accepts either a job URL or the bare numeric id, including the `job_urn` field a
246
+ `curviate core job get` accepts either a job URL or the bare numeric id, including the `job_urn` field a
238
247
  job-search result already returns:
239
248
 
240
249
  ```bash
241
- curviate search jobs --keywords "founding engineer" --location "Berlin" --account acc_1 --json \
250
+ curviate core search jobs --keywords "founding engineer" --location "Berlin" --account acc_1 --json \
242
251
  | jq -r '.items[0].job_urn' \
243
- | xargs -I{} curviate job get {} --account acc_1 --json
252
+ | xargs -I{} curviate core job get {} --account acc_1 --json
244
253
 
245
254
  # A pasted job URL works identically:
246
- curviate job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1
255
+ curviate core job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1
247
256
  ```
248
257
 
249
258
  ## Company
250
259
 
251
- Company commands (`curviate company ...`) are Core-tier reads. `company <id>` accepts a public
260
+ Company commands (`curviate core company ...`) are Core-tier reads. `curviate core company <id>` accepts a public
252
261
  handle (the slug in `linkedin.com/company/<handle>`) or a numeric id; the four sub-resource
253
- commands require the company's **numeric provider id**, the `id` field `company <id>` returns.
262
+ commands require the company's **numeric provider id**, the `id` field `curviate core company <id>` returns.
254
263
  `--account` (or a configured default account) is required on all of them, unless exactly one account is connected.
255
264
 
256
265
  ### 1. Retrieve a company, then list its employees
257
266
 
258
267
  ```bash
259
- curviate company t-systems --account acc_1 --json | jq -r '.id' \
260
- | xargs -I{} curviate company employees {} --keywords "engineer" --limit 10 --account acc_1 --json
268
+ curviate core company t-systems --account acc_1 --json | jq -r '.id' \
269
+ | xargs -I{} curviate core company employees {} --keywords "engineer" --limit 10 --account acc_1 --json
261
270
  ```
262
271
 
263
272
  ### 2. Page through a company's posts and jobs
264
273
 
265
274
  ```bash
266
- curviate company posts 112013061 --limit 5 --account acc_1 --json
267
- curviate company jobs 112013061 --all --account acc_1 --json # streams every page
275
+ curviate core company posts 112013061 --limit 5 --account acc_1 --json
276
+ curviate core company jobs 112013061 --all --account acc_1 --json # streams every page
277
+ ```
278
+
279
+ ## Drafts and scheduled posts
280
+
281
+ A Draft is a stored, editable, unpublished post. Give it an account and `--schedule-at` and Curviate publishes it at that time. Drafts are tenant-wide: `--account` is optional and is never defaulted from your config, so a Draft you create without it has no account yet. `curviate core post create` still publishes immediately and does not schedule.
282
+
283
+ ### 1. Draft a post, schedule it, change your mind
284
+
285
+ ```bash
286
+ curviate core draft create "Three things we learned shipping our first agent integration." --account acc_1 --schedule-at 2026-10-12T09:00:00+02:00 --json
287
+ curviate core draft update drf_1 --unschedule --json # back to a plain Draft
288
+ curviate core draft publish drf_1 --json # or publish now: prints the post id
289
+ ```
290
+
291
+ `--schedule-at` is an ISO 8601 time with an offset, 5 minutes to 365 days ahead, passed to the API unchanged. Two scheduled Drafts on one account must be at least 5 minutes apart.
292
+
293
+ ### 2. Attach media
294
+
295
+ ```sh
296
+ curviate core draft create "Launch day." --account acc_1 --attach shot1.png --attach shot2.png --json
297
+ curviate core draft update drf_1 --attach demo.pdf --json # appends; existing files stay
298
+ ```
299
+
300
+ Up to 20 images (JPEG, PNG, GIF, WEBP, each up to 5 MiB), or one MP4 video, or one PDF (each up to 50 MiB), never mixed. An image over 5 MiB is refused before anything is sent. Files up to 5 MiB go inline in the request; larger ones are uploaded separately, in the order you gave them.
301
+
302
+ ### 3. List what is queued, and what went out
303
+
304
+ ```bash
305
+ curviate core draft list --status scheduled --account acc_1 --order asc --json
306
+ curviate core draft list --status published --from 2026-10-01T00:00:00Z --json # publish records, not Drafts
307
+ curviate core draft list --account none --all --json # Drafts with no account, every page
268
308
  ```
269
309
 
310
+ A scheduled post that fails to publish becomes a `failed` Draft with a `failure` code; any `curviate core draft update` on it clears the failure. Failed `outcome_unknown` means the post may be live: check the account's posts before retrying.
311
+
270
312
  ## Sales Navigator
271
313
 
272
- Sales Navigator commands (`curviate sales-nav ...`) are **beta**: this surface has not been
314
+ Sales Navigator commands (`curviate core sales-nav ...`) are **beta**: this surface has not been
273
315
  exercised against a real Sales Navigator subscription yet, so its responses may still move.
274
316
 
275
317
  There is no Sales Navigator add-on to buy from Curviate and no tier on a seat: one ordinary
@@ -279,18 +321,18 @@ the JSON body: `NO_ACTIVE_SEAT` (no Curviate seat covers the account, fix it in
279
321
  `LINKEDIN_FEATURE_NOT_SUBSCRIBED` (the LinkedIn account lacks the subscription, fix it on
280
322
  LinkedIn) or `BETA_NOT_ENABLED` (a human enables beta in Settings, or pass `--beta` for this
281
323
  call). Branch on the exit code the same way as example 4 above, and read the code for the
282
- remedy. Write commands (`save-lead`, `save-account`, `message new`) accept `--preview` to
324
+ remedy. Write commands (`curviate core sales-nav save-lead`, `curviate core sales-nav save-account`, `curviate core sales-nav message new`) accept `--preview` to
283
325
  render the request without sending it.
284
326
 
285
327
  ### 1. Search Sales Navigator profiles, then get one full profile
286
328
 
287
329
  ```bash
288
- curviate sales-nav search people \
330
+ curviate core sales-nav search people \
289
331
  --keywords "VP Engineering" \
290
332
  --account acc_1 \
291
333
  --limit 5 \
292
334
  | jq -r '.items[0].id' \
293
- | xargs -I{} curviate sales-nav profile {} --account acc_1
335
+ | xargs -I{} curviate core sales-nav profile {} --account acc_1
294
336
  ```
295
337
 
296
338
  ### 2. Save a lead to a specific lead list
@@ -298,12 +340,12 @@ curviate sales-nav search people \
298
340
  Preview first, then send. `--list` is required; the save always targets a specific list.
299
341
 
300
342
  ```bash
301
- curviate sales-nav save-lead ACwAAA1234567 \
343
+ curviate core sales-nav save-lead ACwAAA1234567 \
302
344
  --account acc_1 \
303
345
  --list 987654 \
304
346
  --preview
305
347
 
306
- curviate sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
348
+ curviate core sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
307
349
  ```
308
350
 
309
351
  ### 3. Start a new Sales Navigator chat
@@ -311,7 +353,7 @@ curviate sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
311
353
  `--subject` is required for Sales Navigator messaging.
312
354
 
313
355
  ```bash
314
- curviate sales-nav message new \
356
+ curviate core sales-nav message new \
315
357
  --to ACwAAA1234567 \
316
358
  --account acc_1 \
317
359
  --subject "An opportunity at our company" \
@@ -321,7 +363,7 @@ curviate sales-nav message new \
321
363
  ### 4. Search Sales Navigator companies
322
364
 
323
365
  ```bash
324
- curviate sales-nav search companies \
366
+ curviate core sales-nav search companies \
325
367
  --keywords "series B fintech" \
326
368
  --account acc_1 \
327
369
  --limit 5 --json \
@@ -331,14 +373,14 @@ curviate sales-nav search companies \
331
373
  ### 5. List saved-account and saved-lead lists
332
374
 
333
375
  ```bash
334
- curviate sales-nav account-lists --account acc_1
335
- curviate sales-nav lead-lists --account acc_1
376
+ curviate core sales-nav account-lists --account acc_1
377
+ curviate core sales-nav lead-lists --account acc_1
336
378
  ```
337
379
 
338
380
  ### 6. Browse a saved-account list, filtered to starred accounts
339
381
 
340
382
  ```bash
341
- curviate sales-nav browse-account-list 987654 \
383
+ curviate core sales-nav browse-account-list 987654 \
342
384
  --account acc_1 \
343
385
  --filter STARRED \
344
386
  --sort-by NAME \
@@ -349,7 +391,7 @@ curviate sales-nav browse-account-list 987654 \
349
391
  ### 7. Browse a saved-lead list, spotlighting recent job changes
350
392
 
351
393
  ```bash
352
- curviate sales-nav browse-lead-list 456789 \
394
+ curviate core sales-nav browse-lead-list 456789 \
353
395
  --account acc_1 \
354
396
  --spotlight RECENT_POSITION_CHANGE \
355
397
  --json \
@@ -359,17 +401,17 @@ curviate sales-nav browse-lead-list 456789 \
359
401
  ### 8. Save a company into an account list
360
402
 
361
403
  ```bash
362
- curviate sales-nav save-account 112013061 \
404
+ curviate core sales-nav save-account 112013061 \
363
405
  --account acc_1 \
364
406
  --list 987654 \
365
407
  --preview
366
408
 
367
- curviate sales-nav save-account 112013061 --account acc_1 --list 987654
409
+ curviate core sales-nav save-account 112013061 --account acc_1 --list 987654
368
410
  ```
369
411
 
370
412
  ## Recruiter
371
413
 
372
- Recruiter commands (`curviate recruiter ...`) are **beta**: this surface has not been exercised
414
+ Recruiter commands (`curviate core recruiter ...`) are **beta**: this surface has not been exercised
373
415
  against a real Recruiter subscription yet, so its responses may still move.
374
416
 
375
417
  There is no Recruiter add-on to buy from Curviate and no tier on a seat: one ordinary paid seat
@@ -379,42 +421,46 @@ subscription. A refusal is **exit code `5`** with one of three codes in the JSON
379
421
  `LINKEDIN_FEATURE_NOT_SUBSCRIBED` (the LinkedIn account lacks the subscription, fix it on
380
422
  LinkedIn) or `BETA_NOT_ENABLED` (a human enables beta in Settings, or pass `--beta` for this
381
423
  call). The surface is project-centric: most
382
- operations are scoped to a hiring project id. Write commands (`save-candidate`, `project update`,
383
- `project-job create`/`update`, `job create`/`publish`/`close`, `message new`) accept `--preview`
424
+ operations are scoped to a hiring project id. Write commands (`curviate core recruiter save-candidate`, `curviate core recruiter project update`,
425
+ `curviate core recruiter project-job create`, `curviate core recruiter project-job update`, `curviate core recruiter job create`,
426
+ `curviate core recruiter job publish`, `curviate core recruiter job close`, `curviate core recruiter message new`) accept `--preview`
384
427
  to render the request without sending it.
385
428
 
386
429
  ### 1. List hiring projects
387
430
 
388
431
  ```bash
389
- curviate recruiter projects --account acc_1 --limit 20 --json \
432
+ curviate core recruiter projects --account acc_1 --limit 20 --json \
390
433
  | jq -r '.items[] | "\(.id)\t\(.name)"'
391
434
  ```
392
435
 
393
436
  ### 2. Inspect a project, its pipeline, and its attached job posting
394
437
 
395
- `recruiter project-job get` returns the single job posting attached to a project (a
438
+ `curviate core recruiter project-job get` returns the single job posting attached to a project (a
396
439
  `RESOURCE_NOT_FOUND` / exit `4` when none is attached).
397
440
 
398
441
  ```bash
399
- curviate recruiter project "$PROJECT_ID" --account acc_1 --json
400
- curviate recruiter pipeline "$PROJECT_ID" --account acc_1 --json
401
- curviate recruiter project-job get "$PROJECT_ID" --account acc_1 --json
442
+ curviate core recruiter project "$PROJECT_ID" --account acc_1 --json
443
+ curviate core recruiter pipeline "$PROJECT_ID" --account acc_1 --json
444
+ curviate core recruiter project-job get "$PROJECT_ID" --account acc_1 --json
402
445
  ```
403
446
 
404
447
  ### 3. Create a job posting draft, then publish it
405
448
 
406
- `recruiter job create` requires `--project-name` (the hiring project the posting opens) plus the
407
- full v2 job body: `--job-title`, `--company-id`/`--company-name`, `--workplace-type`, `--location`,
449
+ `curviate core recruiter job create` requires `--project-name` (the hiring project the posting opens) plus the
450
+ full v2 job body: `--job-title-id` with `--job-title`, `--company-id`/`--company-name`, `--workplace-type`, `--location`,
408
451
  `--employment-status`, `--seniority-level`, `--description` (200 characters minimum), `--industry`,
409
- `--job-function`, and `--apply-method`. `--location`/`--industry`/`--job-function` take resolved
410
- parameter ids, the same `search parameters --type LOCATION`/`--type INDUSTRY`/`--type JOB_FUNCTION`
411
- resolution from example 1 above. `recruiter job publish` is project-scoped and requires `--mode`
452
+ `--job-function`, and `--apply-method` (with `--notification-email` or `--website-url`), from flags or a
453
+ `--file <path|->` JSON document; the CLI checks the merged body against the published schema before
454
+ sending and lists every problem at once. `--location`/`--industry`/`--job-function` take resolved
455
+ parameter ids, the same `curviate core search parameters --type LOCATION`/`--type INDUSTRY`/`--type JOB_FUNCTION`
456
+ resolution from example 1 above. `curviate core recruiter job publish` is project-scoped and requires `--mode`
412
457
  (`FREE | PROMOTED | PROMOTED_PLUS`); the paid modes also require the full `--budget-*` triple.
413
458
 
414
459
  ```bash
415
- curviate recruiter job create \
460
+ curviate core recruiter job create \
416
461
  --account acc_1 \
417
462
  --project-name "Backend Hiring 2026" \
463
+ --job-title-id 9 \
418
464
  --job-title "Senior Backend Engineer" \
419
465
  --company-name "Curviate GmbH" \
420
466
  --workplace-type REMOTE \
@@ -425,32 +471,33 @@ curviate recruiter job create \
425
471
  --industry 96 \
426
472
  --job-function 15 \
427
473
  --apply-method linkedin \
474
+ --notification-email jobs@example.com \
428
475
  --json
429
476
 
430
- curviate recruiter job publish "$PROJECT_ID" "$JOB_ID" --account acc_1 --mode FREE --json
477
+ curviate core recruiter job publish "$PROJECT_ID" "$JOB_ID" --account acc_1 --mode FREE --json
431
478
  ```
432
479
 
433
480
  ### 4. List applicants in a project, then get one applicant's detail
434
481
 
435
- `recruiter applicants` is project-scoped and requires `--channel-id` (the project's own
482
+ `curviate core recruiter applicants` is project-scoped and requires `--channel-id` (the project's own
436
483
  JOB_POSTING talent-pool channel). Applicant detail and résumé are also project-scoped.
437
484
 
438
485
  ```bash
439
- curviate recruiter applicants "$PROJECT_ID" --channel-id "$CHANNEL_ID" --account acc_1 --limit 10 --json \
486
+ curviate core recruiter applicants "$PROJECT_ID" --channel-id "$CHANNEL_ID" --account acc_1 --limit 10 --json \
440
487
  | jq -r '.items[0].id' \
441
- | xargs -I{} curviate recruiter applicant "$PROJECT_ID" {} --account acc_1
488
+ | xargs -I{} curviate core recruiter applicant "$PROJECT_ID" {} --account acc_1
442
489
  ```
443
490
 
444
491
  ### 5. Download an applicant's resume
445
492
 
446
493
  ```bash
447
- curviate recruiter applicant resume "$PROJECT_ID" APPLICANT_ID --account acc_1 -o resume.pdf
494
+ curviate core recruiter applicant resume "$PROJECT_ID" APPLICANT_ID --account acc_1 -o resume.pdf
448
495
  ```
449
496
 
450
497
  ### 6. Save a candidate to a project pipeline stage
451
498
 
452
499
  ```bash
453
- curviate recruiter save-candidate "$PROJECT_ID" \
500
+ curviate core recruiter save-candidate "$PROJECT_ID" \
454
501
  --account acc_1 \
455
502
  --stage-id "$STAGE_ID" \
456
503
  --candidate-id AEM789
@@ -459,24 +506,24 @@ curviate recruiter save-candidate "$PROJECT_ID" \
459
506
  ### 7. Search Recruiter people
460
507
 
461
508
  ```bash
462
- curviate recruiter search people \
509
+ curviate core recruiter search people \
463
510
  --keywords "senior backend engineer" \
464
511
  --account acc_1 \
465
512
  --limit 5 --json \
466
513
  | jq -r '.items[] | "\(.id)\t\(.full_name // .headline)"'
467
514
 
468
515
  # A pasted Recruiter search / talent-pool URL runs directly:
469
- curviate recruiter search "https://www.linkedin.com/talent/search?..." --account acc_1 --json
516
+ curviate core recruiter search "https://www.linkedin.com/talent/search?..." --account acc_1 --json
470
517
  ```
471
518
 
472
519
  ### 8. Get a Recruiter-enriched profile, then start a chat with them
473
520
 
474
- `recruiter message new` is JSON-only and requires `--subject` and `--signature`.
521
+ `curviate core recruiter message new` is JSON-only and requires `--subject` and `--signature`.
475
522
 
476
523
  ```bash
477
- curviate recruiter profile "https://www.linkedin.com/in/example" --account acc_1 --json
524
+ curviate core recruiter profile "https://www.linkedin.com/in/example" --account acc_1 --json
478
525
 
479
- curviate recruiter message new \
526
+ curviate core recruiter message new \
480
527
  --to AEM789 \
481
528
  --account acc_1 \
482
529
  --subject "A role you'd be a great fit for" \
@@ -486,15 +533,15 @@ curviate recruiter message new \
486
533
 
487
534
  ### 9. List your postings, and get any public job posting through the Recruiter lens
488
535
 
489
- Unlike `recruiter jobs` (which lists postings you manage), `recruiter job get` retrieves the full
536
+ Unlike `curviate core recruiter jobs` (which lists postings you manage), `curviate core recruiter job get` retrieves the full
490
537
  detail of *any* public LinkedIn job posting, the Recruiter-seated counterpart to the top-level
491
- `job get` command:
538
+ `curviate core job get` command:
492
539
 
493
540
  ```bash
494
- curviate recruiter jobs --account acc_1 --limit 10 --json \
541
+ curviate core recruiter jobs --account acc_1 --limit 10 --json \
495
542
  | jq -r '.items[] | "\(.id)\t\(.title)\t\(.state)"'
496
543
 
497
- curviate recruiter job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1 --json
544
+ curviate core recruiter job get "https://www.linkedin.com/jobs/view/4428113858" --account acc_1 --json
498
545
  ```
499
546
 
500
547
  ## Retrieval modes
@@ -517,7 +564,7 @@ threshold: that combination is a usage error (exit `2`) before any request is
517
564
  sent.
518
565
 
519
566
  Available on the four reads that can be served from a stored copy:
520
- `profile <id>`, `profile me`, `inbox get` and `inbox messages`. The activity
567
+ `curviate core profile <id>`, `curviate core profile me`, `curviate core inbox get` and `curviate core inbox messages`. The activity
521
568
  listings on the profile commands (`--posts`, `--comments`, `--reactions`,
522
569
  `--followers`) do not accept them and reject them with exit `2`.
523
570
 
@@ -540,28 +587,28 @@ this API simply holds no copy, so re-checking the id is the wrong move. It is
540
587
  not a failure either. The fix is another mode, and it is never worth retrying
541
588
  as sent, because the answer cannot change until you change the mode.
542
589
 
543
- `inbox messages` is the strictest case. The store answers it only for an
590
+ `curviate core inbox messages` is the strictest case. The store answers it only for an
544
591
  unfiltered, uncursored first page, only after a walk of the whole chat reached
545
592
  its end, and only when the chat's whole message set fits in that one page
546
593
  (`--limit`, at most 25). Any unfiltered page fetched from LinkedIn (such as
547
594
  `--mode live` without `--all`) restarts the walk, and
548
- `inbox messages <chat_id> --all` walks to the end and closes it. A read
595
+ `curviate core inbox messages <chat_id> --all` walks to the end and closes it. A read
549
596
  carrying `--before`, `--after` or `--cursor` is never served from the store and
550
597
  `--all` does not change that, so a chat with more messages than one page holds
551
598
  exits `14` under `--mode cache_only` however it is walked.
552
599
 
553
600
  ```bash
554
601
  # The default: a fresh stored copy if there is one, otherwise fetch
555
- curviate profile me --account acc_1 --json
602
+ curviate core profile me --account acc_1 --json
556
603
 
557
604
  # Serve whatever is stored at any age, and fetch only if nothing is
558
- curviate profile me --account acc_1 --mode refill --json
605
+ curviate core profile me --account acc_1 --mode refill --json
559
606
 
560
607
  # Accept a stored copy up to five minutes old, otherwise fetch
561
- curviate profile me --account acc_1 --max-age 300 --fields first_name,source,observed_at --json
608
+ curviate core profile me --account acc_1 --max-age 300 --fields first_name,source,observed_at --json
562
609
 
563
610
  # A single chat from the store, never LinkedIn. Exit 14 if nothing is stored.
564
- curviate inbox get 2-AbCdEf== --account acc_1 --mode cache_only --json
611
+ curviate core inbox get 2-AbCdEf== --account acc_1 --mode cache_only --json
565
612
  ```
566
613
 
567
614
  ## Exit codes