Sales Navigator

Requires the Sales Navigator add-on. These commands call Sales Navigator-specific endpoints on the account. If the account does not have the add-on active, the platform returns a TIER_NOT_ACTIVE error (exit 5). The CLI does not pre-check — the error comes back from the API on the first call.

The sales-nav commands give access to Sales Navigator search, profiles, messaging, lead/account list management, and saving leads and accounts. All commands are account-scoped and require --account.

Changed in 0.15.0: sales-nav sync is removed — no v2 endpoint syncs Sales Navigator messages. New: sales-nav <url> (run a pasted search/list URL directly), sales-nav account-lists, sales-nav lead-lists, sales-nav browse-account-list, sales-nav browse-lead-list, sales-nav save-account. sales-nav save-lead --list-id is renamed --list and is now required — the v2 save always targets a specific list.

sales-nav <url>

# Run a pasted Sales Navigator search or list URL directly (POST, paginated)
curviate sales-nav "<sales-navigator-url>" [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] --account <account_id>

sales-nav search people

# Search Sales Navigator members (POST, paginated)
# Named flags: --keywords, --first-name, --last-name, --groups, --profile-language
# Escape hatch: --filters '<json>' | --filters-file <path> | --filters -
curviate sales-nav search people \
  [--keywords <k>] \
  [--first-name <name>] \
  [--last-name <name>] \
  [--groups <ids>] \
  [--profile-language <codes>] \
  [--filters '<json>'] \
  [--filters-file <path>] \
  [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] \
  --account <account_id>

For the full Sales Navigator filter surface (40+ fields), pass a JSON body via --filters. See the API reference for the complete filter field set. Named flags merge over the --filters base body.

sales-nav search companies

# Search Sales Navigator companies (POST, paginated)
# Named flags: --network-distance, --technologies, --recent-activities
# Escape hatch: --filters '<json>' | --filters-file <path> | --filters -
curviate sales-nav search companies \
  [--network-distance <1,2,3>] \
  [--technologies <t>] \
  [--recent-activities <a>] \
  [--filters '<json>'] \
  [--filters-file <path>] \
  [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] \
  --account <account_id>

sales-nav search parameters

Resolves human-readable terms to opaque filter IDs for Sales Navigator searches. Not paginated — --all is not accepted.

# Resolve Sales Navigator filter IDs (GET, not paginated)
curviate sales-nav search parameters \
  --type <TYPE> \
  [--keywords <k>] \
  [--limit <n>] \
  --account <account_id>

--type is one of GROUPS, SALES_INDUSTRY, DEPARTMENT, PERSONA, ACCOUNT_LISTS, LEAD_LISTS, TECHNOLOGIES, SAVED_ACCOUNTS, SAVED_SEARCHES, RECENT_SEARCHES, REGION, POSTAL_CODE.

sales-nav profile

The <identifier> argument accepts a LinkedIn profile URL, a public slug, or a native id — the CLI normalizes automatically.

# Get an extended Sales Navigator profile (read)
curviate sales-nav profile <identifier> --account <account_id>

sales-nav message new

Start a new Sales Navigator conversation. --to takes a verbatim provider ID (ACw… format) — it is not resolved via URL or slug normalization. --subject is required. --voice and --video are unique to Sales Navigator and Recruiter messaging (max 7 MiB each).

# Start a new Sales Navigator conversation (write, multipart, --preview accepted)
curviate sales-nav message new \
  --to <sales_nav_provider_id> \
  --subject "<subject>" \
  "<message text>" \
  [--attach <file>…] \
  [--voice <audio-file>] \
  [--video <video-file>] \
  --account <account_id>

sales-nav save-lead

Save a person to a Sales Navigator lead list. <user_id> is a verbatim Sales Navigator member ID (ACw… format) — not resolved via URL or slug. --list is required — the v2 save always targets a specific list.

# Save a lead to a list (write, --preview accepted)
curviate sales-nav save-lead <user_id> --list <list_id> --account <account_id>

sales-nav save-account

Save a LinkedIn company into an account list. --list is required.

# Save a company into an account list (write, --preview accepted)
curviate sales-nav save-account <company_id> --list <list_id> --account <account_id>

sales-nav account-lists and lead-lists

