LinkedIn API sunsets: 202510, 202511 and 202601 dates, and the upgrade
LinkedIn lists 202510 sunsetting October 15, 2026, 202511 on November 16, 2026 and 202601 on January 15, 2027. Pick one target and test with a Sume clip.
LinkedIn's migration table lists version 202510 sunsetting on October 15, 2026, 202511 on November 16, 2026, and 202601 on January 15, 2027. The latest listed is 202609, with a sunset of September 15, 2027, so moving a video poster to the newest version buys the longest runway.
A version change is a header change: replace the YYYYMM value in Linkedin-Version. The render step on Sume does not change.
Which dates matter now?
These rows come from LinkedIn's API migration status table.
| Version | Sunset date | Status on the page |
|---|---|---|
| 202509 (September 2025) | September 15, 2026 | Deprecated |
| 202510 (October 2025) | October 15, 2026 | Active |
| 202511 (November 2025) | November 16, 2026 | Active |
| 202601 (January 2026) | January 15, 2027 | Active |
| 202609 (September 2026) | September 15, 2027 | Active, latest |
What is a sensible upgrade plan?
Pick the latest version, change the header in config, and run one posting flow end to end before you ship. A short clip is enough: submit it on Sume with sume/auto, wait for completed, and post it with the new header. The existing post on the 202510 sunset covers what to change in the calls themselves.
- List every service that sets
Linkedin-Version. - Move all of them to one shared setting.
- Add the next sunset date to a calendar the day you pick a version.
- Keep Sume job ids in your database so a re-post never needs a re-render.
Sources
Related posts
More in Developers
- LinkedIn missing or deprecated version header errors: fail in CI
LinkedIn answers a missing or deprecated Linkedin-Version header with an error response. Check the header in CI, before a video post fails at runtime.
- LinkedIn-Version has no default: pin YYYYMM in your video poster
LinkedIn does not apply the latest API version when the header is missing. Pin a YYYYMM value in config and fail loudly if it is unset.
- Verify a Sume job webhook in Python, and refuse an empty secret
A Python verifier for Sume job webhooks: HMAC SHA 256 over timestamp.body, a 5-minute window, rotation-safe, and a hard refusal when the secret is empty.
- LiveKit avatar join latency and playback latency: what to measure
LiveKit avatar plugins emit join latency and playback latency. Learn what each means before you pick a live avatar, and what a rendered clip has instead.
Written by Sume