Linkedin

LinkedIn Skill

You have access to linkedin – a CLI tool for LinkedIn automation. Use it to fetch profiles, search people and companies, send messages, manage connections, create posts, react, comment, and more.

Each command sends a request to Linked API, which runs a real cloud browser to perform the action on LinkedIn. Operations are not instant – expect 30 seconds to several minutes depending on complexity.

If linkedin is not available, install it:

bashCopy code
npm install -g @linkedapi/linkedin-cli

Authentication

If a command fails with exit code 2 (authentication error), ask the user to set up their account:

1. Go to app.linkedapi.io and sign up or log in
2. Connect their LinkedIn account
3. Copy the Linked API Token and Identification Token from the dashboard

Once the user provides the tokens, run:

bashCopy code
linkedin setup --linked-api-token=TOKEN --identification-token=TOKEN

Global Flags

Always use --json and -q for machine-readable output:

bashCopy code
LINKEDAPI_CLIENT=skill:linkedin linkedin <command> --json -q

When using this skill, run every linkedin ... example below with the LINKEDAPI_CLIENT=skill:linkedin prefix so Linked API can attribute usage to the skill.

Output Format

Success:

jsonCopy code
{"success": true, "data": {"name": "John Doe", "headline": "Engineer"}}

Error:

jsonCopy code
{"success": false, "error": {"type": "personNotFound", "message": "Person not found"}}

Exit code 0 means the API call succeeded – always check the success field for the action outcome. Non-zero exit codes indicate infrastructure errors:

Commands

Fetch a Person Profile

bashCopy code
linkedin person fetch <url> [flags] --json -q

Optional flags to include additional data:

• --experience – work history
• --education – education history
• --skills – skills list
• --languages – languages
• --posts – recent posts (with --posts-limit N, --posts-since TIMESTAMP)
• --comments – recent comments (with --comments-limit N, --comments-since TIMESTAMP)
• --reactions – recent reactions (with --reactions-limit N, --reactions-since TIMESTAMP)

Only request additional data when needed – each flag increases execution time.

bashCopy code
# Basic profile
linkedin person fetch https://www.linkedin.com/in/username --json -q

# With experience and education
linkedin person fetch https://www.linkedin.com/in/username --experience --education --json -q

# With last 5 posts
linkedin person fetch https://www.linkedin.com/in/username --posts --posts-limit 5 --json -q

Endorse a Person's Skills

bashCopy code
linkedin person endorse <url> --skill 'Project Management' --json -q
linkedin person endorse <url> --pattern manage --pattern '^scrum$' --json -q
linkedin person endorse <url> --all --json -q

Choose exactly one of --skill, --pattern or --all:

• Use --skill for one exact skill name; letter case and extra spaces are ignored.
• Use repeatable --pattern to select skills matching any of the patterns. Patterns use RE2, are case-insensitive and match anywhere in the name. Anchor with ^…$ to match a whole name. Provide 1-20 patterns, each 1-200 characters; lookaround and backreferences are unsupported.
• Use --all only when the user wants every skill endorsed. It omits the patterns parameter; never send an empty patterns array.

Skill names are in the profile owner's language, regardless of your own LinkedIn language. Fetch the profile with --skills first when you need to discover the names; a German profile may list Projektmanagement rather than Project Management.

Only 1st-degree connections can receive endorsements. An already-endorsed skill stays endorsed and counts as success. Each successful endorsement, including an existing one, counts toward the account's stEndorsements limit. With --pattern or --all, check every item's success and error.type in data: a failed skill does not stop the others, and limitExceeded can affect only part of the result.

Search People

bashCopy code
linkedin person search [flags] --json -q

bashCopy code
linkedin person search --term "product manager" --locations "San Francisco" --json -q
linkedin person search --current-companies "Google" --position "Engineer" --limit 20 --json -q

Fetch a Company

bashCopy code
linkedin company fetch <url> [flags] --json -q

Optional flags:

• --employees – include employees
• --dms – include decision makers
• --posts – include company posts