# List the saved-account (company) lists on the operator's seat (paginated read)
curviate sales-nav account-lists [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] --account <account_id>
# List the saved-lead (member) lists on the operator's seat (paginated read)
curviate sales-nav lead-lists [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] --account <account_id>

sales-nav browse-account-list and browse-lead-list

# Browse the saved accounts (companies) in one account list (paginated read)
# --filter: STARRED | GROWTH_ALERTS | RISK_ALERTS
# --sort-by: DATE_ADDED | NAME (default NAME); --sort-order: ASCENDING | DESCENDING (default ASCENDING)
curviate sales-nav browse-account-list <list_id> [--filter <f>] [--sort-by <s>] [--sort-order <o>] [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] --account <account_id>
# Browse the saved leads (members) in one lead list (paginated read)
# --spotlight: RECENT_POSITION_CHANGE | RECENTLY_POSTED_ON_LINKEDIN | FOLLOW_YOUR_COMPANY | SHARE_EXPERIENCE
# --sort-by: DATE_ADDED | ACCOUNT | NAME | OUTREACH_ACTIVITY (default DATE_ADDED); --sort-order: ASCENDING | DESCENDING (default DESCENDING)
curviate sales-nav browse-lead-list <list_id> [--spotlight <s>] [--sort-by <s>] [--sort-order <o>] [--limit <n>] [--cursor <token>] [--all] [--max-pages <n>] --account <account_id>

Examples

Search for Sales Navigator profiles by name

curviate sales-nav search people \
  --first-name "Jane" \
  --last-name "Smith" \
  --keywords "machine learning" \
  --account acc_YOUR_ACCOUNT_ID

Run a pasted Sales Navigator search URL directly

curviate sales-nav "https://www.linkedin.com/sales/search/people?query=..." --account acc_YOUR_ACCOUNT_ID

Search companies by technology

curviate sales-nav search companies \
  --technologies "Python,Kubernetes" \
  --network-distance 1,2 \
  --account acc_YOUR_ACCOUNT_ID

Get a Sales Navigator profile

# Accepts a LinkedIn URL, public slug, or native id
curviate sales-nav profile https://www.linkedin.com/in/janedoe --account acc_YOUR_ACCOUNT_ID

Send a Sales Navigator message with a voice note

curviate sales-nav message new \
  --to SALES_NAV_PROVIDER_ID \
  --subject "Quick intro" \
  "Hi, I wanted to reach out about a potential opportunity." \
  --voice ./intro.m4a \
  --account acc_YOUR_ACCOUNT_ID

Save a lead and a company account

curviate sales-nav save-lead SALES_NAV_USER_ID --list LEAD_LIST_ID --account acc_YOUR_ACCOUNT_ID
 
curviate sales-nav save-account COMPANY_ID --list ACCOUNT_LIST_ID --account acc_YOUR_ACCOUNT_ID

List and browse your saved-lead lists

curviate sales-nav lead-lists --account acc_YOUR_ACCOUNT_ID
 
curviate sales-nav browse-lead-list LEAD_LIST_ID --spotlight RECENT_POSITION_CHANGE --account acc_YOUR_ACCOUNT_ID
COMPANY · LEGAL

Privacy Policy

Redmer Holding GmbHLast updated July 25, 2026

Who we are

Curviate is operated by Redmer Holding GmbH ("Curviate", "we", "us"), a German GmbH registered at Amtsgericht Bonn, HRB 29957, registered address Hostertstraße 16, 53332 Bornheim, Germany. Full company details are on our Imprint. We haven't appointed a statutory Data Protection Officer, since our processing doesn't reach the scale or sensitivity that requires one. Privacy questions go to privacy@curviate.com.

The two roles we play

When you create an account and use Curviate, we process your own data (identity, billing, API keys, connector authorizations). For that data, we are the controller.

When you use Curviate to act on your own connected LinkedIn account, viewing profiles, sending messages, managing engagement, that content and those contacts belong to that account and its people. You are the controller of that data; we are the processor, acting only on your instructions, under the Data Processing Agreement between us. If one of your contacts has a question about being reached through Curviate, you're who they should contact first; email privacy@curviate.com if you need help routing it.

What we collect, and why

