<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LinkedIn API changes | Schedule Social Media</title><description>New entries in the LinkedIn API changelog, each linked to the platform&apos;s own announcement.</description><link>https://schedulesocialmedia.com/</link><language>en</language><atom:link href="https://schedulesocialmedia.com/api-changes/rss/linkedin.xml" rel="self" type="application/rss+xml"/><item><title>LinkedIn Boost API 202611: saved audiences, boost management, hosted billing, per-campaign analytics</title><link>https://schedulesocialmedia.com/api-changes/linkedin-boost-api-targeting-management-202611/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-boost-api-targeting-management-202611/</guid><description>Breaking, effective 2026-11. Apps that boost LinkedIn posts gain simplified targeting and saved audiences, read, edit and delete for live boosts, a LinkedIn-hosted billing link and a political-intent declaration in version 202611. Boost Analytics changes shape: metrics now come per campaign, with spend in local currency. What to do: When moving Boost calls to Linkedin-Version 202611, read analytics from the new campaigns array, move delete calls to the Boost Manage resources, and send advertisers to the returned billingUrl instead of collecting payment details.</description><pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn adds Boost API: turn member and Company Page posts into ads from your app</title><link>https://schedulesocialmedia.com/api-changes/linkedin-boost-api-posts-2026-10/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-boost-api-posts-2026-10/</guid><description>New feature, effective 2026-10. Apps approved for the Advertising API can check if a post can be boosted, preview reach and cost, launch the boost, stop it and read its results, for member and Company Page posts. What to do: Optional. To offer boosting, get Advertising API approval with the boost scopes and send Linkedin-Version 202610 or later.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn Marketing API version sunset calendar: every version and its end date</title><link>https://schedulesocialmedia.com/api-changes/linkedin-marketing-api-version-sunset-calendar-2026-10/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-marketing-api-version-sunset-calendar-2026-10/</guid><description>Deprecation. Every monthly LinkedIn Marketing API version stops working on a fixed sunset date, about a year after release. Calls that send a sunset Linkedin-Version header fail, including Posts, Images, Videos and analytics calls. What to do: Find the Linkedin-Version value your integration sends, look up its sunset date below, and move to a newer version well before that date. Plan one upgrade at least once a year.</description><pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Deprecation</category></item><item><title>LinkedIn removes the location field from /v2/me and /v2/people: use geoLocation</title><link>https://schedulesocialmedia.com/api-changes/linkedin-profile-location-field-removed-2026-08/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-profile-location-field-removed-2026-08/</guid><description>Deprecation. Apps that read a member&apos;s location text (such as &quot;San Francisco Bay Area&quot;) from the Profile API may start getting an empty or null value and need to switch to the geoLocation field. What to do: Request geoLocation with the geo~ projection instead of location, and handle an empty location value from now on.</description><pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Deprecation</category></item><item><title>LinkedIn Events API: endsAt required from 202605, no edits once an event starts</title><link>https://schedulesocialmedia.com/api-changes/linkedin-events-api-endsat-required-no-updates-after-start-2026-05/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-events-api-endsat-required-no-updates-after-start-2026-05/</guid><description>Breaking, effective 2026-05. From version 202605, creating a LinkedIn Event without an end time fails. LinkedIn&apos;s docs also say an event can&apos;t be edited once it has started, and live audio events are deprecated. What to do: Always send endsAt when creating events on 202605 or later, make all edits before startsAt, and stop offering live audio events.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn moves developer support to a request form and lets apps reapply for API access</title><link>https://schedulesocialmedia.com/api-changes/linkedin-developer-support-form-reapply-api-access-2026-05/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-developer-support-form-reapply-api-access-2026-05/</guid><description>Policy, effective 2026-05-15. Since May 15, 2026, LinkedIn developer support runs through the Developer Support Request Form, and the Zendesk path ended on June 30. Expired or declined API product requests can now be resubmitted from the Developer Portal. What to do: Send new support cases through the Developer Support Request Form, and use the Reapply button for expired or declined access requests instead of creating a new app.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Policy</category></item><item><title>LinkedIn: Member post and video analytics return metricType as a string</title><link>https://schedulesocialmedia.com/api-changes/linkedin-member-post-analytics-metrictype-string/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-member-post-analytics-metrictype-string/</guid><description>Breaking, effective 2026-05. Apps reading /memberCreatorPostAnalytics or /memberCreatorVideoAnalytics must parse metricType as a string when they upgrade to version 202605 or later.</description><pubDate>Fri, 01 May 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn publishes integration requirements for partner certification, including Community Management</title><link>https://schedulesocialmedia.com/api-changes/linkedin-integration-requirements-partner-certification-2026-04/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-integration-requirements-partner-certification-2026-04/</guid><description>Policy, effective 2026-04. Partners seeking LinkedIn partner certification now have written lists of the capabilities they must build and demo, per API program, including posting, comments, analytics, token handling and webhooks for Community Management. What to do: If you pursue certification, map your product against the requirements page for each API you use and plan the missing features before asking for Technical Sign Off.</description><pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Policy</category></item><item><title>LinkedIn Member Post Statistics adds saves, sends, link clicks and follower metrics in 202604</title><link>https://schedulesocialmedia.com/api-changes/linkedin-member-post-statistics-new-metrics-202604/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-member-post-statistics-new-metrics-202604/</guid><description>New feature. Creator post analytics now include sends, saves, link clicks, Premium CTA clicks, followers gained and profile views from content. What to do: Use version 202604 or later and request the new metric types if you want them in reports.</description><pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn Videos API adds templateName and linkbackContext for third-party made videos</title><link>https://schedulesocialmedia.com/api-changes/linkedin-videos-api-template-linkback-202602/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-videos-api-template-linkback-202602/</guid><description>New feature. Tools that create videos for LinkedIn posts can attribute those videos to the creating tool. What to do: Optional. Send templateName and linkbackContext on uploads in version 202602 or later if you want attribution.</description><pubDate>Sun, 01 Feb 2026 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn OAuth login adds Sign in with Google and Sign in with Apple from December 2, 2025</title><link>https://schedulesocialmedia.com/api-changes/linkedin-google-apple-sign-in-oauth-2025-11/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-google-apple-sign-in-oauth-2025-11/</guid><description>Policy, effective 2025-12-02. Members connecting a LinkedIn account to an app through OAuth can log in to LinkedIn with Google or Apple, alongside username and password, on desktop and Android web browsers. What to do: Test your LinkedIn connect flow with the Google and Apple options. Follow the standard OAuth pattern for native apps (RFC 8252), and use enable_extended_login=true if you need the options outside desktop and Android browsers.</description><pubDate>Sat, 01 Nov 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Policy</category></item><item><title>LinkedIn Marketing API version 202511 sunsets November 16, 2026</title><link>https://schedulesocialmedia.com/api-changes/linkedin-marketing-api-202511-sunset/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-marketing-api-202511-sunset/</guid><description>Deprecation, effective 2026-11-16. Integrations sending Linkedin-Version: 202511 must move to a newer version header before November 16, 2026; 202601 follows on January 15, 2027.</description><pubDate>Sat, 01 Nov 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Deprecation</category></item><item><title>LinkedIn Developer Portal shows OAuth refresh token usage and throttling per app</title><link>https://schedulesocialmedia.com/api-changes/linkedin-oauth-refresh-token-usage-dashboard-2025-10/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-oauth-refresh-token-usage-dashboard-2025-10/</guid><description>New feature, effective 2025-09. Developers can now see how much of their app&apos;s daily quota for minting access tokens from refresh tokens they have used, and whether the app is currently throttled. What to do: Open the Analytics tab of your app in the Developer Portal, watch the OAuth Token Usage table, and spread token refreshes so you don&apos;t hit the daily quota.</description><pubDate>Wed, 01 Oct 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn emails app admins at 75 percent of the daily API quota</title><link>https://schedulesocialmedia.com/api-changes/linkedin-rate-limit-alerts-75-percent-2025-09/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-rate-limit-alerts-75-percent-2025-09/</guid><description>New feature. App owners now get a warning before a LinkedIn API app runs out of its daily request allowance. What to do: Make sure every admin on your LinkedIn developer app reads the email address on their account: all of them receive the alert.</description><pubDate>Mon, 01 Sep 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn adds member follower, post and video statistics APIs</title><link>https://schedulesocialmedia.com/api-changes/linkedin-member-analytics-apis-launch-2025-06/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-member-analytics-apis-launch-2025-06/</guid><description>New feature. Third-party tools can now read a member&apos;s own follower counts, post analytics and video analytics, with new permissions. What to do: Request r_member_profileAnalytics for follower statistics and r_member_postAnalytics for post and video statistics, and use version 202506 or later for the post endpoints.</description><pubDate>Sun, 01 Jun 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn Posts API accepts BUY_NOW and SHOP_NOW call-to-action labels in 202504</title><link>https://schedulesocialmedia.com/api-changes/linkedin-posts-api-shop-now-cta-202504/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-posts-api-shop-now-cta-202504/</guid><description>New feature. Posts created through the API can use Buy Now or Shop Now buttons when the label is available for the post. What to do: Optional. Use version 202504 or later and set contentCallToActionLabel only where LinkedIn makes the label available.</description><pubDate>Tue, 01 Apr 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn adds the Events Management API: create, schedule and manage LinkedIn Events from your app</title><link>https://schedulesocialmedia.com/api-changes/linkedin-events-management-api-launch-2025-02/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-events-management-api-launch-2025-02/</guid><description>New feature, effective 2025-02. Apps can now create, update and delete LinkedIn Events (LinkedIn Live or external) for a Company Page, with an optional custom registration form, and then share them with the Page&apos;s followers through a post. What to do: Optional. To offer LinkedIn Events, request the Events Management API product in the Developer Portal and add the r_events and rw_events permissions to your OAuth flow.</description><pubDate>Sat, 01 Feb 2025 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn developer apps must be associated with and verified by a Company Page</title><link>https://schedulesocialmedia.com/api-changes/linkedin-developer-app-company-page-verification-2024-10/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-developer-app-company-page-verification-2024-10/</guid><description>Policy. A LinkedIn developer app needs to be linked to a LinkedIn Company Page, and approved by that Page&apos;s super admin, to get the features of the Marketing API products. What to do: In the Developer Portal, associate the app with your organization&apos;s Company Page and have the Page super admin approve the verification request.</description><pubDate>Tue, 01 Oct 2024 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Policy</category></item><item><title>LinkedIn Posts API can fetch celebration posts from version 202404</title><link>https://schedulesocialmedia.com/api-changes/linkedin-posts-api-celebration-posts-202404/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-posts-api-celebration-posts-202404/</guid><description>New feature. Tools can read celebration-type posts through the Posts API, which they could not before. What to do: Use version 202404 or later if you want celebration posts to appear when you fetch posts.</description><pubDate>Mon, 01 Apr 2024 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn sunsets API versions 202306, 202307 and 202312 on December 16, 2024</title><link>https://schedulesocialmedia.com/api-changes/linkedin-versions-202306-202307-202312-sunset/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-versions-202306-202307-202312-sunset/</guid><description>Deprecation, effective 2024-12-16. Requests that still send Linkedin-Version 202306, 202307 or 202312 fail after December 16, 2024. What to do: Move to a currently supported version before December 16, 2024.</description><pubDate>Fri, 01 Mar 2024 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Deprecation</category></item><item><title>LinkedIn Page Statistics replaces region and country fields with Geo fields in 202401</title><link>https://schedulesocialmedia.com/api-changes/linkedin-page-statistics-geo-fields-202401/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-page-statistics-geo-fields-202401/</guid><description>Breaking. Page follower demographics by region and country are replaced by Bing Geo market area and country fields, so existing parsers break on the new version. What to do: Switch to pageStatisticsByGeo and pageStatisticsByGeoCountry when you adopt version 202401 or later.</description><pubDate>Mon, 01 Jan 2024 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn Comments and Reactions APIs change fields in version 202307</title><link>https://schedulesocialmedia.com/api-changes/linkedin-comments-reactions-api-id-field-202307/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-comments-reactions-api-id-field-202307/</guid><description>Breaking. From version 202307 the MAYBE reaction is rejected with a 400 error, and the $URN and digitalmediaAsset fields are replaced by id and image. What to do: When moving to version 202307 or later, read the id field instead of $URN, use image instead of digitalmediaAsset, and stop sending the MAYBE reaction.</description><pubDate>Sat, 01 Jul 2023 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn Posts API raises the multi-image post limit from 9 to 20 images</title><link>https://schedulesocialmedia.com/api-changes/linkedin-posts-api-multi-image-max-20/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-posts-api-multi-image-max-20/</guid><description>New feature. Organic multi-image posts created through the API can now carry up to 20 images instead of 9. What to do: No action needed to keep working. Update any image-count validation in your composer if it still caps at 9.</description><pubDate>Sat, 01 Jul 2023 00:00:00 GMT</pubDate><category>LinkedIn</category><category>New feature</category></item><item><title>LinkedIn accepts only POST for access and refresh token requests after June 30, 2023</title><link>https://schedulesocialmedia.com/api-changes/linkedin-access-token-requests-post-only-2023/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-access-token-requests-post-only-2023/</guid><description>Breaking, effective 2023-06-30. Token exchange and refresh calls made with GET /accessToken return a 400 error after June 30, 2023. What to do: Send access token and refresh token requests with POST to /accessToken, header Content-Type set to x-www-form-urlencoded, and all parameters in the request body.</description><pubDate>Wed, 01 Mar 2023 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn requires migration to the new Community Management API by June 30, 2023</title><link>https://schedulesocialmedia.com/api-changes/linkedin-community-management-api-migration-2023/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-community-management-api-migration-2023/</guid><description>Breaking, effective 2023-06-30. Organic posting and community tools had to apply for and move to the new Community Management API, because the legacy community management permissions were removed. What to do: Apply for the Community Management API product in the LinkedIn Developer Portal and follow the migration guide. The legacy permissions were removed on June 30, 2023.</description><pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item><item><title>LinkedIn sunsets the legacy Shares and UGC Posts APIs and unversioned APIs</title><link>https://schedulesocialmedia.com/api-changes/linkedin-shares-ugc-posts-apis-sunset-2023/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/linkedin-shares-ugc-posts-apis-sunset-2023/</guid><description>Breaking, effective 2023-06-30. Integrations still calling the Shares API, the UGC Posts API or unversioned endpoints stop working and must move to the versioned Posts, Images and Videos APIs. What to do: Move to the versioned Posts API (https://api.linkedin.com/rest/posts) and send the Linkedin-Version header. The cutoff was June 30, 2023.</description><pubDate>Sun, 01 Jan 2023 00:00:00 GMT</pubDate><category>LinkedIn</category><category>Breaking</category></item></channel></rss>