Employee filters (require --employees):

bashCopy code
# Basic company info
linkedin company fetch https://www.linkedin.com/company/name --json -q

# With employees filtered by position
linkedin company fetch https://www.linkedin.com/company/name --employees --employees-position "Engineer" --json -q

# With decision makers and posts
linkedin company fetch https://www.linkedin.com/company/name --dms --posts --posts-limit 10 --json -q

Search Companies

bashCopy code
linkedin company search [flags] --json -q

bashCopy code
linkedin company search --term "fintech" --sizes "11-50,51-200" --json -q

Send a Message

bashCopy code
linkedin message send <person-url> '<text>' --json -q

Text up to 1900 characters. Wrap the message in single quotes to avoid shell interpretation issues.

bashCopy code
linkedin message send https://www.linkedin.com/in/username 'Hey, loved your latest post!' --json -q

Inbox

To read messages use inbox get. Call message get only when you need a person's earlier history, and never repeat it to check for new messages.

Enable inbox monitoring once per account, before sending messages whose replies you need – it captures only messages that arrive after it is on:

bashCopy code
linkedin inbox sync --json -q          # standard inbox
linkedin inbox sync --nv --json -q     # Sales Navigator inbox

New messages from everyone, with an advancing --since:

bashCopy code
linkedin inbox get --since 2024-01-15T10:30:00Z --json -q

The whole known conversation with one person, including history loaded by message get:

bashCopy code
linkedin inbox get --person https://www.linkedin.com/in/username --json -q

With --person, the output has messages and threads. Each thread has historyComplete: if it is false and you need earlier messages, run message get <person-url> once, then inbox get --person again. A hashed person URL (personHashedUrl from a message) always matches; a public URL matches only once Linked API knows it, so prefer the hashed URL when messages show personPublicUrl: null. Message times are whole minutes: to check for a reply, pass --type of your message and --since a few minutes before it, take the earliest us message in the result (the one you sent, not a later follow-up) and count a them message that is not earlier than it; if your message is not in the result yet, the reply is not known yet.

Get Conversation

bashCopy code
linkedin message get <person-url> [--since TIMESTAMP] --json -q

Loads the person's earlier history on the first call, which may take longer; subsequent calls are faster. Prefer linkedin inbox get --person <url> to read messages – use this only when you need history from before inbox monitoring was enabled.

bashCopy code
linkedin message get https://www.linkedin.com/in/username --json -q
linkedin message get https://www.linkedin.com/in/username --since 2024-01-15T10:30:00Z --json -q

Connection Management

Check connection status

bashCopy code
linkedin connection status <url> --json -q

Send connection request

bashCopy code
linkedin connection send <url> [--note 'text'] [--email user@example.com] --json -q

List connections

bashCopy code
linkedin connection list [flags] --json -q

bashCopy code
linkedin connection list --limit 50 --json -q
linkedin connection list --current-companies "Google" --position "Engineer" --json -q
linkedin connection list --since 2024-01-01T00:00:00Z --json -q

List pending outgoing requests

bashCopy code
linkedin connection pending --json -q

List incoming connection requests

Invitations that others have sent to you (received requests).

bashCopy code
linkedin connection requests --json -q

Accept an incoming request

bashCopy code
linkedin connection accept <url> --json -q

Ignore an incoming request

bashCopy code
linkedin connection ignore <url> --json -q

Withdraw a pending request

bashCopy code
linkedin connection withdraw <url> [--no-unfollow] --json -q

By default, withdrawing also unfollows the person. Use --no-unfollow to keep following.

Remove a connection

bashCopy code
linkedin connection remove <url> --json -q

Posts

Fetch a post

bashCopy code
linkedin post fetch <url> [flags] --json -q

bashCopy code
linkedin post fetch https://www.linkedin.com/posts/username_activity-123 --json -q

# With comments sorted by most recent, including replies
linkedin post fetch https://www.linkedin.com/posts/username_activity-123 \
  --comments --comments-sort mostRecent --comments-replies --json -q