DataWhy
Account identity (name, email, sign-in method)Create and secure your account
Your LinkedIn credentialsOperate the actions you request
LinkedIn content returned by an API callFulfil that specific request, nothing more
API keys and connector (OAuth) authorizationsAuthenticate your API, CLI, MCP, or SDK requests
Billing detailsCharge you correctly and meet our tax obligations
Usage and security logsKeep the service reliable and abuse-free
Support messagesRespond to you
Website analytics, only if you opt inUnderstand how the site is used

We rely on our contract with you, our legitimate interest in running and securing the service, our legal obligations (tax law, for example), and, for analytics, your consent. We never sell your data or use it to train models.

Where it's processed, and who else touches it

Our infrastructure runs in the EU. Hosting: Railway. Database and auth: Supabase, Ireland. Email: Resend. Payments: Stripe. Network security: a DDoS-protection provider sits in front of our app and never sees or stores request content. LinkedIn connectivity: a third-party infrastructure provider that lets us execute LinkedIn actions on your behalf. Error tracking: Sentry, Frankfurt. Product analytics: PostHog, Frankfurt. Uptime monitoring: Better Stack.

We give the current, named list of every provider above, plus our Data Processing Agreement, to any customer who asks: security@curviate.com.

Outside the EU

All customer LinkedIn data, account data, and telemetry are processed and stored exclusively in EU regions of our sub-processors. A few providers we rely on (Stripe and Sentry, for example) are headquartered outside the EU/EEA; where that applies, it's covered by their own GDPR safeguards, typically the EU Standard Contractual Clauses.

How long we keep it

DataRetention
Account and workspace dataWhile your account is active
Closed accountRecoverable for 7 days, then deleted on day 8
LinkedIn credentialsUntil you disconnect that account
LinkedIn contentNot stored; any transient cache clears within 1 hour, never indexed, never used for training
API keysUntil you revoke or rotate them
Connector (OAuth) authorizationsAccess token ~1 hour; refresh token up to ~12 months, or until you revoke it, whichever comes first
Billing recordsAs required by German tax law, currently up to 10 years
LogsA short operational window; metadata only, never message content

The 12-month figure above is a server-side credential for a connected AI agent or app. It is not a cookie and doesn't touch your browser session; see Cookies below for that. You can see and revoke every connector from Authorized applications in your dashboard at any time.

Cookies

We keep cookies to a minimum, and ask before anything beyond the essentials runs.

Strictly necessary, no consent needed:

NamePurposeExpiry
cc_cookieRemembers your cookie choice12 months
curviate-themeRemembers light/dark mode (local storage, not a cookie)Persistent
sb-*-auth-tokenKeeps you signed inWhile active; cleared on sign-out

Analytics, only if you accept:

NamePurposeExpiry
_gaGoogle Analytics: distinguishes visitors2 years
_gidGoogle Analytics: distinguishes visitors24 hours
_ga_<container id>Google Analytics: persists session state2 years

No advertising cookies, ever. Accept and reject are equally easy, and you can change your mind any time via Cookie Preferences in the footer; we won't ask again for 12 months unless something material changes. Our LinkedIn connect flow and OAuth authorization screen never set anything beyond the essentials, so no banner appears there.

Connecting an AI agent or app

Curviate is built for AI agents and automated clients as much as for people. If you connect an app like Claude, or your own code, via an API key or an OAuth connector, it can act on your workspace within the access you gave it. What it does with anything it receives back, including what it sends to its own AI model, is between you and that provider; review its practices before connecting it. Review and revoke any connection any time from your dashboard.

Your rights

You can access, correct, delete, restrict, or object to your data, port it elsewhere, and withdraw consent at any time: email privacy@curviate.com. Closing your account starts the 7-day recoverable window above. We don't make automated decisions about you that have a legal or similarly significant effect. You can also complain to a supervisory authority; ours is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), www.ldi.nrw.de, though you're free to complain to the one in your own country instead.

Keeping it secure

Credentials are encrypted and never logged, returned, or shared. LinkedIn actions run through native, humanized flows; full detail is on our Security & Compliance page. If a breach puts your rights at risk, we'll notify the authorities and you, as GDPR requires. Curviate isn't directed at, or offered to, anyone under 16.

Changes

We'll update this page when our practices change, and reset the cookie prompt if the change is material.

Contact