Linkedin Marketing API Updates & Release Notes

Product & Platform Announcements

• Creatives API: New metadata field:

  Starting with the 202610 version, the /creatives endpoint supports a new read-only metadata field that returns descriptive information about a creative: adFormat, adHeadline, adIntroductionText, adLine, landingPage, and assetURL. Previously, retrieving this information required calling a different API depending on the creative's content type. The field is derived on read from the creative's underlying content and isn't stored, and fields that don't apply to the creative's ad format are omitted. metadata isn't returned by default; request it explicitly using the fields query parameter when retrieving a single creative, as described in Retrieve Creative Metadata. It isn't returned by the creatives finders. This is an additive, backward-compatible change; versions 202609 and below don't return this field.

• Company Intelligence API: New jobFunction filter:

  Starting with the 202610 version, the accountIntelligence endpoint finder now supports filtering results by the optional jobFunction field under filterCriteria. Supported job-function buckets are INFORMATION_TECHNOLOGY, PRODUCT, SALES, MARKETING, OPERATIONS, FINANCE, HUMAN_RESOURCES, and OTHER. The field accepts these bucket values directly, rather than a standardized job-function URN or numeric ID. Only one of campaign, campaignGroup, objectiveType, seniority, or jobFunction can be passed in filterCriteria. The jobFunction filter is supported only with the LAST_90_DAYS lookback window. It applies to member-attributable paid and organic engagement metrics; paidQualifiedLeads, conversions, and costInLocalCurrencyPerPaidQualifiedLead aren't broken down by job function. This field is request-only and doesn't change the response schema. Versions 202609 and below don't support this filter.

• Creatives API: New enriched content fields:

  Starting with the 202610 version, /creatives responses can return new read-only standardUpdateAd and videoAd members within content. standardUpdateAd includes reference and an optional contentAuthor field; videoAd includes reference, an optional contentAuthor, and an optional preRollMetadata field. Earlier API versions continue returning content.reference. Clients using 202610 should continue supporting content.reference, because it may still be returned when enriched content is unavailable. These fields are read-only and don't change Creative create requests.

• Ads Reporting API: New memberFollows and memberProfileClicks metrics:

  Starting with the 202610 version, the /adAnalytics endpoint's metrics schema supports two new optional metrics: memberFollows, which returns the count of sponsored member profile follows, and memberProfileClicks, which returns the count of clicks on the profile of the member who owns the sponsored post. Both metrics exist only for Sponsored Updates and member follower display ads, such as Thought Leader Ads.

• Boost API: New Member and Company Page post boost endpoints:

  Starting with the 202610 version, four new Boost API endpoints are available for both Member and Company Page (organization) posts: Boost Init, Boost Hydrate, Boost Post, and Boost Status. These APIs enable partners to embed LinkedIn Boosting directly into their content and publishing workflows, connecting organic content to paid amplification within their platform. The endpoints are available under the existing Advertising API product.

Breaking Changes

• Campaign Management API: New required surface field for publisher lists (action required):

  Starting with version 202611 (November 2026 release), publisher lists (/adPublisherRestrictions) require a surface field that sets the list's placement type: LAN (LinkedIn Audience Network) or CTV (Connected TV). Requests on version 202611 or later that create a publisher list without a valid surface will fail with a 400 error. Existing partner API accounts have a migration window that ends on December 15, 2026. After that date, campaigns (/adAccounts/{id}/adCampaigns) and account trust preferences (/adAccountTrustPreferences) can only use publisher lists whose placement type matches the campaign. Requests that don't meet this rule will fail with a 400 error on every API version. Lists already attached to campaigns will keep working. Please update your integration before December 15, 2026.

Version Sunset

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.

• 202510 - Oct 15, 2026
• 202511 - Nov 16, 2026

Product & Platform Announcements

• Company Intelligence API: New campaignGroup, objectiveType, and seniority filters:

  Starting with the 202609 version, the accountIntelligence endpoint finder now supports filtering results by the following optional fields under filterCriteria: campaignGroup, objectiveType, or member seniority, in addition to the existing campaign filter. Only one of campaign, campaignGroup, objectiveType, or seniority can be passed in the filterCriteria parameter. Organic metrics are 0 when campaign, campaignGroup or objectiveType filter is used. The seniority filter is supported only with LAST_90_DAYS lookback window and when campaign, campaignGroup, and objectiveType aren't used in the filterCriteria. These fields are request-only and do not change the response schema. Versions 202608 and below do not support these filters.

