@curviate/cli 0.47.0 → 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.
- package/CHANGELOG.md +174 -1
- package/README.md +101 -87
- package/dist/{account-RFJ63QYL.js → account-WKQHMM7P.js} +39 -29
- package/dist/chunk-AYKKXGTR.js +1141 -0
- package/dist/{chunk-TC4ZPUWI.js → chunk-CVMSQ3OF.js} +19 -80
- package/dist/{chunk-HOQ7EUHJ.js → chunk-FDJMAF7D.js} +1 -0
- package/dist/chunk-GQKC6E5K.js +36 -0
- package/dist/{chunk-V3MVOVQT.js → chunk-MKGVNDMJ.js} +8 -1
- package/dist/chunk-NNV2OYEF.js +23 -0
- package/dist/{chunk-UJOTQPL6.js → chunk-OHXYFICP.js} +47 -14
- package/dist/{chunk-PD2I5TYC.js → chunk-Q63IIPL2.js} +2 -2
- package/dist/chunk-TSOIZBBU.js +41 -0
- package/dist/{chunk-ERBYEC5P.js → chunk-Y7K4UBFC.js} +1 -1
- package/dist/{chunk-FXYK2GTO.js → chunk-YFXLXION.js} +37 -32
- package/dist/chunk-ZYURL5VK.js +83 -0
- package/dist/cli.js +76 -97
- package/dist/{comment-MCXE7B7V.js → comment-7IQ6ZOJF.js} +27 -22
- package/dist/{company-EUUN372H.js → company-RD7RDGSA.js} +55 -50
- package/dist/{config-K4G3VSBA.js → config-EYBNYRGK.js} +13 -5
- package/dist/{connect-2AL7XVJO.js → connect-HVXT67A6.js} +35 -31
- package/dist/core-6XYGUNAY.js +46 -0
- package/dist/{doctor-WPYI7X2T.js → doctor-HUXQERLQ.js} +8 -4
- package/dist/document-AUUCGST2.js +27 -0
- package/dist/{draft-G65DVXT7.js → draft-DFO22K6Q.js} +26 -21
- package/dist/examples-64YT5V5K.js +53 -0
- package/dist/{feed-HV24WME4.js → feed-JWP6ANPI.js} +13 -9
- package/dist/{group-HADXNVJW.js → group-SIQFJEZV.js} +15 -11
- package/dist/{inbox-G3EE54OB.js → inbox-MMIMCA5O.js} +21 -17
- package/dist/{inboxes-237XOBTP.js → inboxes-RND3D4C7.js} +16 -12
- package/dist/{job-LIN6RWD7.js → job-ACFKBLFK.js} +29 -25
- package/dist/{login-OHAHNBRW.js → login-ZOB5KVKQ.js} +10 -5
- package/dist/{message-U2O2JQSW.js → message-OFK6UVXR.js} +9 -7
- package/dist/{notification-3VG32LWM.js → notification-KKGAZU7M.js} +17 -13
- package/dist/{post-ECDK2KJL.js → post-A5SBCFB2.js} +33 -28
- package/dist/{profile-JOHS6SDW.js → profile-4SOOQZ4K.js} +45 -41
- package/dist/{recruiter-7VXEIXN3.js → recruiter-YN73STDP.js} +123 -120
- package/dist/{sales-nav-K4BMBH7R.js → sales-nav-JXF5RY2K.js} +38 -32
- package/dist/{search-C2UYO6PI.js → search-JAL242A2.js} +58 -48
- package/dist/{setup-GYEZFDEN.js → setup-WICWH4JG.js} +13 -8
- package/dist/{webhook-KCOQOH7D.js → webhook-UGKVYWBC.js} +34 -36
- package/package.json +1 -1
- package/dist/chunk-KJ24DIAJ.js +0 -60
- 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.
|
|
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:
|
|
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
|
-
--
|
|
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,49 +243,49 @@ 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
|
|
268
277
|
```
|
|
269
278
|
|
|
270
279
|
## Drafts and scheduled posts
|
|
271
280
|
|
|
272
|
-
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 post create` still publishes immediately and does not schedule.
|
|
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.
|
|
273
282
|
|
|
274
283
|
### 1. Draft a post, schedule it, change your mind
|
|
275
284
|
|
|
276
285
|
```bash
|
|
277
|
-
curviate draft create "Three things we learned shipping our first agent integration." --account acc_1 --schedule-at 2026-10-12T09:00:00+02:00 --json
|
|
278
|
-
curviate draft update drf_1 --unschedule --json # back to a plain Draft
|
|
279
|
-
curviate draft publish drf_1 --json # or publish now: prints the post id
|
|
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
|
|
280
289
|
```
|
|
281
290
|
|
|
282
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.
|
|
@@ -284,8 +293,8 @@ curviate draft publish drf_1 --json # or publish now: pri
|
|
|
284
293
|
### 2. Attach media
|
|
285
294
|
|
|
286
295
|
```sh
|
|
287
|
-
curviate draft create "Launch day." --account acc_1 --attach shot1.png --attach shot2.png --json
|
|
288
|
-
curviate draft update drf_1 --attach demo.pdf --json # appends; existing files stay
|
|
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
|
|
289
298
|
```
|
|
290
299
|
|
|
291
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.
|
|
@@ -293,16 +302,16 @@ Up to 20 images (JPEG, PNG, GIF, WEBP, each up to 5 MiB), or one MP4 video, or o
|
|
|
293
302
|
### 3. List what is queued, and what went out
|
|
294
303
|
|
|
295
304
|
```bash
|
|
296
|
-
curviate draft list --status scheduled --account acc_1 --order asc --json
|
|
297
|
-
curviate draft list --status published --from 2026-10-01T00:00:00Z --json # publish records, not Drafts
|
|
298
|
-
curviate draft list --account none --all --json # Drafts with no account, every page
|
|
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
|
|
299
308
|
```
|
|
300
309
|
|
|
301
|
-
A scheduled post that fails to publish becomes a `failed` Draft with a `failure` code; any `draft update` on it clears the failure. Failed `outcome_unknown` means the post may be live: check the account's posts before retrying.
|
|
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.
|
|
302
311
|
|
|
303
312
|
## Sales Navigator
|
|
304
313
|
|
|
305
|
-
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
|
|
306
315
|
exercised against a real Sales Navigator subscription yet, so its responses may still move.
|
|
307
316
|
|
|
308
317
|
There is no Sales Navigator add-on to buy from Curviate and no tier on a seat: one ordinary
|
|
@@ -312,18 +321,18 @@ the JSON body: `NO_ACTIVE_SEAT` (no Curviate seat covers the account, fix it in
|
|
|
312
321
|
`LINKEDIN_FEATURE_NOT_SUBSCRIBED` (the LinkedIn account lacks the subscription, fix it on
|
|
313
322
|
LinkedIn) or `BETA_NOT_ENABLED` (a human enables beta in Settings, or pass `--beta` for this
|
|
314
323
|
call). Branch on the exit code the same way as example 4 above, and read the code for the
|
|
315
|
-
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
|
|
316
325
|
render the request without sending it.
|
|
317
326
|
|
|
318
327
|
### 1. Search Sales Navigator profiles, then get one full profile
|
|
319
328
|
|
|
320
329
|
```bash
|
|
321
|
-
curviate sales-nav search people \
|
|
330
|
+
curviate core sales-nav search people \
|
|
322
331
|
--keywords "VP Engineering" \
|
|
323
332
|
--account acc_1 \
|
|
324
333
|
--limit 5 \
|
|
325
334
|
| jq -r '.items[0].id' \
|
|
326
|
-
| xargs -I{} curviate sales-nav profile {} --account acc_1
|
|
335
|
+
| xargs -I{} curviate core sales-nav profile {} --account acc_1
|
|
327
336
|
```
|
|
328
337
|
|
|
329
338
|
### 2. Save a lead to a specific lead list
|
|
@@ -331,12 +340,12 @@ curviate sales-nav search people \
|
|
|
331
340
|
Preview first, then send. `--list` is required; the save always targets a specific list.
|
|
332
341
|
|
|
333
342
|
```bash
|
|
334
|
-
curviate sales-nav save-lead ACwAAA1234567 \
|
|
343
|
+
curviate core sales-nav save-lead ACwAAA1234567 \
|
|
335
344
|
--account acc_1 \
|
|
336
345
|
--list 987654 \
|
|
337
346
|
--preview
|
|
338
347
|
|
|
339
|
-
curviate sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
|
|
348
|
+
curviate core sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
|
|
340
349
|
```
|
|
341
350
|
|
|
342
351
|
### 3. Start a new Sales Navigator chat
|
|
@@ -344,7 +353,7 @@ curviate sales-nav save-lead ACwAAA1234567 --account acc_1 --list 987654
|
|
|
344
353
|
`--subject` is required for Sales Navigator messaging.
|
|
345
354
|
|
|
346
355
|
```bash
|
|
347
|
-
curviate sales-nav message new \
|
|
356
|
+
curviate core sales-nav message new \
|
|
348
357
|
--to ACwAAA1234567 \
|
|
349
358
|
--account acc_1 \
|
|
350
359
|
--subject "An opportunity at our company" \
|
|
@@ -354,7 +363,7 @@ curviate sales-nav message new \
|
|
|
354
363
|
### 4. Search Sales Navigator companies
|
|
355
364
|
|
|
356
365
|
```bash
|
|
357
|
-
curviate sales-nav search companies \
|
|
366
|
+
curviate core sales-nav search companies \
|
|
358
367
|
--keywords "series B fintech" \
|
|
359
368
|
--account acc_1 \
|
|
360
369
|
--limit 5 --json \
|
|
@@ -364,14 +373,14 @@ curviate sales-nav search companies \
|
|
|
364
373
|
### 5. List saved-account and saved-lead lists
|
|
365
374
|
|
|
366
375
|
```bash
|
|
367
|
-
curviate sales-nav account-lists --account acc_1
|
|
368
|
-
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
|
|
369
378
|
```
|
|
370
379
|
|
|
371
380
|
### 6. Browse a saved-account list, filtered to starred accounts
|
|
372
381
|
|
|
373
382
|
```bash
|
|
374
|
-
curviate sales-nav browse-account-list 987654 \
|
|
383
|
+
curviate core sales-nav browse-account-list 987654 \
|
|
375
384
|
--account acc_1 \
|
|
376
385
|
--filter STARRED \
|
|
377
386
|
--sort-by NAME \
|
|
@@ -382,7 +391,7 @@ curviate sales-nav browse-account-list 987654 \
|
|
|
382
391
|
### 7. Browse a saved-lead list, spotlighting recent job changes
|
|
383
392
|
|
|
384
393
|
```bash
|
|
385
|
-
curviate sales-nav browse-lead-list 456789 \
|
|
394
|
+
curviate core sales-nav browse-lead-list 456789 \
|
|
386
395
|
--account acc_1 \
|
|
387
396
|
--spotlight RECENT_POSITION_CHANGE \
|
|
388
397
|
--json \
|
|
@@ -392,17 +401,17 @@ curviate sales-nav browse-lead-list 456789 \
|
|
|
392
401
|
### 8. Save a company into an account list
|
|
393
402
|
|
|
394
403
|
```bash
|
|
395
|
-
curviate sales-nav save-account 112013061 \
|
|
404
|
+
curviate core sales-nav save-account 112013061 \
|
|
396
405
|
--account acc_1 \
|
|
397
406
|
--list 987654 \
|
|
398
407
|
--preview
|
|
399
408
|
|
|
400
|
-
curviate sales-nav save-account 112013061 --account acc_1 --list 987654
|
|
409
|
+
curviate core sales-nav save-account 112013061 --account acc_1 --list 987654
|
|
401
410
|
```
|
|
402
411
|
|
|
403
412
|
## Recruiter
|
|
404
413
|
|
|
405
|
-
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
|
|
406
415
|
against a real Recruiter subscription yet, so its responses may still move.
|
|
407
416
|
|
|
408
417
|
There is no Recruiter add-on to buy from Curviate and no tier on a seat: one ordinary paid seat
|
|
@@ -412,42 +421,46 @@ subscription. A refusal is **exit code `5`** with one of three codes in the JSON
|
|
|
412
421
|
`LINKEDIN_FEATURE_NOT_SUBSCRIBED` (the LinkedIn account lacks the subscription, fix it on
|
|
413
422
|
LinkedIn) or `BETA_NOT_ENABLED` (a human enables beta in Settings, or pass `--beta` for this
|
|
414
423
|
call). The surface is project-centric: most
|
|
415
|
-
operations are scoped to a hiring project id. Write commands (`save-candidate`, `project update`,
|
|
416
|
-
`project-job create
|
|
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`
|
|
417
427
|
to render the request without sending it.
|
|
418
428
|
|
|
419
429
|
### 1. List hiring projects
|
|
420
430
|
|
|
421
431
|
```bash
|
|
422
|
-
curviate recruiter projects --account acc_1 --limit 20 --json \
|
|
432
|
+
curviate core recruiter projects --account acc_1 --limit 20 --json \
|
|
423
433
|
| jq -r '.items[] | "\(.id)\t\(.name)"'
|
|
424
434
|
```
|
|
425
435
|
|
|
426
436
|
### 2. Inspect a project, its pipeline, and its attached job posting
|
|
427
437
|
|
|
428
|
-
`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
|
|
429
439
|
`RESOURCE_NOT_FOUND` / exit `4` when none is attached).
|
|
430
440
|
|
|
431
441
|
```bash
|
|
432
|
-
curviate recruiter project "$PROJECT_ID" --account acc_1 --json
|
|
433
|
-
curviate recruiter pipeline "$PROJECT_ID" --account acc_1 --json
|
|
434
|
-
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
|
|
435
445
|
```
|
|
436
446
|
|
|
437
447
|
### 3. Create a job posting draft, then publish it
|
|
438
448
|
|
|
439
|
-
`recruiter job create` requires `--project-name` (the hiring project the posting opens) plus the
|
|
440
|
-
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`,
|
|
441
451
|
`--employment-status`, `--seniority-level`, `--description` (200 characters minimum), `--industry`,
|
|
442
|
-
`--job-function`, and `--apply-method
|
|
443
|
-
|
|
444
|
-
|
|
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`
|
|
445
457
|
(`FREE | PROMOTED | PROMOTED_PLUS`); the paid modes also require the full `--budget-*` triple.
|
|
446
458
|
|
|
447
459
|
```bash
|
|
448
|
-
curviate recruiter job create \
|
|
460
|
+
curviate core recruiter job create \
|
|
449
461
|
--account acc_1 \
|
|
450
462
|
--project-name "Backend Hiring 2026" \
|
|
463
|
+
--job-title-id 9 \
|
|
451
464
|
--job-title "Senior Backend Engineer" \
|
|
452
465
|
--company-name "Curviate GmbH" \
|
|
453
466
|
--workplace-type REMOTE \
|
|
@@ -458,32 +471,33 @@ curviate recruiter job create \
|
|
|
458
471
|
--industry 96 \
|
|
459
472
|
--job-function 15 \
|
|
460
473
|
--apply-method linkedin \
|
|
474
|
+
--notification-email jobs@example.com \
|
|
461
475
|
--json
|
|
462
476
|
|
|
463
|
-
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
|
|
464
478
|
```
|
|
465
479
|
|
|
466
480
|
### 4. List applicants in a project, then get one applicant's detail
|
|
467
481
|
|
|
468
|
-
`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
|
|
469
483
|
JOB_POSTING talent-pool channel). Applicant detail and résumé are also project-scoped.
|
|
470
484
|
|
|
471
485
|
```bash
|
|
472
|
-
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 \
|
|
473
487
|
| jq -r '.items[0].id' \
|
|
474
|
-
| xargs -I{} curviate recruiter applicant "$PROJECT_ID" {} --account acc_1
|
|
488
|
+
| xargs -I{} curviate core recruiter applicant "$PROJECT_ID" {} --account acc_1
|
|
475
489
|
```
|
|
476
490
|
|
|
477
491
|
### 5. Download an applicant's resume
|
|
478
492
|
|
|
479
493
|
```bash
|
|
480
|
-
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
|
|
481
495
|
```
|
|
482
496
|
|
|
483
497
|
### 6. Save a candidate to a project pipeline stage
|
|
484
498
|
|
|
485
499
|
```bash
|
|
486
|
-
curviate recruiter save-candidate "$PROJECT_ID" \
|
|
500
|
+
curviate core recruiter save-candidate "$PROJECT_ID" \
|
|
487
501
|
--account acc_1 \
|
|
488
502
|
--stage-id "$STAGE_ID" \
|
|
489
503
|
--candidate-id AEM789
|
|
@@ -492,24 +506,24 @@ curviate recruiter save-candidate "$PROJECT_ID" \
|
|
|
492
506
|
### 7. Search Recruiter people
|
|
493
507
|
|
|
494
508
|
```bash
|
|
495
|
-
curviate recruiter search people \
|
|
509
|
+
curviate core recruiter search people \
|
|
496
510
|
--keywords "senior backend engineer" \
|
|
497
511
|
--account acc_1 \
|
|
498
512
|
--limit 5 --json \
|
|
499
513
|
| jq -r '.items[] | "\(.id)\t\(.full_name // .headline)"'
|
|
500
514
|
|
|
501
515
|
# A pasted Recruiter search / talent-pool URL runs directly:
|
|
502
|
-
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
|
|
503
517
|
```
|
|
504
518
|
|
|
505
519
|
### 8. Get a Recruiter-enriched profile, then start a chat with them
|
|
506
520
|
|
|
507
|
-
`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`.
|
|
508
522
|
|
|
509
523
|
```bash
|
|
510
|
-
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
|
|
511
525
|
|
|
512
|
-
curviate recruiter message new \
|
|
526
|
+
curviate core recruiter message new \
|
|
513
527
|
--to AEM789 \
|
|
514
528
|
--account acc_1 \
|
|
515
529
|
--subject "A role you'd be a great fit for" \
|
|
@@ -519,15 +533,15 @@ curviate recruiter message new \
|
|
|
519
533
|
|
|
520
534
|
### 9. List your postings, and get any public job posting through the Recruiter lens
|
|
521
535
|
|
|
522
|
-
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
|
|
523
537
|
detail of *any* public LinkedIn job posting, the Recruiter-seated counterpart to the top-level
|
|
524
|
-
`job get` command:
|
|
538
|
+
`curviate core job get` command:
|
|
525
539
|
|
|
526
540
|
```bash
|
|
527
|
-
curviate recruiter jobs --account acc_1 --limit 10 --json \
|
|
541
|
+
curviate core recruiter jobs --account acc_1 --limit 10 --json \
|
|
528
542
|
| jq -r '.items[] | "\(.id)\t\(.title)\t\(.state)"'
|
|
529
543
|
|
|
530
|
-
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
|
|
531
545
|
```
|
|
532
546
|
|
|
533
547
|
## Retrieval modes
|
|
@@ -550,7 +564,7 @@ threshold: that combination is a usage error (exit `2`) before any request is
|
|
|
550
564
|
sent.
|
|
551
565
|
|
|
552
566
|
Available on the four reads that can be served from a stored copy:
|
|
553
|
-
`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
|
|
554
568
|
listings on the profile commands (`--posts`, `--comments`, `--reactions`,
|
|
555
569
|
`--followers`) do not accept them and reject them with exit `2`.
|
|
556
570
|
|
|
@@ -573,28 +587,28 @@ this API simply holds no copy, so re-checking the id is the wrong move. It is
|
|
|
573
587
|
not a failure either. The fix is another mode, and it is never worth retrying
|
|
574
588
|
as sent, because the answer cannot change until you change the mode.
|
|
575
589
|
|
|
576
|
-
`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
|
|
577
591
|
unfiltered, uncursored first page, only after a walk of the whole chat reached
|
|
578
592
|
its end, and only when the chat's whole message set fits in that one page
|
|
579
593
|
(`--limit`, at most 25). Any unfiltered page fetched from LinkedIn (such as
|
|
580
594
|
`--mode live` without `--all`) restarts the walk, and
|
|
581
|
-
`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
|
|
582
596
|
carrying `--before`, `--after` or `--cursor` is never served from the store and
|
|
583
597
|
`--all` does not change that, so a chat with more messages than one page holds
|
|
584
598
|
exits `14` under `--mode cache_only` however it is walked.
|
|
585
599
|
|
|
586
600
|
```bash
|
|
587
601
|
# The default: a fresh stored copy if there is one, otherwise fetch
|
|
588
|
-
curviate profile me --account acc_1 --json
|
|
602
|
+
curviate core profile me --account acc_1 --json
|
|
589
603
|
|
|
590
604
|
# Serve whatever is stored at any age, and fetch only if nothing is
|
|
591
|
-
curviate profile me --account acc_1 --mode refill --json
|
|
605
|
+
curviate core profile me --account acc_1 --mode refill --json
|
|
592
606
|
|
|
593
607
|
# Accept a stored copy up to five minutes old, otherwise fetch
|
|
594
|
-
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
|
|
595
609
|
|
|
596
610
|
# A single chat from the store, never LinkedIn. Exit 14 if nothing is stored.
|
|
597
|
-
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
|
|
598
612
|
```
|
|
599
613
|
|
|
600
614
|
## Exit codes
|