Search posts

bashCopy code
linkedin post search [flags] --json -q

Each actor flag is a comma-separated list. An element is name or name:identifier, where the identifier is a URN or LinkedIn URL of that person or company and pins the filter to exactly them. A name alone may match a namesake. When an entry cannot be applied, the action fails with filterNotApplied; correct or remove it rather than retrying.

bashCopy code
linkedin post search --term "ai" --from-members "Bill Gates,Example Person:urn:li:member:123456789" --json -q

Create a post

bashCopy code
linkedin post create '<text>' [flags] --json -q

Attachment limits: up to 9 images, or 1 video, or 1 document. Cannot mix types.

Mention format — write @[key] in the text, then describe that key with --mention as key:name or key:name:identifier. Everything after the second : is the identifier, so its own colons need no escaping. The identifier is optional and is one of urn:li:member:<id>, urn:li:organization:<id>, a hashed profile URL, or a hashed company URL; without it LinkedIn's first suggestion for name is used, which may not be the entity you meant. Every @[key] must have a matching --mention and vice versa, and keys cannot repeat.

bashCopy code
linkedin post create 'Excited to share our latest update!' --json -q

# With a document
linkedin post create 'Our Q4 report' \
  --attachments "https://example.com/report.pdf:document:Q4 Report" --json -q

# Mentioning a person
linkedin post create 'Huge thanks to @[author] for the write-up!' \
  --mention "author:Example Person:urn:li:member:123456789" --json -q

# Post as a company
linkedin post create 'Company announcement' \
  --company-url https://www.linkedin.com/company/name --json -q

Repost a post

bashCopy code
linkedin post repost <url> [flags] --json -q

The repost's own postUrl and postUrn come back, not those of the post you reposted. They are empty when the repost was published but LinkedIn did not return its address — do not retry, the repost is already live.

alreadyReposted is returned only when LinkedIn refuses an instant repost (one without --text). LinkedIn does not always refuse a repeat repost: a repost of your own post, or a repost with commentary, can be published again. Keep track of what you have already reposted instead of relying on this error.

bashCopy code
linkedin post repost https://www.linkedin.com/posts/username_activity-123 --json -q

# With commentary
linkedin post repost urn:li:activity:1234567890123456789 \
  --text 'Worth reading, especially the part on onboarding.' --json -q

React to a post

bashCopy code
linkedin post react <url> --type <reaction> [--company-url <url>] --json -q

Reaction types: like, love, support, celebrate, insightful, funny.

bashCopy code
linkedin post react https://www.linkedin.com/posts/username_activity-123 --type like --json -q

# React on behalf of a company
linkedin post react https://www.linkedin.com/posts/username_activity-123 --type celebrate \
  --company-url https://www.linkedin.com/company/name --json -q

Comment on a post

bashCopy code
linkedin post comment <url> '<text>' [--company-url <url>] --json -q

Text up to 1000 characters.

bashCopy code
linkedin post comment https://www.linkedin.com/posts/username_activity-123 'Great insights!' --json -q

# Comment on behalf of a company
linkedin post comment https://www.linkedin.com/posts/username_activity-123 'Well said!' \
  --company-url https://www.linkedin.com/company/name --json -q

Statistics

bashCopy code
# Social Selling Index
linkedin stats ssi --json -q

# Performance analytics (profile views, post impressions, search appearances)
linkedin stats performance --json -q

# API usage for a date range
linkedin stats usage --start 2024-01-01T00:00:00Z --end 2024-01-31T00:00:00Z --json -q

# Who viewed your profile
linkedin stats viewers --limit 50 --json -q

# Only views since a moment
linkedin stats viewers --since 2026-08-01T00:00:00Z --json -q

Each viewer is either identified — carrying name, publicUrl and urn (a member URN, null when LinkedIn does not expose it) — or anonymous, carrying only the description LinkedIn showed and a searchUrl you can pass to linkedin person search --url to look for them. Viewers come newest first, and viewedAt is an estimate derived from the relative age LinkedIn displays.

