curviate-search

Topics in the source

• Curviate: search and discovery
• Before any command
• Resolve filter terms first
• The search commands
• Traps
• Groups
• Pagination: one page is not the result set
• Full command surface

Search is where most workflows start: find the person, the company, the post or the posting, then act on it. Two rules decide whether a search is trustworthy, and both fail silently when broken: structured filters take opaque ids, never human text, and a single page is not the result set. Command surface established against CLI 0.33.0. Credentials resolve flag > environment > stored profile (CURVIATEAPIKEY, CURVIATEBASEURL, CURVIATEACCOUNT). --profile picks the stored credential set; --account picks which connected LinkedIn account performs this command. They answer different questions; pass either or both. --account takes an id, never an account name. --json on anything you parse; --fields a,b,c to keep result sets small; --verbose when a slim response looks suspiciously empty. Put global flags at the end of the command. Trailing placement is unambiguous on every version. Branch on the exit code, never on prose. See the table at the end. Search is a read. --mode/--max-age are refused here with unknown flag, exit 2. Retrieval mode exists on four commands only, and none of them is a search (see curviate-profile). Every id-taking filter (--location, --industry, --company, --school, -

This is an excerpt. Refer to the complete source and its current requirements.