• Ads Reporting API: New MEMBER_DESIGNATED_MARKET_AREA pivot:

  Starting with the 202609 version, in the adAnalytics endpoint's analytics finder, pivot.value parameter now supports MEMBER_DESIGNATED_MARKET_AREA, letting partners request analytics reports grouped by Nielsen Designated Market Area (DMA), consistent with other member demographic pivots such as MEMBER_REGION_V2. Pivot items are returned as urn:li:geo:{id} URNs. You may use the /adTargetingEntities resource to resolve these geo URNs to DMA region names. When displaying results grouped by this pivot, you must display a "circle R" notice of registration immediately following each display of the DMA marks (that is, DMA®) and the statement "DMA® is a registered service mark of The Nielsen Company."

• Conversions API: New hashedFirstName and hashedLastName fields:

  Starting with the 202609 version, the userInfo object for the /conversionEvents endpoint supports two new optional fields for matching: hashedFirstName and hashedLastName, in addition to the existing plain text firstName and lastName fields. Before hashing, normalize the value to lowercase with no spaces or punctuation, and encode special characters as UTF-8. The result should be a SHA-256 HEX-encoded string of exactly 64 characters. A valid userInfo combination requires either firstName or hashedFirstName, together with either lastName or hashedLastName.

• Conversions API: New 180-day attribution window option:

  The postClickAttributionWindowSize and viewThroughAttributionWindowSize fields on the Conversion Rule schema in /conversions endpoint now support a 180-day value, in addition to the existing 365-day option, for the following conversion types: SUBMIT_APPLICATION, PURCHASE, ADD_TO_CART, QUALIFIED_LEAD, LEAD, MARKETING_QUALIFIED_LEAD, and SALES_QUALIFIED_LEAD. This update is available on all active versions. MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD conversion types are available starting with the 202608 version onwards.

Version Sunset

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.

• 202510 - Oct 15, 2026
• 202511 - Nov 16, 2026

Product & Platform Announcements

• Matched Audiences API: Generally available to all qualified developers: Starting August 2026, the Matched Audiences API is now generally available for application to all qualified developers. You can apply for access directly from the Developer Portal.

• DMP Segments API: Cap on number of DMP Segments in ad account: Starting August 2026, each sponsored account is restricted to a maximum of 1,000 DMP segments for Matched Audiences (USER, COMPANY, LIST_UPLOAD) and Predictive Audiences. Requests to the /dmpSegments endpoint from ad accounts that exceed this threshold return a 429 error with the code SEGMENT_LIMIT_EXCEEDED. This update applies to all versions. To allocate space for additional segments, delete unused segments before creating new ones. See Delete DMP Segment for details.

• Dynamic UTM API: Ad account-level tracking parameter support: Starting with the 202608 version, the /adTrackingParameters endpoint now supports setting dynamic UTM tracking parameters at the ad account level using the sponsoredAccount member of the adEntity key, in addition to the existing sponsoredCampaign. Account-level parameters apply to creatives across all campaigns in the account. This is an additive, backward-compatible change.

• Conversions API: New conversion types for Marketing & Sales Qualified Leads: Starting with the 202608 version, the /conversions endpoint now supports MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD as granular conversion types in addition to the existing QUALIFIED_LEAD. Conversion events streamed on conversion rules with these new types are used in the qualified leads optimization goal for deeper funnel campaign optimization, similar to QUALIFIED_LEAD. See Qualified leads optimization goal for details.

• Conversions API: Additional use cases: Additional use cases published for the Conversions API, including qualified leads optimization, retargeting audiences, source data for predictive audiences, and conversion lift testing.

• Ad Accounts API: New productType and originatingCustomer fields: Starting with the 202608 version, the /adAccounts endpoint returns productType (MARKETING_SOLUTIONS, TALENT_SOLUTIONS, LINKEDIN_ON_LINKEDIN) and originatingCustomer (a urn:li:customer:{id} URN). Both fields apply to ENTERPRISE accounts only and are immutable once set at account creation. This is an additive, backward-compatible change.

• Campaign Groups API: New billing, beneficiary, and buying type fields: Starting with the 202608 version, the /adCampaignGroups endpoint supports billingReference, billingParentReference, beneficiaryReference (a union of company or organization), and buyingType (AUCTION or RESERVATION). All four fields are immutable once set at campaign group creation; billingReference and billingParentReference apply to ENTERPRISE accounts only. In earlier versions, these fields are rejected with a 422 error. This is an additive, backward-compatible change.

Version Sunset

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.

• 202508 - Aug 17, 2026
• 202509 - Sep 15, 2026
• 202510 - Oct 15, 2026

