Linkedin Release Notes

Sales Navigator user and admin updates

Salesforce updates to external client app authentication

Effective May 2026, Salesforce is introducing new security requirements for external client apps used by partner integrations. As part of these updates, partners are required to implement:

• Proof Key for Code Exchange (PKCE)
• Refresh Token Rotation (RTR)

These controls improve the security of OAuth authentication flows and help protect against token misuse.

What’s changing for Sales Navigator admins?

Sales Navigator admins must enable new OAuth security controls:

• PKCE must be enabled and can’t be turned off once activated.
• RTR must be enabled, which changes how refresh tokens are issued and used.

These updates are required for continued compliance. Sales Navigator admins are advised to review the Salesforce communications and complete the recommended next steps.

Salesforce CRM user seat connections and inactivity limits

To improve security and reliability, Salesforce enforces a 30-day inactivity limit on refresh tokens for user seat connections. If a user doesn’t have Salesforce CRM activity for 30 consecutive days, their connection expires. The data is not lost; the connection is just paused. When the user returns and attempts a CRM action, they’ll be prompted to reconnect, after which time, they can sync and access their CRM data.

Get Started guide to help prospect by finding and saving leads

Saving a lead in Sales Navigator lets you track a prospect and receive updates that can help you plan outreach. The Get Started guide can help you start finding leads in Sales Navigator and save leads from your search results to monitor and reach out to leads at the right time.

Learn more

• Sales Navigator release notes

Product & Platform Announcements

• Events Management API: Off-Platform Event Support and Required End Dates

  Starting with the 202605 version, the /rest/events endpoint adopts the new Event schema with the following changes:

  • hasDarkUgc: A boolean field indicating whether the event is backed only by a dark UGC post created through sponsored ad workflows. When true, the event has no LinkedIn Events Detail Page and is suppressed from all organic surfaces regardless of discoveryMode. The field is CREATE ONLY and defaults to false for regular page-backed events.
  • endsAt: Now a required field on all event types. Create requests that omit endsAt will be rejected with a validation error. This is a breaking change introduced from 202605; versions 202604 and below continue to treat endsAt as optional.

• Event Ads API: Off-Platform Event Ads and Lead Generation Campaign Objective

  Starting with the 202605 version, the Event Ads API (/rest/adAccounts/{adAccountId}/adCampaigns with format: SPONSORED_UPDATE_EVENT) adds the following capabilities:

  • objectiveType: LEAD_GENERATION is now a supported objective for Event Ad campaigns, alongside the existing BRAND_AWARENESS, WEBSITE_VISITS, and ENGAGEMENT objectives. The referenced event must have a lead gen form attached (event.leadGenForm) and be published (event.ugcPost populated).
  • Off-platform Event Ads: A new end-to-end flow is available for advertisers who want to run Event Ads without a LinkedIn Events Detail Page. Create the backing event with hasDarkUgc: true, then proceed with the standard campaign, dark post, and Event Ad creative steps. The ad redirects to the external URL regardless of event lifecycle stage.

• Conversions API: New user identifiers available for matching, updated required field validation for lead, and a new request parameter to fetch cross-account shared conversion rules

  New optional user identifiers in the userIds object in the Conversion Event User Schema for /rest/conversionEvents to improve match rates and attribution performance. This update is available on all active versions.

  • PLAINTEXT_IP_ADDRESS: IP address of the user in plain text format. Currently, only IPv4 addresses are supported.
  • GOOGLE_AID: The Google Advertising ID (GAID), a unique, user-resettable, and anonymous identifier for Android devices.

  Updated the required field validation in the Conversion Event User Schema for /rest/conversionEvents to allow sending conversion events with only lead as the user identifier. Previously, this returned a 400 validation error. This update is available on all active versions.

  The Find Conversion Rules by Ad Account API on /rest/conversions finder by account now supports an optional array parameter conversionOwnershipTypes accepting two possible values: OWNED and SHARED. The response body includes a new field ownershipType with one of those values in the conversion object. This allows fetching both owned conversions for the ad account and shared conversions across ad accounts within the same Business Manager. If this query parameter is not passed, only OWNED conversions are returned by default, preserving existing behavior for version 202604 and earlier.

• Predictive Audiences API: New method to Get all predictive audiences in the account

  Starting with the 202605 version, the Predictive Audiences API supports the GET_ALL method on /rest/dmpSegments/{dmpSegmentId}/businessObjectiveBasedAudiences, which retrieves all predictive audiences under a given parent DMP segment as a paginated collection.

• Ad Analytics API: New metric available for Appointments Scheduled from Lead Gen Forms

  Starting with the 202605 version, the AdAnalytics API supports a new metric appointmentsScheduled in the response for /rest/adAnalytics. This metric measures the number of appointments booked through Lead Gen campaigns.

