# Linked API changelog

What has been added to Linked API: new actions, result fields, parameters and capabilities. One
release a week at most, dated by the Monday of its week; a week with nothing new has no release.

Machine-readable forms of this page:

- JSON, only releases for the week of a moment you name and later: https://linkedapi.io/api/changelog?since=2026-01-01T00:00:00Z
- RSS: https://linkedapi.io/changelog/rss.xml

## Week of 2026-11-09

- **Sales Navigator lists.** `nv.retrieveLists` reads your Sales Navigator lead or account lists with their IDs, `nv.createList`, `nv.renameList` and `nv.deleteList` create, rename and delete them, and `nv.retrieveListLeads` and `nv.retrieveListAccounts` read the leads or accounts in one list; the same is available in the Node SDK, as `linkedin navigator lists` in the CLI, in the MCP server and in n8n. [Docs](https://linkedapi.io/docs/action-nv-retrieve-lists)
- **Saving leads and accounts.** `nv.saveLead` and `nv.saveAccount` save a person or company in Sales Navigator, optionally into one of your lists and also straight from search results under `nv.doForPeople` and `nv.doForCompanies`, `nv.unsaveLead` and `nv.unsaveAccount` unsave them, and `nv.removeLeadFromList` and `nv.removeAccountFromList` take one out of a single list; the same is available in the Node SDK, the CLI, the MCP server and n8n. [Docs](https://linkedapi.io/docs/action-nv-save-lead)
- **Saved searches.** `nv.createSavedSearch` saves a Sales Navigator lead or account search from its URL, `nv.retrieveSavedSearches` reads your saved searches with their count of new results and the URL to pass as `customSearchUrl` to `nv.searchPeople` or `nv.searchCompanies`, and `nv.deleteSavedSearch` deletes one; the same is available in the Node SDK, as `linkedin navigator saved-searches` in the CLI, in the MCP server and in n8n. [Docs](https://linkedapi.io/docs/action-nv-retrieve-saved-searches)
- **Sales Navigator alerts.** `nv.retrieveAlerts` reads the lead and account alerts from your Sales Navigator home feed, newest first or by relevance, filtered by lead or account, alert type, publication time, one of your lists, chosen leads or accounts, or only the subjects you saved; the same is available in the Node SDK, as `linkedin navigator alerts` in the CLI, in the MCP server and in n8n. [Docs](https://linkedapi.io/docs/action-nv-retrieve-alerts)
- **People search by URL in the CLI.** `linkedin person search --url` runs a LinkedIn people search URL, the CLI form of `customSearchUrl`, in place of `--term` and the filters. [Docs](https://linkedapi.io/docs/action-st-search-people)

## Week of 2026-10-19

- **Skill endorsements.** `st.endorsePersonSkill` endorses one skill of a 1st-degree connection by its name, and `st.doForSkills` under `st.retrievePersonSkills` endorses all of the person's skills or only those whose names match RE2 `skillNamePatterns`, reporting the outcome for each selected skill; the same is available as `endorsePersonSkill` and `endorsePersonSkills` in the Node SDK, `linkedin person endorse` in the CLI, `endorse_person_skill` and `endorse_person_skills` in the MCP server and the Endorse person skill and Endorse person skills actions in n8n. [Docs](https://linkedapi.io/docs/endorsing-skills)

## Week of 2026-10-12

- **One person's conversation.** `/inbox/poll` with `personUrl` returns the whole known conversation with one person, the messages the inbox captured together with history loaded by `st.syncConversation` or `nv.syncConversation`, and its `threads` say how far back each thread's history goes with `historyFrom` and `historyComplete`; the same view is available as `pollInbox` in the Node SDK, `linkedin inbox get --person` in the CLI and `get_inbox` in the MCP server. [Docs](https://linkedapi.io/docs/monitoring-inbox)

## Week of 2026-10-05

- **Viewer state.** Person and content results carry a `viewerState` object that says how your account relates to them: people, including the authors of posts and comments, report your `connectionDegree` (`1st`, `2nd` or `3rd+`), and posts and comments report your `reaction` and `isOwn`, or `null` where it cannot be read. [Docs](https://linkedapi.io/docs/data-conventions)
- **Connection degree filters.** `st.searchPeople`, `nv.searchPeople`, `st.retrieveCompanyEmployees` and `nv.retrieveCompanyEmployees` filter by your connection degree with `connectionDegrees` (`1st`, `2nd`, `3rd+`, plus `groupMembers` on Sales Navigator), also available as CLI flags. [Docs](https://linkedapi.io/docs/action-st-search-people)
- **Signed webhooks and custom headers.** Webhook deliveries can carry an HMAC-SHA256 signature to verify and custom headers for an endpoint that requires authentication, both off by default and set through `webhook.set`, `webhook.setSigning` and `webhook.setHeader`, with endpoints to reveal and rotate the secret and to replace or delete headers. [Docs](https://linkedapi.io/docs/webhook-signature-verification)
- **Event selection.** A webhook can receive only the events you choose, exact types such as `workflow.completed` or whole namespaces such as `inbox.*`, set with `events` on `webhook.set`, changed with `webhook.setEvents` or under Advanced → Events on the platform; a webhook that never chooses keeps receiving every event. [Docs](https://linkedapi.io/docs/webhook-event-types)
- **Webhook management in the SDKs and CLI.** The Node and Python SDKs and the CLI manage webhook signing, custom headers and event selection, and the SDKs verify a signed delivery with `verifyWebhookSignature` / `verify_webhook_signature`. [Docs](https://linkedapi.io/docs/admin-webhooks)
- **Changelog in the SDKs, CLI and MCP.** Read this changelog with `getChangelog` / `get_changelog` from code, `linkedin changelog` from the terminal or the `get_changelog` tool in the MCP server, with no token. [Docs](https://linkedapi.io/sdks/get-changelog)

## Week of 2026-09-28

- **Reposts.** `st.createRepost` reposts someone else's post or your own, as is or with your commentary, addressed by `postUrl` or `postUrn`. [Docs](https://linkedapi.io/docs/action-st-create-repost)
- **Mentions.** `st.createPost` and `st.createRepost` tag up to 20 people and companies through `mentions`: write `@[key]` in the text and describe each key with a name, optionally pinned by `urn`, `personHashedUrl` or `companyHashedUrl`. [Docs](https://linkedapi.io/docs/action-st-create-post)
- **Post URNs.** Opening, reacting to, commenting on and reposting a post, and reading its comments and reactions, accept `postUrn` instead of `postUrl`, and `st.createPost` returns the new post's `postUrn` when LinkedIn gives it an address and, in workflows sent to the API, can run `st.openPost` on it as a child. [Docs](https://linkedapi.io/docs/publishing-posts)

## Week of 2026-09-14

- **Post search.** `st.searchPosts` searches LinkedIn posts by keyword, with filters for the author, the date posted and the content type. [Docs](https://linkedapi.io/docs/action-st-search-posts)

## Week of 2026-08-17

- **Public profile URL in inbox events.** Inbox polling and message webhooks carry `personPublicUrl`, the other participant's public URL, once Linked API has resolved it; it can be null on any message. [Docs](https://linkedapi.io/docs/monitoring-inbox)

## Week of 2026-08-10

- **Conversation sync period.** `st.syncConversation` and `nv.syncConversation` accept `days` (1 to 90) and return `syncUntil`; sync lasts 30 days unless `days` says otherwise, and running the action again starts a new period without losing the history. [Docs](https://linkedapi.io/docs/action-st-sync-conversation)
- **LinkedIn URNs.** Results carry LinkedIn's permanent identifiers next to URLs, `urn` for the person, company or job posting a result is about and fields such as `companyUrn` and `personUrn` for related entities, including in inbox and network events, or null where LinkedIn exposes none. [Docs](https://linkedapi.io/docs/data-conventions)
- **Profile viewers.** `st.retrieveProfileViewers` reads who viewed your profile and when; semi-private viewers come back as anonymous with a people-search URL, and viewers in full private mode are not returned. [Docs](https://linkedapi.io/docs/action-st-retrieve-profile-viewers)
- **AI-powered jobs search.** On LinkedIn's AI-powered jobs search, `st.searchJobs` takes `preferences` (date posted, experience levels, employment types, companies, remote, Easy Apply, under 10 applicants, in your network, keywords) that LinkedIn applies where it offers them, reports `isSimilarMatch` for each job, and leaves near matches out with `allowSimilarResults: false`. [Docs](https://linkedapi.io/docs/searching-for-jobs)

## Week of 2026-08-03

- **Working hours.** An account can have a weekly activity window, set on the platform: your requests outside it are queued, rejected with `outsideWorkingHours` or run anyway depending on the account's policy, a workflow that has not started reports why in `pendingReason`, and an account with no window is never gated. [Docs](https://linkedapi.io/docs/working-hours)

## Week of 2026-07-27

- **Connection page completion.** `accounts.createConnectionSession` and `accounts.createReconnectionSession` accept a `completion` object that sets how limits are handled on a new connection, a button back to your product, and redirects on success or failure. [Docs](https://linkedapi.io/docs/admin-connection-sessions)

## Week of 2026-07-20

- **Feed.** `st.retrieveFeed` reads your LinkedIn feed: the posts, their authors and their engagement counts. [Docs](https://linkedapi.io/docs/action-st-retrieve-feed)
- **Comments.** React to or reply to a single comment with `st.reactToComment` and `st.replyToComment`, open one with `st.openComment`, or act with `st.doForComments` on each comment `st.retrievePostComments` returns. [Docs](https://linkedapi.io/docs/reacting-and-commenting)

## Week of 2026-07-13

- **Network sync.** `st.syncNetwork` enables network monitoring, so connection events (accepted requests, new connections, incoming requests) arrive through polling or `network.*` webhooks for the changes made after you enable it. [Docs](https://linkedapi.io/docs/action-st-sync-network)
- **Profile photos and company logos.** Person results carry `avatarUrl` and company results `logoUrl`, or null, on the profile, company page and search actions for standard LinkedIn and Sales Navigator. [Docs](https://linkedapi.io/docs/action-st-open-person-page)
- **Company and newsletter invitations.** Received invitations also include invitations to follow a company or subscribe to a newsletter, each with its `invitationType`, accepted or ignored with the same actions. [Docs](https://linkedapi.io/docs/working-with-invitations)

## Week of 2026-07-06

- **Inbox sync.** Keep a LinkedIn inbox in sync and read it through the API, or receive its messages as `inbox.messageReceived` and `inbox.messageSent` webhooks, for standard LinkedIn and Sales Navigator. [Docs](https://linkedapi.io/docs/action-st-sync-inbox)
- **Conversations.** `st.sendMessage` and `nv.sendMessage` reply into an existing thread by `threadId`, `st.manageConversation` archives, stars or mutes a conversation and undoes each, also right after sending a message, and `nv.manageConversation` archives and unarchives one. [Docs](https://linkedapi.io/docs/action-st-manage-conversation)
- **Received connection requests.** Read the connection requests you have received, and accept or ignore each one. [Docs](https://linkedapi.io/docs/working-with-invitations)

## Week of 2026-06-29

- **Webhooks.** Register one HTTPS endpoint through the Admin API to receive workflow and account events instead of polling; deliveries are retried and can be listed, replayed and tested, and a completed workflow's result travels in the event or is fetched by id. [Docs](https://linkedapi.io/docs/webhooks)