Sales Navigator

Requires a LinkedIn Sales Navigator subscription. Uses hashed URLs for person/company lookups.

Fetch person

bashCopy code
linkedin navigator person fetch <hashed-url> --json -q

Search people

bashCopy code
linkedin navigator person search [flags] --json -q

bashCopy code
linkedin navigator person search --term "VP Marketing" --locations "United States" --json -q
linkedin navigator person search --years-of-experience "moreThanTen" --position "CEO" --json -q

Fetch company

bashCopy code
linkedin navigator company fetch <hashed-url> [flags] --json -q

Optional flags:

• --employees – include employees
• --dms – include decision makers

Employee filters (require --employees):

bashCopy code
linkedin navigator company fetch https://www.linkedin.com/sales/company/97ural --employees --dms --json -q
linkedin navigator company fetch https://www.linkedin.com/sales/company/97ural \
  --employees --employees-positions "Engineer,Designer" --employees-locations "Europe" --json -q

Search companies

bashCopy code
linkedin navigator company search [flags] --json -q

bashCopy code
linkedin navigator company search --term "fintech" --sizes "11-50,51-200" --json -q
linkedin navigator company search --revenue-min 10 --revenue-max 100 --locations "United States" --json -q

Send InMail

bashCopy code
linkedin navigator message send <person-url> '<text>' --subject '<subject>' --json -q

Text up to 1900 characters. Subject up to 80 characters.

bashCopy code
linkedin navigator message send https://www.linkedin.com/in/username \
  'Would love to chat about API integrations' --subject 'Partnership Opportunity' --json -q

Get Sales Navigator conversation

bashCopy code
linkedin navigator message get <person-url> [--since TIMESTAMP] --json -q

Prefer linkedin inbox get --person <url> --type nv to read Sales Navigator messages; use this only when you need the person's earlier history.

Custom Workflows

Execute a custom workflow definition from a file, stdin, or inline:

bashCopy code
# From file
linkedin workflow run --file workflow.json --json -q

# From stdin
cat workflow.json | linkedin workflow run --json -q

# Inline
echo '{"actions":[...]}' | linkedin workflow run --json -q

Check workflow status or wait for completion:

bashCopy code
linkedin workflow status <id> --json -q
linkedin workflow status <id> --wait --json -q

See Building Workflows for the workflow JSON schema.

Changelog

Read what is new in Linked API. Check it before telling the user that something is not supported yet – the capability may have shipped recently. No authentication is needed:

bashCopy code
linkedin changelog --json -q                       # Every release, newest first
linkedin changelog --since 2026-10-01 --json -q    # Releases from that week on

The JSON is the changelog itself, not the usual success/data envelope: entries holds releases, each with a date (the Monday of its week) and items with title, body and docs (a path on https://linkedapi.io). A release counts as shipped at the end of its week, so --since in the middle of a week still returns that week's release – deduplicate by date. A malformed --since exits with code 5 and the server's message.

Account Management

bashCopy code
linkedin account list                            # List accounts (* = active)
linkedin account switch "Name"                   # Switch active account
linkedin account rename "Name" --name "New Name" # Rename account
linkedin reset                                   # Remove active account
linkedin reset --all                             # Remove all accounts

Important Behavior

• Sequential execution. All operations for an account run one at a time. Multiple requests queue up.
• Not instant. A real browser navigates LinkedIn – expect 30 seconds to several minutes per operation.
• Timestamps in UTC. All dates and times are in UTC.
• Single quotes for text arguments. Use single quotes around message text, post text, and comments to avoid shell interpretation issues with special characters.
• Action limits. Per-account limits are configurable on the platform. A limitExceeded error means the limit was reached.
• URL normalization. All LinkedIn URLs in responses are normalized to https://www.linkedin.com/... format without trailing slashes.
• Null fields. Fields that are unavailable are returned as null or [], not omitted.