LinkedIn Marketing API 202511 sunsets November 16, 2026: what to check, what to migrate, and which new metrics matter

LinkedIn will sunset Marketing API version 202511 (November 2025) on November 16, 2026. After that date, a request that sends Linkedin-Version: 202511 gets an error response. Any ads reporting, campaign management or Thought Leader Ads integration still pinned to that header needs to move to a supported version first. Microsoft Learn lists 202610 (October 2026) as the latest version, supported until October 15, 2027. Migrating is usually a header change, but the versions between 202511 and 202610 include at least one response-format change and several new fields, so test before you switch.

Last checked: November 9, 2026, against LinkedIn's versioning page, migrations table and recent changes log on Microsoft Learn.

What exactly is sunsetting on November 16, 2026?

LinkedIn versions its Marketing APIs monthly. Each version is identified by a YYYYMM value in the Linkedin-Version request header and is supported for at least one year. The deprecation notice on Microsoft Learn reads: "The Marketing Version 202511 (Marketing November 2025) will be sunset on November 16, 2026."

Source: LinkedIn's API migration status table on Microsoft Learn. The table lists no 202512 version.

Who needs to act?

You need to act if you run or depend on software that calls LinkedIn's Marketing APIs with the 202511 header. That includes:

• Agencies with in-house dashboards that pull LinkedIn ad analytics

• Teams that sync LinkedIn campaign data into a warehouse or BI tool

• Tools that report on Thought Leader Ads or boosted member posts

• Internal scripts for audience uploads, conversions or lead sync

If you only use a third-party tool, ask the vendor which version they call and when they moved. If you can't get an answer before November 16, plan for a reporting gap.

What happens if you miss the date?

LinkedIn's versioning FAQ says an error response is returned when a request uses a deprecated version header. It also says requests with no version header return an error, and the latest version is not applied by default. A missed migration does not quietly upgrade itself. Calls fail, and dashboards built on them stop updating.

How to migrate from 202511 to a current version

1. Find every place the header is set. Search your code and configuration for Linkedin-Version and 202511. Check scheduled jobs and serverless functions, which are easy to forget.

2. Pick the target version. LinkedIn recommends the latest version. On November 9, 2026, that is 202610, supported until October 15, 2027.

3. Read the changes between versions. LinkedIn's recent changes log lists every version. The items in the next section are the ones most likely to affect reporting.

4. Change the header in a test environment. LinkedIn's FAQ describes migration as updating the YYYYMM value, for example from 202501 to 202601.

5. Compare outputs. Run the same report on both versions for the same date range before November 16 and compare field names and values.

6. Ship and monitor. Watch for error responses after the switch, and log the version in each request so the next migration is easier.

Changes between 202511 and 202610 worth testing

These are taken from LinkedIn's recent changes log. The log is the complete list; this is a selection for reporting and agency use.

One more date to note. LinkedIn's 202610 notes describe a required surface field for publisher lists starting with version 202611, with a migration window for existing partner accounts that ends December 15, 2026. If you manage publisher lists, put that date on the same plan.

Which new metrics matter for Thought Leader Ads reporting?

From 202610, /adAnalytics supports two optional metrics that LinkedIn says exist only for Sponsored Updates and member follower display ads, such as Thought Leader Ads:

• memberFollows: the count of sponsored member profile follows

• memberProfileClicks: the count of clicks on the profile of the member who owns the sponsored post

For agencies running executive ads, these answer a question clients ask: did the spend grow the executive's audience, or only the post's reach? You only get them after migrating to 202610 or later, and only if you request them.

Both are counts. They tell you how many people followed or clicked, and the API does not return who they were. If a client wants to follow up with the people engaging around an executive's content, that is a different job from ads reporting. Our guide to LinkedIn Thought Leader Ads strategies covers the format itself.

Where traxy fits (and where it doesn't)

traxy is not a LinkedIn ads reporting tool, and this migration does not involve it. If you use traxy alongside your ads stack, the jobs stay separate:

• Marketing API reporting gives aggregate counts for campaigns and sponsored posts.

• traxy finds qualified people from LinkedIn engagement on the profiles and posts you track, scores each one against your lead criteria, and shows the recorded signal (how qualification works).

For example, if an executive's organic posts are getting traction, you can track the executive's profile in traxy with a Teammate relationship and review who engages and fits your criteria. For older posts, submit the post URL as a tracked post (tracking). For company content, see find leads from the people who engage with a LinkedIn company page.

Migration checklist

• [ ] Search code and config for Linkedin-Version: 202511

• [ ] Ask each vendor that calls LinkedIn's Marketing API which version they use

• [ ] Choose a target version (latest on Nov 9, 2026: 202610)

• [ ] Review LinkedIn's recent changes log from 202601 to your target

• [ ] Update parsers for the 202605 metricType string change if you read member creator analytics

• [ ] Run side-by-side reports before November 16, 2026

• [ ] Add memberFollows and memberProfileClicks to Thought Leader Ads reports if useful

• [ ] Note the December 15, 2026 publisher list deadline if it applies

• [ ] Log the version on every request

FAQ

Is 202511 the latest LinkedIn Marketing API version?

No. On November 9, 2026, Microsoft Learn lists 202610 (October 2026) as the latest version.

How long is each LinkedIn Marketing API version supported?

LinkedIn says monthly versions are supported for a minimum of one year. The migrations table lists each version's sunset date.

Can I skip to the newest version directly?

Yes. LinkedIn says you can migrate to any later version, and recommends the latest so you can wait up to a year before migrating again.

What if my request has no version header?

LinkedIn's FAQ says an error response is returned. The latest version is not applied by default.

Where do I ask LinkedIn about migration problems?

The deprecation notice points to the LinkedIn Developer Support Portal.

Next step

Search your codebase for 202511 today, and list every vendor that touches your LinkedIn ads data. If you also want the people behind the engagement on organic posts, read how to message LinkedIn post engagers without sounding creepy, then try traxy on one executive's profile.