Reminders

Starting Aug 31, 2026, LinkedIn will completely stop supporting Legacy Geo for Ads Targeting. Requests to create campaigns using legacy geo will result in a 400 error with the INVALID_VALUE_FOR_FIELD code. All partners and developers must use Bing-geo as previously published in this migration guide.

The top-level location field (for example, "San Francisco Bay Area") is also being removed from /v2/me and /v2/people responses. Partners currently relying on location may begin receiving an empty or null value and should migrate to the geoLocation field (for example, request projection=(geoLocation(geo,autoGenerated)), which is already available on both endpoints. See the Profile API documentation for guidance on using geoLocation with the geo projection to retrieve the location display name.

Product & Platform Announcements

• Matched Audiences API: Generally available to all qualified developers:
  Starting August 2026, the Matched Audiences API is now generally available for application to all qualified developers. You can apply for access directly from the Developer Portal.

• DMP Segments API: Cap on number of DMP Segments in ad account:
  Starting August 2026, each sponsored account is restricted to a maximum of 1,000 DMP segments for Matched Audiences (USER, COMPANY, LIST_UPLOAD) and Predictive Audiences. Requests to the /dmpSegments endpoint from ad accounts that exceed this threshold return a 429 error with the code SEGMENT_LIMIT_EXCEEDED. This update applies to all versions. To allocate space for additional segments, delete unused segments before creating new ones. See Delete DMP Segment for details.

• Dynamic UTM API: Ad account-level tracking parameter support:
  Starting with the 202608 version, the /adTrackingParameters endpoint now supports setting dynamic UTM tracking parameters at the ad account level using the sponsoredAccount member of the adEntity key, in addition to the existing sponsoredCampaign. Account-level parameters apply to creatives across all campaigns in the account. This is an additive, backward-compatible change.

• Conversions API: New conversion types for Marketing & Sales Qualified Leads:
  Starting with the 202608 version, the /conversions endpoint now supports MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD as granular conversion types in addition to the existing QUALIFIED_LEAD. Conversion events streamed on conversion rules with these new types are used in the qualified leads optimization goal for deeper funnel campaign optimization, similar to QUALIFIED_LEAD. See Qualified leads optimization goal for details.

• Conversions API: Additional use cases:
  Additional use cases published for the Conversions API, including qualified leads optimization, retargeting audiences, source data for predictive audiences, and conversion lift testing.

Product & Platform Announcements

• Predictive Audiences API: id field available in the response:

  Starting version 202607, fetching a Predictive Audience (single or list) now returns its read-only id. Partners can now obtain the id for audiences created in Campaign Manager or the API, and use it to update them.

• Conversions API: New user identifier available for matching:

  A new optional user identifier SHA256_IP_ADDRESS is available in the userIds object in the Conversion Event User Schema for /rest/conversionEvents to match with the hashed IP address of the user using SHA256. This update is available on all active versions. This is in addition to the existing PLAINTEXT_IP_ADDRESS already available in plain text format. Currently, only IPv4 addresses are supported.

• Create and Manage Campaigns: creativeSelection in SPONSORED_INMAILS type campaigns with LEAD_GENERATION objective for Message & Conversation Ads:

  Starting July 2026, the adCampaigns API will support, as the default, OPTIMIZED for creativeSelection in SPONSORED_INMAILS type campaigns (Message Ads and Conversation Ads) with the LEAD_GENERATION objective. Previously, this combination was rejected with a 400 validation error and forced to ROUND_ROBIN. If your integration creates or updates SPONSORED_INMAILS campaigns with the LEAD_GENERATION objective without explicitly setting creativeSelection, the behavior will default to OPTIMIZED starting with the July 2026 release and will apply to all versions. To preserve even ad rotation, explicitly set creativeSelection as ROUND_ROBIN. Note: OPTIMIZED is only valid for the SPONSORED_INMAILS type with the LEAD_GENERATION objective — all other objectives in this type still reject it with a 400 error.

Version Sunset

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.

• 202507 - Jul 15, 2026
• 202508 - Aug 17, 2026
• 202509 - Sep 15, 2026

Product & Platform Announcements

• Company Intelligence API: 365-Day Lookback and Company Attribute Decoration:

  Starting with the version 202606, the /accountIntelligence endpoint adopts the following changes:

  • filterCriteria.lookbackWindow: A new value LAST_365_DAYS is now supported alongside the existing LAST_7_DAYS, LAST_30_DAYS, LAST_60_DAYS, LAST_90_DAYS, and LAST_180_DAYS. When supplied, engagement and conversion metrics are aggregated over the trailing 365 days from the data calculation date, giving partners a full year of engagement history per target company. Versions 202605 and earlier continue to cap the window at 180 days.
  • companySize: A StaffCountRange enum field representing the range of the number of staff employed by the target company. Possible values are: SIZE_1, SIZE_2_TO_10, SIZE_11_TO_50, SIZE_51_TO_200, SIZE_201_TO_500, SIZE_501_TO_1000, SIZE_1001_TO_5000, SIZE_5001_TO_10000, and SIZE_10001_OR_MORE. The field is response-only, included in the default projection, and defaults to $UNKNOWN when the target company has not declared a staff size.
  • industry: An IndustryUrn field identifying the industry the target company is associated with based on its primary business activities and products (e.g., urn:li:industry:1). The field is response-only, included in the default projection, and defaults to urn:li:industry:0 when no industry has been assigned.
  • countryCode: A string field representing the ISO country code of the target company's headquarters (e.g., "US", "GB"). The field is response-only, included in the default projection, and defaults to an empty string when the headquarters country is not available.
  • costInLocalCurrencyPerPaidQualifiedLead: A double type field representing the cost per paid qualified lead (CPQL) attributed to the target company, in the advertiser's local currency. Derived as the ratio of total ad spend over the number of paid qualified leads collected from members of the target company within the lookback window. The field is response-only, included in the default projection, and defaults to 0.0 when no paid qualified leads have been attributed to the target company within the lookback window.

• Dynamic UTM API: Added dynamic tracking parameter support for CREATIVE_NAME:

  Starting with the version 202606, the /adTrackingParameters endpoint now supports CREATIVE_NAME in addition to existing parameter values in dynamicTrackingParameters field. This will allow advertisers to track creative names along with their creative ID using Dynamic UTM that uses placeholder parameters which are automatically replaced with relevant values when an ad is served. Within Campaign Manager, this is already available within the URL tracking parameters under the Placement tab as {{CREATIVE_NAME}}.

• Conversation Ads API: Not Interested Call-to-Action (CTA):

  A Not Interested CTA is automatically rendered on the firstMessageContent for SponsoredConversations. The CTA is applied to new and existing ads at render time and is not exposed in the API. Use test sends to preview the behavior. For ads created from Campaign Manager, GET requests to /conversationAds/{sponsoredConversationURN}/sponsoredMessageContents will now return a new NOT_INTERESTED value in the replyType field.

• Message Ads API: Not Interested Call-to-Action (CTA)

  A Not Interested CTA is automatically rendered on Message Ads. The CTA is applied to new and existing ads at render time and is not exposed in the API. Use test sends to preview the behavior.

Version Sunset

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.

• 202506 - Jun 15, 2026
• 202507 - Jul 15, 2026
• 202508 - Aug 17, 2026

Reminders

• Change to Developer Support path: Please 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 on June 30th. Please use the form for all new requests as we transition.

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.

Breaking Changes

• Member Post Statistics API and Member Video Statistics API: Starting with the 202605 version, the /memberCreatorPostsAnalytics and /memberCreatorVideoAnalytics endpoints change the format of metricType in the response body from object to string to simplify parsing.

Version Sunset

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.

• 202505 - May 15, 2026
• 202506 - Jun 15, 2026
• 202507 - Jul 15, 2026

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

Starting with the 202605 version, the /memberCreatorPostsAnalytics and /memberCreatorVideoAnalytics endpoints change the format of metricType in the response body from object to string to simplify parsing.

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

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.

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

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 guide.

• 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

Product & Platform Announcements

• Ad Analytics API: New Event and Video Watch Time metrics available

  Starting with the 202601 version, we have introduced two sets of new metrics to be returned for the /AdAnalytics endpoint: EventWatchTime metrics and VideoWatchTime metrics.

  For events, API partners can now measure eventViews, eventWatchTime, averageEventWatchTime and costPerEventView, plus thresholded variants for audiences who watched over 15 seconds, 30 seconds, or 2 minutes. These signals help advertisers better understand audience quality and downstream engagement beyond basic view counts, making it easier to evaluate which events and audiences are driving meaningful attention.

  For video, the videoWatchTime and averageVideoWatchTime metrics are now available. These metrics provide additional data on the duration that sponsored videos are viewed, supporting more detailed analysis of video engagement and viewer retention.

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.

• 202501 - Jan 15, 2026
• 202502 - Feb 16, 2026
• 202503 - Mar 16, 2026