• Company Intelligence API: Paid Video Views Metric

  Starting with the 202605 version, the /accountIntelligence endpoint now includes the following new field for campaign insights at the company level:

  • paidVideoViews: A long type field representing the total count of paid video ad views from members of the target company. Counts are aggregated over the window specified in filterCriteria.lookbackWindow. The field is response-only, included in the default projection alongside the existing engagement metrics, and defaults to 0 when no paid video views have been attributed to the target company within the lookback window.

• Change to Developer Support path

  Starting May 15, 2026, contact Developer Support via the Developer Support Request Form. This will be the primary way to reach Developer Support going forward. The Zendesk support path will sunset soon. Use the form for all new requests as we transition.

• Reapply to API Products from your Developer Portal

  Developers can now resubmit expired API access requests (that expire after 21 days) or those declined for insufficient details directly in the Developer Portal. A Reapply CTA replaces "Access denied", reloads the original form for edits, and creates a new case—no need to recreate the app or contact support.

Product & Platform Announcements

• Member Post Statistics: New Creator Analytics Metrics

The /memberCreatorPostAnalytics endpoint now supports new metrics:

• POST_SEND: Number of times post entities were sent via LinkedIn messaging.

• POST_SAVE: Number of times post entities were saved.

• LINK_CLICKS: Number of clicks on links within post entities.

• PREMIUM_CTA_CLICKS: Number of clicks on premium call-to-action buttons.

• FOLLOWER_GAINED_FROM_CONTENT: Number of new followers gained from post entities.

• PROFILE_VIEW_FROM_CONTENT: Number of profile views generated from post entities.

• Company Intelligence API: New 180-Day Lookback Window

Starting with the 202604 version, the /accountIntelligence endpoint now supports a LAST_180_DAYS lookback window, extending the maximum range for filtering impression and engagement data from 90 to 180 days.

• New Integration Requirements Pages

New requirement pages are now available to guide developers on the technical criteria for integrating with LinkedIn Marketing Solutions APIs. These requirements must be met as part of an organization pursuing partner certification.

• Community Management
• Event Management
• Conversions API
• Reporting
• Advertising
• Audience Insights
• Media Planning
• Company Intelligence
• Matched Audiences
• Lead Sync

Product & Platform Announcements

• Member Post Statistics: New Creator Analytics Metrics

The /memberCreatorPostAnalytics endpoint now supports new metrics:

• POST_SEND: Number of times post entities were sent via LinkedIn messaging.

• POST_SAVE: Number of times post entities were saved.

• LINK_CLICKS: Number of clicks on links within post entities.

• PREMIUM_CTA_CLICKS: Number of clicks on premium call-to-action buttons.

• FOLLOWER_GAINED_FROM_CONTENT: Number of new followers gained from post entities.

• PROFILE_VIEW_FROM_CONTENT: Number of profile views generated from post entities.

• Company Intelligence API: New 180-Day Lookback Window

Starting with the 202604 version, the /accountIntelligence endpoint now supports a LAST_180_DAYS lookback window, extending the maximum range for filtering impression and engagement data from 90 to 180 days.

• New Integration Requirements Pages

New requirement pages are now available to guide developers on the technical criteria for integrating with LinkedIn Marketing Solutions APIs. These requirements must be met as part of an organization pursuing partner certification.

• Breaking Changes

The monthly API versions below will be sunset and removed from the platform on the dates listed. For information on all the supported versions, refer to the migrations documentation. To avoid disruptions to your platform, please migrate to the latest API version launched today.

• Version Sunset

202504 - Apr 15, 2026
202505 - May 15, 2026
202506 - Jun 15, 2026

• Reminders

Member Post Statistics API: New creator analytics metrics

Starting with the 202604 version, the /memberCreatorPostAnalytics endpoint now supports new metrics:

POST_SEND, POST_SAVE, LINK_CLICKS, PREMIUM_CTA_CLICKS, FOLLOWER_GAINED_FROM_CONTENT, PROFILE_VIEW_FROM_CONTENT.

This release notes article lists the enhancements and content updates for Sales Navigator users, admins, and partners from January to March 2026.

Sales Navigator updates

As a Sales Navigator user, you can use a combination of search filter refinements to find accounts. You can share account searches with your colleagues directly in Sales Navigator, which can be helpful if you’re collaborating with a team.

Share account searches in Sales Navigator

As a Sales Navigator user, you can use a combination of search filter refinements to find accounts. You can share account searches with your colleagues directly in Sales Navigator, which can be helpful if you’re collaborating with a team.

Sales Navigator admin guide

As a Sales Navigator admin, learn how to activate users faster, manage your account and integrate Sales Navigator with your existing systems, and ensure seller success with Sales Navigator. The guide can help you:

• Assign licenses and manage Sales Navigator access.
• Optimize your account setup.
• Learn admin best practices.
• Help users sell effectively with Sales Navigator.
• Manage billing and payments.
• Contact support.

Learn more about the
Sales Navigator admin guide.

CRM Sync user authentication in Sales Navigator

Learn how to complete your CRM Sync user authentication to access activity writeback, create leads and contacts, and view CRM insights in Sales Navigator. This will ensure that any activity you perform, for example, sending InMail, creating contacts, or updating records, can write back to your CRM (Salesforce, Microsoft Dynamics 365, HubSpot, or Oracle Sales) depending on what your admin has enabled.

Learn more

Sales Navigator release notes

Product & Platform Announcements

• Company Intelligence API: New Qualified Leads and Conversions Metrics

  Starting with the 202603 version, the /accountIntelligence endpoint's response now includes the following new fields for campaign insights at the company level:

  • paidQualifiedLeads: A long value representing the number of qualified leads from the Conversions API attributed to the target company.
  • conversions: A long value representing the count of conversions based on actions performed by a member after viewing or clicking on an ad. This includes both the Conversions API and Insights Tag conversions.

  Both fields are returned by default (included in the default projection) and will be present in the response, returning 0 when no data is available. These metrics correlate qualified leads and conversions with target companies to inform account-based marketing prioritization.

• Lead Sync API: Webhook validation is required for new lead notifications

  Starting March 16, 2026, we are enforcing webhook validation while sending push events for LEAD_ACTION type. New lead notifications will only be pushed to webhooks that have been validated. For more information, refer to the Webhook validation guide and FAQ.

• Ads Targeting Facets API: New Buyer Group Targeting Facet

  The Ad Targeting Facets API introduces a new buyerGroups facet. This feature allows advertisers to target audiences based on predefined buyer group categories. Each buyer group represents a standardized product category (Example: Cybersecurity Software).

  The buyerGroups facet supports the following finders on the /adTargetingEntities endpoint:

  • adTargetingFacet: Retrieves the full list of available buyer group segments.
  • typeahead: Searches for buyer group segments by keyword (Example: Query "software" returns matching product categories).

• Brand Lift Testing API: Maximum of 50 Campaign Groups per Test

  Brand Lift Tests are limited to 50 Campaign Groups maximum upon creation.

Documentation Updates

• Event Management API: Field mutability and lifecycle update restrictions

  The revised Event fields documentation clarifies modification rules by classifying fields as READ ONLY, CREATE ONLY, or UPDATABLE. A critical change is the restriction that no fields, including the event name and description, can be updated after an event has begun. The documentation also indicates that live audio events are a deprecated feature.

Breaking Changes

The monthly API versions below will be sunset and removed from the platform on the dates listed. For information on all the supported versions, refer to the migrations documentation. To avoid disruptions to your platform, please migrate to the latest API version launched today.

202503 - Mar 16, 2026

202504 - Apr 15, 2026

202505 - May 15, 2026

Product & Platform Announcements

• Videos API: New Media Attribution Fields for Third-Party Integration

  Starting with the 202602 version, we have introduced two optional fields to the /videos endpoint's initializeUploadRequest: templateName and linkbackContext. Developers can now track and attribute videos created using third-party tools, companies, or templates. You can provide attribution metadata using the following optional fields:

  • templateName: A string identifying the name of the template used to create the video (Example: "Sunshine birthday wishes").
  • linkbackContext: A string that provides context for linking back to the original source, such as a URL pointing to the specific template or tool.

  These fields allow downstream systems to identify the source template or tool used during video creation and enable deep linking back to the original resource when needed. When a video is created with these attribution fields, LinkedIn can display the template name and provide a direct link to the source, enabling attribution and allowing advertisers and content creators to reference the tools or templates used during video creation.

• Ad Campaigns API & Ad Budget Pricing API: Qualified leads available as optimization target for Lead Generation campaign objective

  Starting with the 202602 version, we have introduced MAX_QUALIFIED_LEAD as a supported value for optimizationTargetType field used in the /adCampaigns and /adBudgetPricing endpoints when using LEAD_GENERATION as campaign objectiveType. This optimizes lead generation campaigns to target high-quality leads using qualified lead data sent from Conversions API (where conversion rule type must be QUALIFIED_LEAD) or CRM data shared from Business Manager. Learn more here.

• Breaking Changes

  The monthly API versions below will be sunset and removed from the platform on the dates listed. To avoid disruptions to your platform, please migrate to the latest API version launched today. For information on all the supported versions, refer to the migrations documentation.

  202502 - Feb 16, 2026
  202503 - Mar 16, 2026
  202504 - Apr 15, 2026