LinkedIn Marketing API · Status at source date: Version retired
LinkedIn Marketing API 202509 has passed its retirement date
LinkedIn now marks Marketing API version 202509 as deprecated after its 15 September 2026 sunset. Confirm that reporting and campaign integrations use a supported version.
This update uses a PMC cover because no suitable source image was available when checked on 8 Sept 2026. Available source and video links are retained.
What changed
LinkedIn’s current migration table marks Marketing API version 202509 as deprecated and retains 15 September 2026 as its sunset date. The deadline has passed. The September release notes identify 202609 as the latest version and list 15 October 2026 as the next sunset, for version 202510. These are API maintenance dates, not evidence that a particular advertiser’s connector has failed.
The version identifies the API contract an integration uses, rather than the dates of the campaigns or reports it retrieves. Teams still analysing older campaign data need a supported API version too. A reporting period and a release version answer different questions, so a historical export should not be assumed to require an obsolete version.
Start with the workflows that run without someone watching them: reporting connectors, scheduled exports and internal tools. Ask each owner or vendor which version their requests use and whether migration is complete. A successful sign-in or an old report in a dashboard does not establish that the latest scheduled request succeeded. Inspect a recent run and its output before treating the migration as finished.
Why it matters for advertisers
The useful outcome is continuity of the business process. Review the migration guidance for the endpoints each integration actually uses, confirm a supported destination version and compare representative output. For reporting, check expected fields, date ranges and downstream totals. Campaign creation or editing needs its own validation. If the team uses a third-party connector, request its current migration status rather than assuming that a local account setting controls its API version. This source check does not certify any connector, script or live advertising workflow.
What to check next
- Confirm the requested API version and migration status with each reporting or campaign-integration owner.
- Validate recent scheduled runs and their downstream output; investigate gaps without assuming this retirement caused them.
- Review the next 202510 sunset on 15 October 2026 and plan changes against LinkedIn’s current supported-version table.
Sources & contributor credit
- Official documentation or announcement · LinkedIn / Microsoft Learn
Recent Marketing API Changes. August 2026 release section; exact publication day unknown. Version sunset table inspected.
- Official release month · LinkedIn Marketing API release notes
The August release section records the 15 September 2026 sunset. The same page now includes September 202609 notes; the original release month and site publication date remain separate.
- Documentation checked · Checked LinkedIn Marketing API versioning
Explains the Linkedin-Version request header. This is the check date, not a publication date.
- Documentation checked · Checked LinkedIn Marketing API migrations
The current migration table marks 202509 deprecated after its 15 September sunset and 202609 active. Rechecked 18 September 2026. No specific integration was executed or certified.
- Official release month · LinkedIn September 2026 release notes
September 202609 is labelled latest; 202510 is scheduled to sunset on 15 October 2026. Exact publication day is not established.
Original creator unverified
Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.
Attribution evidence and limitations
Full attribution review pending.
A source link alone does not establish original authorship.
Original image and video creators have not yet been verified.
- Published on this site
- Article updated
This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.


