# AdStack Watch > Ad & martech platform changelog + GTM price tracker. A structured, source-linked record of API version sunsets, deprecations, breaking changes, policy changes, tracking/signal-loss changes and ad format changes across Google Ads, Meta (Graph & Marketing API), LinkedIn Marketing API, TikTok Ads, Shopify, HubSpot, Salesforce; plus plan/price/usage-credit history for GTM tools (Apollo.io, Clay, ZoomInfo, HubSpot Sales Hub, HubSpot Marketing Hub, Instantly, Smartlead, lemlist, Artisan (AI SDR), AiSDR, Salesforce Sales Cloud, Salesforce Agentforce (add-ons & Flex Credits)). Every record has a stable `id`, dates (`published_date`, `effective_date` + precision), `source_url` (official) and `fetched_at`. Data as of 2026-10-17T03:44:51Z: 693 change records (71 upcoming deadlines, of which 24 are unreleased versions with tentative dates), 12 tools, 50 price-history events. ## Machine-readable data - [All changes (JSON)](https://adstackwatch.com/api/changes.json): every change record - [Upcoming deadlines (JSON)](https://adstackwatch.com/api/upcoming.json): effective on/after today, soonest first - [Per-platform changes](https://adstackwatch.com/api/platforms.json): index; files at /api/changes/{platform}.json for google-ads, meta, linkedin, tiktok, shopify, hubspot, salesforce - [GTM prices (JSON)](https://adstackwatch.com/api/prices.json) and [price history](https://adstackwatch.com/api/price-history.json); per tool at /api/prices/{tool_id}.json - [OpenAPI 3.1 spec](https://adstackwatch.com/openapi.json) - [Atom feed](https://adstackwatch.com/feed.xml), [RSS](https://adstackwatch.com/rss.xml) - [Full text for LLMs](https://adstackwatch.com/llms-full.txt) ## MCP - A Model Context Protocol server (stdio + streamable HTTP) exposes search_changes, get_upcoming_deprecations, get_change, list_platforms, get_tool_pricing, get_price_history. See [https://adstackwatch.com/developers/](https://adstackwatch.com/developers/). ## Pages - [Upcoming deadlines](https://adstackwatch.com/deadlines/) - [Search all changes](https://adstackwatch.com/changes/) (supports ?q=&platform=&category=&upcoming=1) - [Google Ads](https://adstackwatch.com/platforms/google-ads/) - [Meta (Graph & Marketing API)](https://adstackwatch.com/platforms/meta/) - [LinkedIn Marketing API](https://adstackwatch.com/platforms/linkedin/) - [TikTok Ads](https://adstackwatch.com/platforms/tiktok/) - [Shopify](https://adstackwatch.com/platforms/shopify/) - [HubSpot](https://adstackwatch.com/platforms/hubspot/) - [Salesforce](https://adstackwatch.com/platforms/salesforce/) - [GTM price tracker](https://adstackwatch.com/pricing/) - [Weekly digest](https://adstackwatch.com/newsletter/) ## Usage notes - Cite `source_url` when relaying a fact; treat summaries as extracts of the official text. - `effective_date_precision` is `day` or `month`; month-level dates are as published by the platform. - Prices are as displayed on vendor pages at `fetched_at`; check `unit_text`, `billing` and the plan excerpt for billing period. - `tentative: true` marks unreleased versions whose dates the platform calls tentative; `in_source: false` marks records no longer listed by their source. - Licence: compilation CC BY 4.0 (credit AdStack Watch); source text under its owners' terms. --- # Upcoming deadlines - 2026-10-23 | Shopify | New tax fields for return shipping fees in the GraphQL Admin API | As of API version 2026-10, the GraphQL Admin API exposes the tax amounts calculated for return shipping fees. These amounts reflect the tax calculated by the merchant's tax provider for the fee. | source: https://shopify.dev/changelog/new-return-shipping-fee-tax-fields | id: shopify-6c57d48c76 - 2026-11-02 | Shopify | Global Catalog REST API stops serving traffic on November 2, 2026 | The Global Catalog REST API, which was deprecated in April 2026, stops serving traffic on November 2, 2026. If your app still calls it, you need to migrate to Global Catalog MCP, which implements the Universal Commerce Protocol (UCP), before that date. | source: https://shopify.dev/changelog/global-catalog-rest-api-stops-serving-traffic-on-november-2-2026 | id: shopify-b9a63bd92b - 2026-11-16 | LinkedIn Marketing API | LinkedIn Marketing API version 202511 (November 2025) sunset on November 16, 2026 | Developers using LinkedIn Marketing APIs version 202511 (November 2025) to migrate to the latest versions. Sunset date: November 16, 2026. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-b117c8c38c - 2026-12-01 | Shopify | Built for Shopify requirements for Returns and exchanges apps and Subscription apps (effective December 1, 2026) | Effective December 1, 2026 , Returns and exchanges apps and Subscription apps that provide buyer-facing self-service experiences must authenticate customers using the Customer Account API. Apps that don't meet this requirement by the deadline are at risk of losing Built for Shopify status . | source: https://shopify.dev/changelog/built-for-shopify-requirements-for-returns-and-exchanges-and-subscription-apps | id: shopify-3298dec977 - 2026-12-04 | HubSpot | Pipelines API V1 Sunset: December 4, 2026 | HubSpot will sunset the Pipelines API V1 on December 4, 2026 . After this date, the API will no longer be supported. If your integration relies on V1 endpoints, you'll need to migrate to the 2026-03 or newer version before the deadline to avoid disruption. | source: https://developers.hubspot.com/changelog/pipelines-api-v1-sunset | id: hubspot-cb3daa6483 - 2026-12-15 | LinkedIn Marketing API | Campaign Management API: New required surface field for publisher lists (action required) (October 2026 - Version 202610 (Latest)) | 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). | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes | id: linkedin-90cdc0c816 - 2026-12-15 | Salesforce | Salesforce retirement: Standard-Volume Platform Events (December 15, 2026) | Salesforce lists "Standard-Volume Platform Events" on its Active Product & Feature Retirements page with timing: December 15, 2026. | source: https://help.salesforce.com/s/articleView?id=002280033&type=1&language=en_US | id: salesforce-9749b01f80 - 2026-12-31 | Salesforce | Salesforce retirement: Data Mask Managed Package End of Support (December 31, 2026) | Salesforce lists "Data Mask Managed Package End of Support" on its Active Product & Feature Retirements page with timing: December 31, 2026. | source: https://help.salesforce.com/s/articleView?id=005299299&type=1&language=en_US | id: salesforce-071936ef8e - 2027-01-01 | TikTok Ads | TikTok API: non-Search Legacy Manual Flow campaign creation ends; migrate to Upgraded Smart+ APIs | Starting January 1, 2027, /campaign/create/ , /campaign/copy/task/create/ , /adgroup/create/ , /ad/create/ , and /ad/aco/create/ will no longer support creating or copying non-Search Legacy Manual Flow campaigns, or creating ad groups or ads under them, for Sales, App Promotion, and Lead Generation objectives. Please migrate affected workflows to the Upgraded Smart+ APIs as soon as possible. | source: https://business-api.tiktok.com/portal/docs?id=1740029171730433 | id: tiktok-4bb33d838c - 2027-01-01 | Shopify | Expiring offline access tokens required for all public apps as of January 1, 2027 | We're changing how public apps handle offline access tokens to enhance merchant data protection. Starting January 1, 2027, all public apps must use expiring offline access tokens when calling the Admin API. After that date, public apps still using non-expiring tokens will receive authentication errors. | source: https://shopify.dev/changelog/expiring-offline-access-tokens-required-for-all-public-apps-as-of-january-1-2027 | id: shopify-c6bf4ebc4f - 2027-01-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202601 (January 2026) sunset on January 15, 2027 | Developers using LinkedIn Marketing APIs version 202601 (January 2026) to migrate to the latest versions. Sunset date: January 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-82a2ae909a - 2027-01-21 | Meta (Graph & Marketing API) | Meta Graph API v21.0 expiration (January 21, 2027) | Meta Graph API v21.0 was released October 2, 2024. Listed expiration date: January 21, 2027. | source: https://developers.facebook.com/docs/graph-api/changelog/versions | id: meta-55a6e88121 - 2027-01-28 | Google Ads | Deprecating Structured Data Files v9, v9.1, and v9.2 | Today we’re announcing the deprecation of Structured Data Files v9 , v9.1 , and v9.2 . These three versions will all sunset on January 28, 2027 . Migrate to v10 or higher before the sunset date to avoid any interruption of service. | source: https://ads-developers.googleblog.com/2026/06/deprecating-structured-data-files-v9.html | id: google-ads-4bf0d3beae - 2027-01-30 | Salesforce | Salesforce retirement: Salesforce for Outlook (January 30, 2027) | Salesforce lists "Salesforce for Outlook" on its Active Product & Feature Retirements page with timing: January 30, 2027. | source: https://help.salesforce.com/s/articleView?id=000353024&language=en_US&type=1&mode=1 | id: salesforce-0da1bbb931 - 2027-02 | Google Ads | Google Ads API v23 sunset (February 2027) | Google Ads API v23 was released on January 28, 2026; its listed sunset date is February 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-4f862a77d8 - 2027-02 | Google Ads | Google Ads API v23.1 sunset (February 2027) | Google Ads API v23.1 was released on February 25, 2026; its listed sunset date is February 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-62e47032a9 - 2027-02 | Google Ads | Google Ads API v23.2 sunset (February 2027) | Google Ads API v23.2 was released on March 25, 2026; its listed sunset date is February 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-144ee74d52 - 2027-02 | Salesforce | Salesforce retirement: EAC Activity Metrics, Dashboard, Recommended Connections and A360 Reports (Spring '27 - Feb 2027) | Salesforce lists "EAC Activity Metrics, Dashboard, Recommended Connections and A360 Reports" on its Active Product & Feature Retirements page with timing: Spring '27 - Feb 2027. | source: https://help.salesforce.com/s/articleView?id=005384640&type=1&language=en_US | id: salesforce-cbf6080a45 - 2027-02 | Salesforce | Salesforce retirement: Salesforce-to-Salesforce (Spring '27 - Feb 2027) | Salesforce lists "Salesforce-to-Salesforce" on its Active Product & Feature Retirements page with timing: Spring '27 - Feb 2027. | source: https://help.salesforce.com/s/articleView?id=005103355&type=1&language=en_US | id: salesforce-fad6492a77 - 2027-02-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202602 (February 2026) sunset on February 15, 2027 | Developers using LinkedIn Marketing APIs version 202602 (February 2026) to migrate to the latest versions. Sunset date: February 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-046d762ee9 - 2027-03-16 | LinkedIn Marketing API | LinkedIn Marketing API version 202603 (March 2026) sunset on March 16, 2027 | Developers using LinkedIn Marketing APIs version 202603 (March 2026) to migrate to the latest versions. Sunset date: March 16, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-71a4c6da2b - 2027-04-01 | Salesforce | Salesforce retirement: Einstein Relationship Insights (April 1, 2027) | Salesforce lists "Einstein Relationship Insights" on its Active Product & Feature Retirements page with timing: April 1, 2027. | source: https://help.salesforce.com/s/articleView?id=005385568&type=1&language=en_US | id: salesforce-19d624ed01 - 2027-04-01 | Salesforce | Salesforce retirement: Lightning Sync (April 1, 2027) | Salesforce lists "Lightning Sync" on its Active Product & Feature Retirements page with timing: April 1, 2027. | source: https://help.salesforce.com/s/articleView?id=005321528&type=1&language=en_US | id: salesforce-76ded56eff - 2027-04-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202604 (April 2026) sunset on April 15, 2027 | Developers using LinkedIn Marketing APIs version 202604 (April 2026) to migrate to the latest versions. Sunset date: April 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-752ccbae9e - 2027-05-01 | Shopify | Polaris 2.0 release candidate | The Polaris 2.0 release candidate is now available for embedded App Home interfaces. It includes the Shopify admin’s new visual styles, allowing your app to adopt the new look. The new Shopify admin design began rolling out progressively to merchants on September 15, 2026. | source: https://shopify.dev/changelog/polaris-2-0-release-candidate | id: shopify-20201458a4 - 2027-05 | Google Ads | Google Ads API v24 sunset (May 2027) | Google Ads API v24 was released on April 22, 2026; its listed sunset date is May 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-de3be13f45 - 2027-05 | Google Ads | Google Ads API v24.1 sunset (May 2027) | Google Ads API v24.1 was released on May 13, 2026; its listed sunset date is May 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-ae7699e698 - 2027-05-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202605 (May 2026) sunset on May 15, 2027 | Developers using LinkedIn Marketing APIs version 202605 (May 2026) to migrate to the latest versions. Sunset date: May 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-a019bbf466 - 2027-05-20 | Meta (Graph & Marketing API) | Meta Graph API v22.0 expiration (May 20, 2027) | Meta Graph API v22.0 was released January 21, 2025. Listed expiration date: May 20, 2027. | source: https://developers.facebook.com/docs/graph-api/changelog/versions | id: meta-3170627adb - 2027-06 | Google Ads | Google Ads API v24.2 sunset (June 2027) | Google Ads API v24.2 was released on June 24, 2026; its listed sunset date is June 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-d5fe74e03d - 2027-06 | Salesforce | Salesforce retirement: SOAP API login() (Summer '27 - June 2027) | Salesforce lists "SOAP API login()" on its Active Product & Feature Retirements page with timing: Summer '27 - June 2027. | source: https://help.salesforce.com/s/articleView?language=en_US&id=005132110&type=1 | id: salesforce-ed27f3cb6b - 2027-06-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202606 (June 2026) sunset on June 15, 2027 | Developers using LinkedIn Marketing APIs version 202606 (June 2026) to migrate to the latest versions. Sunset date: June 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-58ce926b2b - 2027-06-30 | Google Ads | Announcing Google Mobile Ads Next-Gen SDK as the preferred SDK for Android | Google Mobile Ads (GMA) Next-Gen SDK is now the preferred SDK for Android development with Google AdMob and Google Ad Manager. GMA Next-Gen SDK is a significant rewrite of Google Mobile Ads SDK that improves speed, stability, and the developer experience. Google Mobile Ads SDK for Android is now legacy. | source: https://ads-developers.googleblog.com/2026/07/announcing-google-mobile-ads-next-gen.html | id: google-ads-5ee48a926e - 2027-07-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202607 (July 2026) sunset on July 15, 2027 | Developers using LinkedIn Marketing APIs version 202607 (July 2026) to migrate to the latest versions. Sunset date: July 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-9e2f89e72a - 2027-08 | Google Ads | Google Ads API v25 sunset (August 2027) | Google Ads API v25 was released on July 22, 2026; its listed sunset date is August 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-7ec370f560 - 2027-08 | Google Ads | Google Ads API v25.1 sunset (August 2027) | Google Ads API v25.1 was released on August 19, 2026; its listed sunset date is August 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-68ff2d742b - 2027-08 | Google Ads | Google Ads API v25.2 sunset (August 2027) | Google Ads API v25.2 was released on September 23, 2026; its listed sunset date is August 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-c737dbdf5b - 2027-08-17 | LinkedIn Marketing API | LinkedIn Marketing API version 202608 (August 2026) sunset on August 17, 2027 | Developers using LinkedIn Marketing APIs version 202608 (August 2026) to migrate to the latest versions. Sunset date: August 17, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-84f8fe25cc - 2027-09-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202609 (September 2026) sunset on September 15, 2027 | Developers using LinkedIn Marketing APIs version 202609 (September 2026) to migrate to the latest versions. Sunset date: September 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-1312825e76 - 2027-10-08 | Meta (Graph & Marketing API) | Meta Graph API v23.0 expiration (October 8, 2027) | Meta Graph API v23.0 was released May 29, 2025. Listed expiration date: October 8, 2027. | source: https://developers.facebook.com/docs/graph-api/changelog/versions | id: meta-02ce250b81 - 2027-10-15 | LinkedIn Marketing API | LinkedIn Marketing API version 202610 (October 2026) sunset on October 15, 2027 | Developers using LinkedIn Marketing APIs version 202610 (October 2026) to migrate to the latest versions. Sunset date: October 15, 2027. Status listed: Active. | source: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations | id: linkedin-7433137407 - 2027-11 | Google Ads | Google Ads API v26 sunset (November 2027) | Google Ads API v26 was released on October 14, 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-40997678c4 - 2027-11 (tentative) | Google Ads | Google Ads API v26.1 sunset (November 2027) (planned, tentative) | Google Ads API v26.1 is planned for release in October 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-d270dfa1ce - 2027-11 (tentative) | Google Ads | Google Ads API v26.2 sunset (November 2027) (planned, tentative) | Google Ads API v26.2 is planned for release in November 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-b40e2b383b - 2027-11 (tentative) | Google Ads | Google Ads API v26.3 sunset (November 2027) (planned, tentative) | Google Ads API v26.3 is planned for release in December 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. Source footnote: "v26.3 and v30.3 are designated as optional releases due to overlap with the holiday season." | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-552ff17366 - 2028-02 (tentative) | Google Ads | Google Ads API v27 sunset (February 2028) (planned, tentative) | Google Ads API v27 is planned for release in January 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-82d41db342 - 2028-02 (tentative) | Google Ads | Google Ads API v27.1 sunset (February 2028) (planned, tentative) | Google Ads API v27.1 is planned for release in February 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-9d1c117df8 - 2028-02 (tentative) | Google Ads | Google Ads API v27.2 sunset (February 2028) (planned, tentative) | Google Ads API v27.2 is planned for release in February 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-2ce919baf4 - 2028-02 (tentative) | Google Ads | Google Ads API v27.3 sunset (February 2028) (planned, tentative) | Google Ads API v27.3 is planned for release in March 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-1380ddea55 - 2028-02 (tentative) | Google Ads | Google Ads API v27.4 sunset (February 2028) (planned, tentative) | Google Ads API v27.4 is planned for release in March 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-e925318577 - 2028-02 | Salesforce | Salesforce retirement: Open CTI (Spring '28 - February 2028) | Salesforce lists "Open CTI" on its Active Product & Feature Retirements page with timing: Spring '28 - February 2028. | source: https://help.salesforce.com/s/articleView?id=005317712&type=1&language=en_US | id: salesforce-9fe74cd1d2 - 2028-02-18 | Meta (Graph & Marketing API) | Meta Graph API v24.0 expiration (February 18, 2028) | Meta Graph API v24.0 was released October 8, 2025. Listed expiration date: February 18, 2028. | source: https://developers.facebook.com/docs/graph-api/changelog/versions | id: meta-961f2ca636 - 2028-05-01 | Salesforce | Salesforce retirement: Vlocity Public Sector Managed Package (May 1, 2028) | Salesforce lists "Vlocity Public Sector Managed Package" on its Active Product & Feature Retirements page with timing: May 1, 2028. | source: https://help.salesforce.com/s/articleView?id=005384463&type=1&language=en_US | id: salesforce-6486e2a52f - 2028-05 (tentative) | Google Ads | Google Ads API v28 sunset (May 2028) (planned, tentative) | Google Ads API v28 is planned for release in April 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-085d08b455 - 2028-05 (tentative) | Google Ads | Google Ads API v28.1 sunset (May 2028) (planned, tentative) | Google Ads API v28.1 is planned for release in April 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-5214ca98a6 - 2028-05 (tentative) | Google Ads | Google Ads API v28.2 sunset (May 2028) (planned, tentative) | Google Ads API v28.2 is planned for release in May 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-3b8107c5f6 - 2028-05 (tentative) | Google Ads | Google Ads API v28.3 sunset (May 2028) (planned, tentative) | Google Ads API v28.3 is planned for release in May 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-96edaa7ebb - 2028-05 (tentative) | Google Ads | Google Ads API v28.4 sunset (May 2028) (planned, tentative) | Google Ads API v28.4 is planned for release in June 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-44e1497585 - 2028-05 (tentative) | Google Ads | Google Ads API v28.5 sunset (May 2028) (planned, tentative) | Google Ads API v28.5 is planned for release in June 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-a5b79f777d - 2028-06 | Salesforce | Salesforce retirement: Salesforce Platform API Versions 31.0 through 40.0 (Summer '28 - June 2028) | Salesforce lists "Salesforce Platform API Versions 31.0 through 40.0" on its Active Product & Feature Retirements page with timing: Summer '28 - June 2028. | source: https://help.salesforce.com/s/articleView?id=005321531&type=1&language=en_US | id: salesforce-3e54362c25 - 2028-07-29 | Meta (Graph & Marketing API) | Meta Graph API v25.0 expiration (July 29, 2028) | Meta Graph API v25.0 was released February 18, 2026. Listed expiration date: July 29, 2028. | source: https://developers.facebook.com/docs/graph-api/changelog/versions | id: meta-81f12270bf - 2028-08 (tentative) | Google Ads | Google Ads API v29 sunset (August 2028) (planned, tentative) | Google Ads API v29 is planned for release in July 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-0375ff781b - 2028-08 (tentative) | Google Ads | Google Ads API v29.1 sunset (August 2028) (planned, tentative) | Google Ads API v29.1 is planned for release in July 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-29f80ee908 - 2028-08 (tentative) | Google Ads | Google Ads API v29.2 sunset (August 2028) (planned, tentative) | Google Ads API v29.2 is planned for release in August 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-b14c53ecf6 - 2028-08 (tentative) | Google Ads | Google Ads API v29.3 sunset (August 2028) (planned, tentative) | Google Ads API v29.3 is planned for release in August 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-3f5f743c45 - 2028-08 (tentative) | Google Ads | Google Ads API v29.4 sunset (August 2028) (planned, tentative) | Google Ads API v29.4 is planned for release in September 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-0cbaf65560 - 2028-08 (tentative) | Google Ads | Google Ads API v29.5 sunset (August 2028) (planned, tentative) | Google Ads API v29.5 is planned for release in September 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-2dd294d2d1 - 2028-11 (tentative) | Google Ads | Google Ads API v30 sunset (November 2028) (planned, tentative) | Google Ads API v30 is planned for release in October 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-0429d0dff8 - 2028-11 (tentative) | Google Ads | Google Ads API v30.1 sunset (November 2028) (planned, tentative) | Google Ads API v30.1 is planned for release in October 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-cfe67334ed - 2028-11 (tentative) | Google Ads | Google Ads API v30.2 sunset (November 2028) (planned, tentative) | Google Ads API v30.2 is planned for release in November 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-b71ee7ac61 - 2028-11 (tentative) | Google Ads | Google Ads API v30.3 sunset (November 2028) (planned, tentative) | Google Ads API v30.3 is planned for release in December 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. Source footnote: "v26.3 and v30.3 are designated as optional releases due to overlap with the holiday season." | source: https://developers.google.com/google-ads/api/docs/sunset-dates | id: google-ads-a76a3e7f0f # GTM tool pricing (latest snapshot) ## Apollo.io (Sales intelligence / data) — https://www.apollo.io/pricing — snapshot 2026-10-17 - Free: $0 per seat per year, granted monthly (billed annual) | 900 credits - Basic: $49 Per seat per month, (billed annual) | 30,000 credits - Professional: $79 Per seat per month, (billed annual) | 48,000 credits - Organization: $119 billed annually (billed annual) | 72,000 credits - Advanced Dialer: $119 Per team, per month (billed annual) ## Clay (Data enrichment / GTM workflows) — https://www.clay.com/pricing — snapshot 2026-10-17 - Launch: $167/mo Starts at $54/mo, expand anytime (billed annual) | Starts at 15,000 actions/mo - Growth: $446/mo Starts at $185/mo, expand anytime (billed annual) | Starts at 40,000 actions/mo ## ZoomInfo (Sales intelligence / data) — https://www.zoominfo.com/pricing — snapshot 2026-10-17 - No list prices published on the page (contact-sales pricing) or none extracted. ## HubSpot Sales Hub (CRM) — https://www.hubspot.com/pricing/sales — snapshot 2026-10-17 - Free: $0 /mo | Free for up to 2 users. No credit card required. - Starter: $7 /mo/seat | also shown $20 - Professional: $90 /mo/seat | also shown $100 - Enterprise: $150 /mo/seat ## HubSpot Marketing Hub (Marketing automation) — https://www.hubspot.com/pricing/marketing — snapshot 2026-10-17 - Free: $0 /mo | Free for up to 2 users. No credit card required. - Starter: $7 /mo/seat | also shown $20 - Professional: $800 /mo | also shown $890 | Includes 3 Core Seats - Enterprise: $3,600 /mo | Includes 5 Core Seats ## Instantly (Outbound email) — https://instantly.ai/pricing — snapshot 2026-10-17 - Bundle: Starter: $94 /monthly | 5000 emails monthly, 1000 uploaded contacts - Bundle: Scale: $194 /monthly | 100,000 emails monthly, 25,000 uploaded contacts - Bundle: Agency: $555 /monthly | 500,000 emails monthly, 100,000 uploaded contacts - Outreach: Growth: $47 /monthly | also shown $37.6 | 1000 Uploaded Contacts - Outreach: Hypergrowth: $97 /monthly | also shown $77.6 | 25 000 Uploaded Contacts - Outreach: Light Speed: $358 /monthly | also shown $286.3 | 500 000 Emails Monthly - Credits: Growth: $47 /monthly | also shown $37.6 | 1500-2000 Instantly Credits Monthly - Credits: Supersonic: $97 /monthly | also shown $87.3 | 5000-7500 Instantly Credits Monthly - Credits: Hyper: From $197 /monthly | also shown $177.3 | 10K-200K Instantly Credits Monthly ## Smartlead (Outbound email) — https://www.smartlead.ai/pricing — snapshot 2026-10-17 - Base: $39 /month | 2,000 contacts - Pro: $94 /month | 30,000 contacts - Unlimited Smart: $174 /month | 50,000 Verified Emails - Unlimited Prime: $379 /month | 170,000 Verified Emails ## lemlist (Outbound email / multichannel) — https://www.lemlist.com/pricing — snapshot 2026-10-17 - Email: $69 / month | also shown $55 | 50,000 emails - Multichannel: $109 / month | also shown $87 - Lead data enrichment: $20 / month | also shown $16 | Get emails, phones, and other key top 25+ providers. - Buying intent signals: $29 / month | also shown $21 | 100 signals ## Artisan (AI SDR) (AI SDR) — https://www.artisan.co/pricing — snapshot 2026-10-17 - No list prices published on the page (contact-sales pricing) or none extracted. ## AiSDR (AI SDR) — https://aisdr.com/pricing/ — snapshot 2026-10-17 - Pay as you go: $1.50 / person prospected - Warmed-up mailbox: $33 - Per-campaign managed service: $149/campaign - Fully managed service: $2,500/mo ## Salesforce Sales Cloud (CRM) — https://www.salesforce.com/sales/pricing/ — snapshot 2026-10-17 - Starter Suite: $25 USD/User/Month (billed monthly) - Pro Suite: $100 USD/User/Month (billed annual) - Core: $195 USD/User/Month (billed annual) - Advanced: $395 USD/User/Month (billed annual) - Max: $550 USD/User/Month (billed annual) - Agentforce for Sales: From $125 - Revenue Intelligence: From $220 ## Salesforce Agentforce (add-ons & Flex Credits) (Salesforce add-on / AI agents) — https://www.salesforce.com/agentforce/pricing/ — snapshot 2026-10-17 - Agentforce add-ons (Sales, Service, Field Service): $125 - Max Edition: from $550 (billed annual) | 2.75M Flex Credits per org per year - Agentforce Industries add-ons: $150 - Agentforce User License: $5 USD/User/Month # All change records (newest first) ## Google Ads - [google-ads-0429d0dff8] 2028-11 | Google Ads API v30 sunset (November 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v30 is planned for release in October 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-cfe67334ed] 2028-11 | Google Ads API v30.1 sunset (November 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v30.1 is planned for release in October 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-b71ee7ac61] 2028-11 | Google Ads API v30.2 sunset (November 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v30.2 is planned for release in November 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-a76a3e7f0f] 2028-11 | Google Ads API v30.3 sunset (November 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v30.3 is planned for release in December 2027; its listed sunset date is November 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. Source footnote: "v26.3 and v30.3 are designated as optional releases due to overlap with the holiday season." | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-0375ff781b] 2028-08 | Google Ads API v29 sunset (August 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v29 is planned for release in July 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-29f80ee908] 2028-08 | Google Ads API v29.1 sunset (August 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v29.1 is planned for release in July 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-b14c53ecf6] 2028-08 | Google Ads API v29.2 sunset (August 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v29.2 is planned for release in August 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-3f5f743c45] 2028-08 | Google Ads API v29.3 sunset (August 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v29.3 is planned for release in August 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-0cbaf65560] 2028-08 | Google Ads API v29.4 sunset (August 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v29.4 is planned for release in September 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-2dd294d2d1] 2028-08 | Google Ads API v29.5 sunset (August 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v29.5 is planned for release in September 2027; its listed sunset date is August 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-085d08b455] 2028-05 | Google Ads API v28 sunset (May 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v28 is planned for release in April 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-5214ca98a6] 2028-05 | Google Ads API v28.1 sunset (May 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v28.1 is planned for release in April 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-3b8107c5f6] 2028-05 | Google Ads API v28.2 sunset (May 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v28.2 is planned for release in May 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-96edaa7ebb] 2028-05 | Google Ads API v28.3 sunset (May 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v28.3 is planned for release in May 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-44e1497585] 2028-05 | Google Ads API v28.4 sunset (May 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v28.4 is planned for release in June 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-a5b79f777d] 2028-05 | Google Ads API v28.5 sunset (May 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v28.5 is planned for release in June 2027; its listed sunset date is May 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-82d41db342] 2028-02 | Google Ads API v27 sunset (February 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v27 is planned for release in January 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-9d1c117df8] 2028-02 | Google Ads API v27.1 sunset (February 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v27.1 is planned for release in February 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-2ce919baf4] 2028-02 | Google Ads API v27.2 sunset (February 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v27.2 is planned for release in February 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-1380ddea55] 2028-02 | Google Ads API v27.3 sunset (February 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v27.3 is planned for release in March 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-e925318577] 2028-02 | Google Ads API v27.4 sunset (February 2028) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v27.4 is planned for release in March 2027; its listed sunset date is February 2028. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-40997678c4] 2027-11 | Google Ads API v26 sunset (November 2027) | api_version_sunset | published 2026-10-14 | Google Ads API v26 was released on October 14, 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-d270dfa1ce] 2027-11 | Google Ads API v26.1 sunset (November 2027) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v26.1 is planned for release in October 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-b40e2b383b] 2027-11 | Google Ads API v26.2 sunset (November 2027) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v26.2 is planned for release in November 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-552ff17366] 2027-11 | Google Ads API v26.3 sunset (November 2027) (planned, tentative) | api_version_sunset | published n/a | Google Ads API v26.3 is planned for release in December 2026; its listed sunset date is November 2027. Requests to a sunset version fail after that date. Google lists dates for unreleased versions as tentative. Source footnote: "v26.3 and v30.3 are designated as optional releases due to overlap with the holiday season." | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-7ec370f560] 2027-08 | Google Ads API v25 sunset (August 2027) | api_version_sunset | published 2026-07-22 | Google Ads API v25 was released on July 22, 2026; its listed sunset date is August 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-68ff2d742b] 2027-08 | Google Ads API v25.1 sunset (August 2027) | api_version_sunset | published 2026-08-19 | Google Ads API v25.1 was released on August 19, 2026; its listed sunset date is August 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-c737dbdf5b] 2027-08 | Google Ads API v25.2 sunset (August 2027) | api_version_sunset | published 2026-09-23 | Google Ads API v25.2 was released on September 23, 2026; its listed sunset date is August 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-5ee48a926e] 2027-06-30 | Announcing Google Mobile Ads Next-Gen SDK as the preferred SDK for Android | api_version_sunset, deprecation | published 2026-07-06 | Google Mobile Ads (GMA) Next-Gen SDK is now the preferred SDK for Android development with Google AdMob and Google Ad Manager. GMA Next-Gen SDK is a significant rewrite of Google Mobile Ads SDK that improves speed, stability, and the developer experience. Google Mobile Ads SDK for Android is now legacy. | https://ads-developers.googleblog.com/2026/07/announcing-google-mobile-ads-next-gen.html - [google-ads-d5fe74e03d] 2027-06 | Google Ads API v24.2 sunset (June 2027) | api_version_sunset | published 2026-06-24 | Google Ads API v24.2 was released on June 24, 2026; its listed sunset date is June 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-de3be13f45] 2027-05 | Google Ads API v24 sunset (May 2027) | api_version_sunset | published 2026-04-22 | Google Ads API v24 was released on April 22, 2026; its listed sunset date is May 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-ae7699e698] 2027-05 | Google Ads API v24.1 sunset (May 2027) | api_version_sunset | published 2026-05-13 | Google Ads API v24.1 was released on May 13, 2026; its listed sunset date is May 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-4f862a77d8] 2027-02 | Google Ads API v23 sunset (February 2027) | api_version_sunset | published 2026-01-28 | Google Ads API v23 was released on January 28, 2026; its listed sunset date is February 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-62e47032a9] 2027-02 | Google Ads API v23.1 sunset (February 2027) | api_version_sunset | published 2026-02-25 | Google Ads API v23.1 was released on February 25, 2026; its listed sunset date is February 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-144ee74d52] 2027-02 | Google Ads API v23.2 sunset (February 2027) | api_version_sunset | published 2026-03-25 | Google Ads API v23.2 was released on March 25, 2026; its listed sunset date is February 2027. Requests to a sunset version fail after that date. | https://developers.google.com/google-ads/api/docs/sunset-dates - [google-ads-4bf0d3beae] 2027-01-28 | Deprecating Structured Data Files v9, v9.1, and v9.2 | api_version_sunset, deprecation, format_change | published 2026-06-29 | Today we’re announcing the deprecation of Structured Data Files v9 , v9.1 , and v9.2 . These three versions will all sunset on January 28, 2027 . Migrate to v10 or higher before the sunset date to avoid any interruption of service. | https://ads-developers.googleblog.com/2026/06/deprecating-structured-data-files-v9.html - [google-ads-10b66c10ae] - | Announcing v26 of the Google Ads API | breaking_change | published 2026-10-14 | Today we are announcing the release of v26 of the Google Ads API. To use the new capabilities, you must upgrade your client libraries and client code. We've published all updated client libraries and code examples. | https://ads-developers.googleblog.com/2026/10/announcing-v26-of-google-ads-api.html - [google-ads-f8f0799d68] - | Google Ads API Release and Sunset Schedules for 2026-2027 | api_version_sunset, deprecation, breaking_change | published 2026-10-12 | Last year, we shifted to a monthly release schedule for the Google Ads API to provide you faster API access to Ads features available in the Google Ads UI . | https://ads-developers.googleblog.com/2026/10/google-ads-api-release-and-sunset.html - [google-ads-d163f23c26] - | Launching Structured Data Files v11 | api_version_sunset, deprecation, format_change | published 2026-10-08 | Today we’re announcing the general availability of Structured Data Files v11 . All users can now use v11 when downloading and uploading SDFs in the Display & Video 360 interface. | https://ads-developers.googleblog.com/2026/10/launching-structured-data-files-v11.html - [google-ads-47d4171f25] 2026-10-07 | Google Ads API v22 sunset reminder | api_version_sunset | published 2026-09-02 | Google Ads API v22 will sunset on October 7, 2026. Starting on this date, all v22 API requests will begin to fail. Migrate to a newer version prior to October 7, 2026 to ensure your API access is unaffected. | https://ads-developers.googleblog.com/2026/09/google-ads-api-v22-sunset-reminder.html - [google-ads-3c0a50c9ba] 2026-10-01 | October 2026 changes to the Display & Video 360 API and Structured Data Files | deprecation, breaking_change, format_change | published 2026-08-27 | Today we’re announcing three unversioned changes to the Display & Video 360 API and Structured Data Files that will take effect in October 2026 and may impact your existing integrations. | https://ads-developers.googleblog.com/2026/08/october-2026-changes-to-display-video.html - [google-ads-48efebce75] - | Announcing v25.2 of the Google Ads API | breaking_change, tracking_signal, format_change | published 2026-09-23 | Today we are announcing the release of v25.2 of the Google Ads API. To use the new capabilities, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published. | https://ads-developers.googleblog.com/2026/09/announcing-v252-of-google-ads-api.html - [google-ads-99a7a87be0] - | A new onboarding experience for Google Ads API developers | api_version_sunset, breaking_change, policy | published 2026-09-10 | To improve the developer onboarding and usage experience, we built a new homepage for the Google Ads API in the Google Cloud Console . Basic Access applications are now automated for developers who have completed brand verification . This blog post covers several related changes that will start rolling out today. | https://ads-developers.googleblog.com/2026/09/new-onboarding-experience-for-google-ads-api.html - [google-ads-cd317c555d] 2026-09-01 | Migrate Campaign-level Broad Match and Automatically Created Assets to AI Max | deprecation | published 2026-08-12 | The legacy automigrations are divided into two separate phases: Phase 1 ( Campaign-level Broad Match and Automatically Created Assets ), which starts September 1, 2026. Phase 2 (Dynamic Search Ads), which has been rescheduled to February 2027. | https://ads-developers.googleblog.com/2026/08/migrate-campaign-level-broad-match-and.html - [google-ads-830209d391] - | Making Google Ads More Secure with Updates to Developer Policies | policy | published 2026-08-31 | We are updating our Google Ads Developer Policies formerly the “Google Ads API Policy”, to support developers in building robust, high-quality integrations as new AI capabilities continue to shape the advertising industry. | https://ads-developers.googleblog.com/2026/08/making-google-ads-more-secure-with.html - [google-ads-309ce7d00f] 2026-08-31 | Enabling Local Inventory Ads by Default for Shopping Campaigns starting on August 31, 2026 | deprecation, breaking_change | published 2026-07-20 | On August 31, 2026, we are aligning Shopping campaigns with Performance Max for Retail campaigns by enabling Local Inventory Ads (LIA) by default. Previously, developers and advertisers had to explicitly set the enable_local field to true within a campaign's ShoppingSetting in order to serve products in their LIA feed. | https://ads-developers.googleblog.com/2026/07/enabling-local-inventory-ads-by-default.html - [google-ads-0928482713] - | Google Ads API Developer Assistant v4.0.0 | tracking_signal | published 2026-08-25 | A major release of the Google Ads API Developer Assistant is now available. This release transitions the assistant from a standalone project setup to a unified plugin architecture designed to bring specialized Google Ads API capabilities directly into AI agent workflows. | https://ads-developers.googleblog.com/2026/08/google-ads-api-developer-assistant-v400.html - [google-ads-f958cd8134] - | Announcing v25.1 of the Google Ads API | breaking_change | published 2026-08-19 | Today we are announcing the release of v25.1 of the Google Ads API . To use the new capabilities, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published. | https://ads-developers.googleblog.com/2026/08/announcing-v251-of-google-ads-api.html - [google-ads-b09b117e1b] - | Google Ads language targeting changes starting September 2026 | deprecation | published 2026-08-13 | We're making changes to language targeting for Search, AI Max for Search, and Performance Max campaigns in Google Ads, simplifying campaign management while maintaining a high-quality ad experience. | https://ads-developers.googleblog.com/2026/08/google-ads-language-targeting-changes.html - [google-ads-9563e048e1] - | Query report data with the Campaign Manager 360 API | breaking_change, policy | published 2026-08-12 | You can now use the reportData.query endpoint in the Campaign Manager 360 API to synchronously query your campaign performance data and retrieve structured JSON data directly in the response. | https://ads-developers.googleblog.com/2026/08/query-report-data-with-campaign-manager.html - [google-ads-336aa4c8fb] - | Google Ads API pilot: Secure API Access to your Manager Accounts | breaking_change, policy | published 2026-08-03 | The Google Ads API is piloting a security feature designed for securing API access to Google Ads manager accounts. We are seeking developers who would like to participate in this pilot project and provide us with feedback. What are we offering? | https://ads-developers.googleblog.com/2026/08/google-ads-api-pilot-secure-api-access.html - [google-ads-b94d3000f9] - | Data Manager API updates: RemoveAllAudienceMembers method, ingestion field warnings, expanded address data | deprecation, breaking_change, tracking_signal | published 2026-07-30 | The latest release of the Data Manager API introduces features that simplify audience management, enhance ingestion workflows with field-level warnings, and enable more granular user-provided data for Google Analytics. | https://ads-developers.googleblog.com/2026/07/data-manager-api-updates.html - [google-ads-f3f5f7411c] - | Launching Structured Data Files v10.1 | deprecation, format_change | published 2026-07-29 | Today we’re announcing the general availability of Structured Data Files v10.1 . All users can now use v10.1 when downloading and uploading SDFs in the Display & Video 360 interface. | https://ads-developers.googleblog.com/2026/07/launching-structured-data-files-v101.html - [google-ads-45d58e900b] - | Support for AI Content Labeling using the Campaign Manager and Display & Video 360 APIs | format_change | published 2026-07-28 | As the use of AI becomes more prevalent, transparency is key. | https://ads-developers.googleblog.com/2026/07/support-for-ai-content-labeling-using.html - [google-ads-20c92c821c] - | Passkey authentication requirement for the Google Ads API | breaking_change, policy | published 2026-07-27 | As part of improving security for Google Ads accounts, the Google Ads API will start requiring passkeys for Google Ads API users . This is part of a broader change in Google Ads that requires passkeys to authorize sensitive actions in your Google Ads account. | https://ads-developers.googleblog.com/2026/07/passkey-authentication-requirement-for.html - [google-ads-acba802ce9] - | July 2026 update to the Display & Video 360 API | format_change | published 2026-07-23 | Today we’re launching the July 2026 update to the Display & Video 360 API. This update includes the following: Added a new syntheticContentAttestationStatus field to Creative and AdAsset resources. This field lets you specify whether a creative or ad asset contains content that was created or edited with AI. | https://ads-developers.googleblog.com/2026/07/july-2026-update-to-display-video-360.html - [google-ads-2124e9619f] - | Announcing v25 of the Google Ads API | breaking_change, format_change | published 2026-07-22 | Today, we’re announcing the v25 release of the Google Ads API . This major release brings support for new reporting features and goals. To use these new capabilities, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published. | https://ads-developers.googleblog.com/2026/07/announcing-v25-of-google-ads-api.html - [google-ads-122b735591] - | Accelerate Google Ads API Basic Access reviews with brand verification | policy | published 2026-07-07 | Today, we are launching a pilot process to expedite the Basic Access application review process. If you have a pending Basic Access application for your Google Ads API developer token, then you can complete brand verification for your Google Cloud project to expedite the reviews for your pending application. | https://ads-developers.googleblog.com/2026/07/accelerate-google-ads-api-basic-access.html - [google-ads-073a4d8367] - | July 2026 changes for Display & Video 360 API and Structured Data Files | deprecation, format_change | published 2026-06-26 | Today we’re announcing two unversioned changes to the Display & Video 360 API and Structured Data Files that will take effect on July 13, 2026 and may impact your existing integrations. | https://ads-developers.googleblog.com/2026/06/july-2026-changes-for-display-video-360.html ## Meta (Graph & Marketing API) - [meta-81f12270bf] 2028-07-29 | Meta Graph API v25.0 expiration (July 29, 2028) | api_version_sunset | published 2026-02-18 | Meta Graph API v25.0 was released February 18, 2026. Listed expiration date: July 29, 2028. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-961f2ca636] 2028-02-18 | Meta Graph API v24.0 expiration (February 18, 2028) | api_version_sunset | published 2025-10-08 | Meta Graph API v24.0 was released October 8, 2025. Listed expiration date: February 18, 2028. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-02ce250b81] 2027-10-08 | Meta Graph API v23.0 expiration (October 8, 2027) | api_version_sunset | published 2025-05-29 | Meta Graph API v23.0 was released May 29, 2025. Listed expiration date: October 8, 2027. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-3170627adb] 2027-05-20 | Meta Graph API v22.0 expiration (May 20, 2027) | api_version_sunset | published 2025-01-21 | Meta Graph API v22.0 was released January 21, 2025. Listed expiration date: May 20, 2027. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-55a6e88121] 2027-01-21 | Meta Graph API v21.0 expiration (January 21, 2027) | api_version_sunset | published 2024-10-02 | Meta Graph API v21.0 was released October 2, 2024. Listed expiration date: January 21, 2027. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-c05ad5f55e] 2026-10-06 | Meta Marketing API v24.0 expiration (October 6, 2026) | api_version_sunset | published 2025-10-08 | Meta Marketing API v24.0 was released October 8, 2025. Listed expiration date: October 6, 2026. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-fa892f5a41] 2026-09-24 | Meta Graph API v20.0 expiration (September 24, 2026) | api_version_sunset | published 2024-05-21 | Meta Graph API v20.0 was released May 21, 2024. Listed expiration date: September 24, 2026. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-33d73864dc] - | Meta Graph API v26.0 expiration (TBD) | api_version_sunset | published 2026-07-29 | Meta Graph API v26.0 was released July 29, 2026. Listed expiration date: TBD. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-a2c78845a4] 2026-06-09 | Meta Marketing API v23.0 expiration (June 9, 2026) | api_version_sunset | published 2025-05-29 | Meta Marketing API v23.0 was released May 29, 2025. Listed expiration date: June 9, 2026. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-60d84fe761] 2026-05-21 | Meta Graph API v19.0 expiration (May 21, 2026) | api_version_sunset | published 2024-01-23 | Meta Graph API v19.0 was released January 23, 2024. Listed expiration date: May 21, 2026. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-e591ad9d5f] 2026-02-19 | Meta Marketing API v22.0 expiration (February 19, 2026) | api_version_sunset | published 2025-01-21 | Meta Marketing API v22.0 was released January 21, 2025. Listed expiration date: February 19, 2026. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-fa5f7099f1] - | Meta Marketing API v25.0 expiration (TBD) | api_version_sunset | published 2026-02-18 | Meta Marketing API v25.0 was released February 18, 2026. Listed expiration date: TBD. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-1cde680f6d] 2026-01-26 | Meta Graph API v18.0 expiration (January 26, 2026) | api_version_sunset | published 2023-09-12 | Meta Graph API v18.0 was released September 12, 2023. Listed expiration date: January 26, 2026. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-ab8026d52d] 2025-09-12 | Meta Graph API v17.0 expiration (September 12, 2025) | api_version_sunset | published 2023-05-23 | Meta Graph API v17.0 was released May 23, 2023. Listed expiration date: September 12, 2025. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-a2b78f33ad] 2025-09-09 | Meta Marketing API v21.0 expiration (September 9, 2025) | api_version_sunset | published 2024-10-02 | Meta Marketing API v21.0 was released October 2, 2024. Listed expiration date: September 9, 2025. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-7f76e625fd] 2025-05-14 | Meta Graph API v16.0 expiration (May 14, 2025) | api_version_sunset | published 2023-02-02 | Meta Graph API v16.0 was released February 2, 2023. Listed expiration date: May 14, 2025. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-5efe0cb33c] 2025-05-06 | Meta Marketing API v20.0 expiration (May 6, 2025) | api_version_sunset | published 2024-05-21 | Meta Marketing API v20.0 was released May 21, 2024. Listed expiration date: May 6, 2025. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-f98659edc1] 2025-02-04 | Meta Marketing API v19.0 expiration (February 4, 2025) | api_version_sunset | published 2024-01-23 | Meta Marketing API v19.0 was released January 23, 2024. Listed expiration date: February 4, 2025. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-bae563a2aa] 2024-11-20 | Meta Graph API v15.0 expiration (November 20, 2024) | api_version_sunset | published 2022-09-15 | Meta Graph API v15.0 was released September 15, 2022. Listed expiration date: November 20, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-9dac7be646] 2024-09-17 | Meta Graph API v14.0 expiration (September 17, 2024) | api_version_sunset | published 2022-05-25 | Meta Graph API v14.0 was released May 25, 2022. Listed expiration date: September 17, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-485e022abb] 2024-08-13 | Meta Marketing API v18.0 expiration (August 13, 2024) | api_version_sunset | published 2023-09-12 | Meta Marketing API v18.0 was released September 12, 2023. Listed expiration date: August 13, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-e0aa28a53d] 2024-05-28 | Meta Graph API v13.0 expiration (May 28, 2024) | api_version_sunset | published 2022-02-08 | Meta Graph API v13.0 was released February 8, 2022. Listed expiration date: May 28, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-728969cc65] 2024-05-14 | Meta Marketing API v17.0 expiration (May 14, 2024) | api_version_sunset | published 2023-05-23 | Meta Marketing API v17.0 was released May 23, 2023. Listed expiration date: May 14, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-c616778760] 2024-02-08 | Meta Graph API v12.0 expiration (February 8, 2024) | api_version_sunset | published 2021-09-14 | Meta Graph API v12.0 was released September 14, 2021. Listed expiration date: February 8, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-c23cfed3f4] 2024-02-06 | Meta Marketing API v16.0 expiration (February 6, 2024) | api_version_sunset | published 2023-02-02 | Meta Marketing API v16.0 was released February 2, 2023. Listed expiration date: February 6, 2024. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-4c4fb469c8] 2023-09-20 | Meta Marketing API v15.0 expiration (September 20, 2023) | api_version_sunset | published 2022-09-15 | Meta Marketing API v15.0 was released September 15, 2022. Listed expiration date: September 20, 2023. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-9ca264c059] 2023-09-20 | Meta Marketing API v14.0 expiration (September 20, 2023) | api_version_sunset | published 2022-05-25 | Meta Marketing API v14.0 was released May 25, 2022. Listed expiration date: September 20, 2023. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-bc490c2715] 2023-09-14 | Meta Graph API v11.0 expiration (September 14, 2023) | api_version_sunset | published 2021-06-08 | Meta Graph API v11.0 was released June 8, 2021. Listed expiration date: September 14, 2023. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-75502699a5] 2023-06-08 | Meta Graph API v10.0 expiration (June 8, 2023) | api_version_sunset | published 2021-02-23 | Meta Graph API v10.0 was released February 23, 2021. Listed expiration date: June 8, 2023. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-ab0e74c7d4] 2023-02-23 | Meta Graph API v9.0 expiration (February 23, 2023) | api_version_sunset | published 2020-11-10 | Meta Graph API v9.0 was released November 10, 2020. Listed expiration date: February 23, 2023. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-d35e736352] 2023-01-25 | Meta Marketing API v13.0 expiration (January 25, 2023) | api_version_sunset | published 2022-02-08 | Meta Marketing API v13.0 was released February 8, 2022. Listed expiration date: January 25, 2023. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-8e79fe904d] 2022-11-01 | Meta Graph API v8.0 expiration (November 1, 2022) | api_version_sunset | published 2020-08-04 | Meta Graph API v8.0 was released August 4, 2020. Listed expiration date: November 1, 2022. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-34b32e419a] 2022-08-09 | Meta Marketing API v12.0 expiration (August 9, 2022) | api_version_sunset | published 2021-09-14 | Meta Marketing API v12.0 was released September 14, 2021. Listed expiration date: August 9, 2022. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-abd0e3f546] 2022-08-04 | Meta Graph API v7.0 expiration (August 4, 2022) | api_version_sunset | published 2020-05-05 | Meta Graph API v7.0 was released May 5, 2020. Listed expiration date: August 4, 2022. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-5904718e91] 2022-05-05 | Meta Graph API v6.0 expiration (May 5, 2022) | api_version_sunset | published 2020-02-03 | Meta Graph API v6.0 was released February 3, 2020. Listed expiration date: May 5, 2022. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-5d101a7ff0] 2022-02-23 | Meta Marketing API v11.0 expiration (February 23, 2022) | api_version_sunset | published 2021-06-08 | Meta Marketing API v11.0 was released June 8, 2021. Listed expiration date: February 23, 2022. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-fbb928a713] 2022-02-03 | Meta Graph API v5.0 expiration (February 3, 2022) | api_version_sunset | published 2019-10-29 | Meta Graph API v5.0 was released October 29, 2019. Listed expiration date: February 3, 2022. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-2339b4327a] 2021-11-02 | Meta Graph API v4.0 expiration (November 2, 2021) | api_version_sunset | published 2019-07-29 | Meta Graph API v4.0 was released July 29, 2019. Listed expiration date: November 2, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-ff39750805] 2021-10-04 | Meta Marketing API v10.0 expiration (October 4, 2021) | api_version_sunset | published 2021-02-23 | Meta Marketing API v10.0 was released February 23, 2021. Listed expiration date: October 4, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-74eabc9642] 2021-08-25 | Meta Marketing API v9.0 expiration (August 25, 2021) | api_version_sunset | published 2020-11-10 | Meta Marketing API v9.0 was released November 10, 2020. Listed expiration date: August 25, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-6685ca93e9] 2021-08-03 | Meta Graph API v3.3 expiration (August 3, 2021) | api_version_sunset | published 2019-04-30 | Meta Graph API v3.3 was released April 30, 2019. Listed expiration date: August 3, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-5927c79ded] 2021-05-04 | Meta Graph API v3.2 expiration (May 4, 2021) | api_version_sunset | published 2018-10-23 | Meta Graph API v3.2 was released October 23, 2018. Listed expiration date: May 4, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-92bb96b0dc] 2021-05-04 | Meta Marketing API v8.0 expiration (May 4, 2021) | api_version_sunset | published 2020-08-04 | Meta Marketing API v8.0 was released August 4, 2020. Listed expiration date: May 4, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-946ae783e7] 2021-03-03 | Meta Marketing API v7.0 expiration (March 3, 2021) | api_version_sunset | published 2020-05-05 | Meta Marketing API v7.0 was released May 5, 2020. Listed expiration date: March 3, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-7135b81974] 2021-02-08 | Meta Marketing API v6.0 expiration (Extended to February 8, 2021) | api_version_sunset | published 2020-02-03 | Meta Marketing API v6.0 was released February 3, 2020. Listed expiration date: Extended to February 8, 2021. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-4cda548ed0] 2020-10-27 | Meta Graph API v3.1 expiration (October 27, 2020) | api_version_sunset | published 2018-07-26 | Meta Graph API v3.1 was released July 26, 2018. Listed expiration date: October 27, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-009ff1b91d] 2020-09-28 | Meta Marketing API v5.0 expiration (September 28, 2020) | api_version_sunset | published 2019-10-29 | Meta Marketing API v5.0 was released October 29, 2019. Listed expiration date: September 28, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-a483a474c2] 2020-07-28 | Meta Graph API v3.0 expiration (July 28, 2020) | api_version_sunset | published 2018-05-01 | Meta Graph API v3.0 was released May 1, 2018. Listed expiration date: July 28, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-bb85ac4377] 2020-05-05 | Meta Graph API v2.12 expiration (May 5, 2020) | api_version_sunset | published 2018-01-30 | Meta Graph API v2.12 was released January 30, 2018. Listed expiration date: May 5, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-d9ef4d6f6b] 2020-03-31 | Meta Marketing API v4.0 expiration (March 31, 2020) | api_version_sunset | published 2019-07-29 | Meta Marketing API v4.0 was released July 29, 2019. Listed expiration date: March 31, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-b5c1c34941] 2020-01-28 | Meta Graph API v2.11 expiration (January 28, 2020) | api_version_sunset | published 2017-11-07 | Meta Graph API v2.11 was released November 7, 2017. Listed expiration date: January 28, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-0749fbfa7c] 2020-01-13 | Meta Marketing API v3.3 expiration (January 13, 2020) | api_version_sunset | published 2019-04-30 | Meta Marketing API v3.3 was released April 30, 2019. Listed expiration date: January 13, 2020. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-f5e9e78c65] 2019-11-07 | Meta Graph API v2.10 expiration (November 7, 2019) | api_version_sunset | published 2017-07-18 | Meta Graph API v2.10 was released July 18, 2017. Listed expiration date: November 7, 2019. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-17408d6c40] 2019-08-13 | Meta Marketing API v3.2 expiration (August 13, 2019) | api_version_sunset | published 2018-10-23 | Meta Marketing API v3.2 was released October 23, 2018. Listed expiration date: August 13, 2019. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-b55f824885] 2019-07-22 | Meta Graph API v2.9 expiration (July 22, 2019) | api_version_sunset | published 2017-04-18 | Meta Graph API v2.9 was released April 18, 2017. Listed expiration date: July 22, 2019. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-0c39c34819] 2019-05-14 | Meta Marketing API v3.1 expiration (May 14, 2019) | api_version_sunset | published 2018-07-26 | Meta Marketing API v3.1 was released July 26, 2018. Listed expiration date: May 14, 2019. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-41dfdcdbf0] 2019-04-18 | Meta Graph API v2.8 expiration (April 18, 2019) | api_version_sunset | published 2016-10-05 | Meta Graph API v2.8 was released October 5, 2016. Listed expiration date: April 18, 2019. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-abc745d7c7] 2019-02-01 | Meta Marketing API v3.0 expiration (February 1, 2019) | api_version_sunset | published 2018-05-01 | Meta Marketing API v3.0 was released May 1, 2018. Listed expiration date: February 1, 2019. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-3ff86e914a] 2018-10-05 | Meta Graph API v2.7 expiration (October 5, 2018) | api_version_sunset | published 2016-07-13 | Meta Graph API v2.7 was released July 13, 2016. Listed expiration date: October 5, 2018. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-0720ebdd95] 2018-08-07 | Meta Marketing API v2.12 expiration (August 7, 2018) | api_version_sunset | published 2018-01-30 | Meta Marketing API v2.12 was released January 30, 2018. Listed expiration date: August 7, 2018. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-96c39a1365] 2018-08-07 | Meta Marketing API v2.11 expiration (August 7, 2018) | api_version_sunset | published 2017-11-07 | Meta Marketing API v2.11 was released November 7, 2017. Listed expiration date: August 7, 2018. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-da905a4642] 2018-07-13 | Meta Graph API v2.6 expiration (July 13, 2018) | api_version_sunset | published 2016-04-12 | Meta Graph API v2.6 was released April 12, 2016. Listed expiration date: July 13, 2018. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-8a56de6f27] 2018-05-08 | Meta Marketing API v2.10 expiration (May 8, 2018) | api_version_sunset | published 2017-07-18 | Meta Marketing API v2.10 was released July 18, 2017. Listed expiration date: May 8, 2018. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-9aac5652df] 2018-04-12 | Meta Graph API v2.5 expiration (April 12, 2018) | api_version_sunset | published 2015-10-07 | Meta Graph API v2.5 was released October 7, 2015. Listed expiration date: April 12, 2018. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-616b3aef16] 2017-11-06 | Meta Marketing API v2.9 expiration (November 6, 2017) | api_version_sunset | published 2017-04-18 | Meta Marketing API v2.9 was released April 18, 2017. Listed expiration date: November 6, 2017. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-39ae10f8ee] 2017-10-09 | Meta Graph API v2.4 expiration (October 9, 2017) | api_version_sunset | published 2015-07-08 | Meta Graph API v2.4 was released July 8, 2015. Listed expiration date: October 9, 2017. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-aaf9f2564b] 2017-07-26 | Meta Marketing API v2.8 expiration (July 26, 2017) | api_version_sunset | published 2016-10-05 | Meta Marketing API v2.8 was released October 5, 2016. Listed expiration date: July 26, 2017. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-7b6f38eecf] 2017-07-10 | Meta Graph API v2.3 expiration (July 10, 2017) | api_version_sunset | published 2015-03-25 | Meta Graph API v2.3 was released March 25, 2015. Listed expiration date: July 10, 2017. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-6ba53c74f7] 2017-04-25 | Meta Marketing API v2.7 expiration (April 25, 2017) | api_version_sunset | published 2016-07-13 | Meta Marketing API v2.7 was released July 13, 2016. Listed expiration date: April 25, 2017. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-19d8dd0375] 2017-03-27 | Meta Graph API v2.2 expiration (March 27, 2017) | api_version_sunset | published 2014-10-30 | Meta Graph API v2.2 was released October 30, 2014. Listed expiration date: March 27, 2017. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-9abd31c87f] 2016-10-31 | Meta Graph API v2.1 expiration (October 31, 2016) | api_version_sunset | published 2014-08-07 | Meta Graph API v2.1 was released August 7, 2014. Listed expiration date: October 31, 2016. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-b7184b8ba0] 2016-10-05 | Meta Marketing API v2.6 expiration (October 5, 2016) | api_version_sunset | published 2016-04-12 | Meta Marketing API v2.6 was released April 12, 2016. Listed expiration date: October 5, 2016. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-0813199809] 2016-08-08 | Meta Graph API v2.0 expiration (August 8, 2016) | api_version_sunset | published 2014-04-30 | Meta Graph API v2.0 was released April 30, 2014. Listed expiration date: August 8, 2016. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-f5ae42ab94] 2016-07-13 | Meta Marketing API v2.5 expiration (July 13, 2016) | api_version_sunset | published 2015-10-07 | Meta Marketing API v2.5 was released October 7, 2015. Listed expiration date: July 13, 2016. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-316b432889] 2016-04-11 | Meta Marketing API v2.4 expiration (April 11, 2016) | api_version_sunset | published 2015-07-08 | Meta Marketing API v2.4 was released July 8, 2015. Listed expiration date: April 11, 2016. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-abf5956c37] 2015-10-08 | Meta Marketing API v2.3 expiration (October 8, 2015) | api_version_sunset | published 2015-03-25 | Meta Marketing API v2.3 was released March 25, 2015. Listed expiration date: October 8, 2015. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-5c48d5da0d] 2015-07-08 | Meta Marketing API v2.2 expiration (July 8, 2015) | api_version_sunset | published 2014-10-30 | Meta Marketing API v2.2 was released October 30, 2014. Listed expiration date: July 8, 2015. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-e652dedc07] 2015-04-30 | Meta Graph API v1.0 expiration (April 30, 2015) | api_version_sunset | published 2010-04-21 | Meta Graph API v1.0 was released April 21, 2010. Listed expiration date: April 30, 2015. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-5f66f589af] 2015-03-11 | Meta Marketing API v2.1 expiration (March 11, 2015) | api_version_sunset | published 2014-10-01 | Meta Marketing API v2.1 was released October 1, 2014. Listed expiration date: March 11, 2015. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-d96e7f713b] 2015-03-11 | Meta Marketing API v2.0 expiration (March 11, 2015) | api_version_sunset | published 2014-10-01 | Meta Marketing API v2.0 was released October 1, 2014. Listed expiration date: March 11, 2015. | https://developers.facebook.com/docs/graph-api/changelog/versions - [meta-02462e6907] 2015-03-11 | Meta Marketing API v1.0 expiration (March 11, 2015) | api_version_sunset | published 2014-10-01 | Meta Marketing API v1.0 was released October 1, 2014. Listed expiration date: March 11, 2015. | https://developers.facebook.com/docs/graph-api/changelog/versions ## LinkedIn Marketing API - [linkedin-7433137407] 2027-10-15 | LinkedIn Marketing API version 202610 (October 2026) sunset on October 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202610 (October 2026) to migrate to the latest versions. Sunset date: October 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-1312825e76] 2027-09-15 | LinkedIn Marketing API version 202609 (September 2026) sunset on September 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202609 (September 2026) to migrate to the latest versions. Sunset date: September 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-84f8fe25cc] 2027-08-17 | LinkedIn Marketing API version 202608 (August 2026) sunset on August 17, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202608 (August 2026) to migrate to the latest versions. Sunset date: August 17, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-9e2f89e72a] 2027-07-15 | LinkedIn Marketing API version 202607 (July 2026) sunset on July 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202607 (July 2026) to migrate to the latest versions. Sunset date: July 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-58ce926b2b] 2027-06-15 | LinkedIn Marketing API version 202606 (June 2026) sunset on June 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202606 (June 2026) to migrate to the latest versions. Sunset date: June 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-a019bbf466] 2027-05-15 | LinkedIn Marketing API version 202605 (May 2026) sunset on May 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202605 (May 2026) to migrate to the latest versions. Sunset date: May 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-752ccbae9e] 2027-04-15 | LinkedIn Marketing API version 202604 (April 2026) sunset on April 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202604 (April 2026) to migrate to the latest versions. Sunset date: April 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-71a4c6da2b] 2027-03-16 | LinkedIn Marketing API version 202603 (March 2026) sunset on March 16, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202603 (March 2026) to migrate to the latest versions. Sunset date: March 16, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-046d762ee9] 2027-02-15 | LinkedIn Marketing API version 202602 (February 2026) sunset on February 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202602 (February 2026) to migrate to the latest versions. Sunset date: February 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-82a2ae909a] 2027-01-15 | LinkedIn Marketing API version 202601 (January 2026) sunset on January 15, 2027 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202601 (January 2026) to migrate to the latest versions. Sunset date: January 15, 2027. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-90cdc0c816] 2026-12-15 | Campaign Management API: New required surface field for publisher lists (action required) (October 2026 - Version 202610 (Latest)) | breaking_change, format_change | published 2026-10 | 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). | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b117c8c38c] 2026-11-16 | LinkedIn Marketing API version 202511 (November 2025) sunset on November 16, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202511 (November 2025) to migrate to the latest versions. Sunset date: November 16, 2026. Status listed: Active. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-63de8abc84] 2026-10-15 | LinkedIn Marketing API version 202510 (October 2025) sunset on October 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202510 (October 2025) to migrate to the latest versions. Sunset date: October 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-99537908fa] - | Creatives API: New metadata field (October 2026 - Version 202610 (Latest)) | breaking_change, format_change | published 2026-10 | 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 . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-825ff2ee8d] - | Company Intelligence API: New jobFunction filter (October 2026 - Version 202610 (Latest)) | announcement | published 2026-10 | New jobFunction filter : Starting with the 202610 version, the accountIntelligence endpoint finder now supports filtering results by the optional jobFunction field under filterCriteria. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-76006504aa] - | Creatives API: New enriched content fields (October 2026 - Version 202610 (Latest)) | format_change | published 2026-10 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d86d98c330] - | Ads Reporting API: New memberFollows and memberProfileClicks metrics (October 2026 - Version 202610 (Latest)) | announcement | published 2026-10 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-389e8a3645] - | Boost API: New Member and Company Page post boost endpoints (October 2026 - Version 202610 (Latest)) | announcement | published 2026-10 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-8bec8479f5] 2026-09-15 | LinkedIn Marketing API version 202509 (September 2025) sunset on September 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202509 (September 2025) to migrate to the latest versions. Sunset date: September 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-51f018bdd0] - | Company Intelligence API: New campaignGroup , objectiveType , and seniority filters (September 2026 - Version 202609) | announcement | published 2026-09 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-bcec09b659] - | Ads Reporting API: New MEMBER_DESIGNATED_MARKET_AREA pivot (September 2026 - Version 202609) | breaking_change | published 2026-09 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ef69363144] - | Conversions API: New hashedFirstName and hashedLastName fields (September 2026 - Version 202609) | tracking_signal | published 2026-09 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-a2c911fc6e] - | Conversions API: New 180-day attribution window option (September 2026 - Version 202609) | tracking_signal | published 2026-09 | 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 ,… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e9d4453f95] 2026-08-17 | LinkedIn Marketing API version 202508 (August 2025) sunset on August 17, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202508 (August 2025) to migrate to the latest versions. Sunset date: August 17, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-bb696efa3b] - | Matched Audiences API: Generally available to all qualified developers (August 2026 - Version 202608) | announcement | published 2026-08 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-0cabdad5c3] - | DMP Segments API: Cap on number of DMP Segments in ad account (August 2026 - Version 202608) | announcement | published 2026-08 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e69ce52796] - | Dynamic UTM API: Ad account-level tracking parameter support (August 2026 - Version 202608) | tracking_signal | published 2026-08 | 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 . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-9dd0a8148d] - | Conversions API: New conversion types for Marketing & Sales Qualified Leads (August 2026 - Version 202608) | tracking_signal | published 2026-08 | 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 . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-607e3bed0b] - | Conversions API: Additional use cases (August 2026 - Version 202608) | tracking_signal | published 2026-08 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-8458e67cb3] - | Ad Accounts API: New productType and originatingCustomer fields (August 2026 - Version 202608) | announcement | published 2026-08 | 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). | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-62e85fdf70] - | Campaign Groups API: New billing, beneficiary, and buying type fields (August 2026 - Version 202608) | announcement | published 2026-08 | 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 ). | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-db76a48961] 2026-07-15 | LinkedIn Marketing API version 202507 (July 2025) sunset on July 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202507 (July 2025) to migrate to the latest versions. Sunset date: July 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-5c116fe13f] - | Predictive Audiences API: id field available in the response (July 2026 - Version 202607) | announcement | published 2026-07 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-dc2e95eb63] - | Conversions API: New user identifier available for matching (July 2026 - Version 202607) | tracking_signal, format_change | published 2026-07 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-7c559f7281] - | Create and Manage Campaigns (July 2026 - Version 202607) | announcement | published 2026-07 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e340533334] 2026-06-15 | LinkedIn Marketing API version 202506 (June 2025) sunset on June 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202506 (June 2025) to migrate to the latest versions. Sunset date: June 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-2575228bb7] - | Company Intelligence API: 365-Day Lookback and Company Attribute Decoration (June 2026 - Version 202606) | announcement | published 2026-06 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d7368f03c8] - | Dynamic UTM API: Added dynamic tracking parameter support for CREATIVE_NAME (June 2026 - Version 202606) | tracking_signal, format_change | published 2026-06 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-cfe2ee61eb] - | Conversation Ads API: Not Interested Call-to-Action (CTA) (June 2026 - Version 202606) | announcement | published 2026-06 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-f8bba61dbf] - | Message Ads API (June 2026 - Version 202606) | announcement | published 2026-06 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-c217c11705] - | Change to Developer Support path (June 2026 - Version 202606) | api_version_sunset | published 2026-06 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-045e583c33] 2026-05-15 | LinkedIn Marketing API version 202505 (May 2025) sunset on May 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202505 (May 2025) to migrate to the latest versions. Sunset date: May 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-83d8835a4b] - | Events Management API (May 2026 - Version 202605) | breaking_change | published 2026-05 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-6b66a3d301] - | Event Ads API (May 2026 - Version 202605) | breaking_change, format_change | published 2026-05 | 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,… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b4c24132a8] - | Conversions API (May 2026 - Version 202605) | breaking_change, tracking_signal, format_change | published 2026-05 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-46a9c88797] - | Predictive Audiences API (May 2026 - Version 202605) | announcement | published 2026-05 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-dba391e881] - | Ad Analytics API (May 2026 - Version 202605) | announcement | published 2026-05 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-42db0e94f3] - | Company Intelligence API (May 2026 - Version 202605) | format_change | published 2026-05 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-a09119cc2b] - | Member Post Statistics API and Member Video Statistics API (May 2026 - Version 202605) | format_change | published 2026-05 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-465956c30a] - | Member Post Statistics API (May 2026 - Version 202605) | announcement | published 2026-05 | New creator analytics metrics Starting with the 202604 version, 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-82ceb63da8] 2026-04-15 | LinkedIn Marketing API version 202504 (April 2025) sunset on April 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202504 (April 2025) to migrate to the latest versions. Sunset date: April 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-b0feefac78] - | Member Post Statistics (April 2026 - Version 202604) | announcement | published 2026-04 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-478f3f8f53] - | Company Intelligence API (April 2026 - Version 202604) | announcement | published 2026-04 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-7e220336b1] 2026-03-16 | LinkedIn Marketing API version 202503 (March 2025) sunset on March 16, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202503 (March 2025) to migrate to the latest versions. Sunset date: March 16, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-76575062c5] 2026-03-16 | Lead Sync API (March 2026 - Version 202603) | breaking_change | published 2026-03 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-25a9ca4e05] - | Company Intelligence API (March 2026 - Version 202603) | tracking_signal | published 2026-03 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-3116e0426c] - | Ads Targeting Facets API (March 2026 - Version 202603) | announcement | published 2026-03 | 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). | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2b29302934] - | Brand Lift Testing API (March 2026 - Version 202603) | announcement | published 2026-03 | Maximum of 50 Campaign Groups per Test Brand Lift Tests are limited to 50 Campaign Groups maximum upon creation. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2d6d6e8adc] 2026-02-16 | LinkedIn Marketing API version 202502 (February 2025) sunset on February 16, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202502 (February 2025) to migrate to the latest versions. Sunset date: February 16, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-be13c5736e] - | Videos API (February 2026 - Version 202602) | tracking_signal, format_change | published 2026-02 | 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. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-98c4a90deb] - | Ad Campaigns API & Ad Budget Pricing API (February 2026 - Version 202602) | breaking_change, tracking_signal | published 2026-02 | 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… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-fe50cde6ba] 2026-01-15 | LinkedIn Marketing API version 202501 (January 2025) sunset on January 15, 2026 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202501 (January 2025) to migrate to the latest versions. Sunset date: January 15, 2026. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-50df8b566b] - | Ad Analytics API (January 2026 - Version 202601) | format_change | published 2026-01 | 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 /AdAnalytics endpoint: EventWatchTime metrics and VideoWatchTime metrics. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e8cf95ec92] 2025-12-02 | Member Authentication (November 2025 - Version 202511) | announcement | published 2025-11 | Google and Apple Sign-In for Developer Applications Starting December 2, 2025, LinkedIn will support Sign in with Google and Sign in with Apple as new options for member authentication in developer applications, alongside the existing username/password method for OAuth 2.0 authorization requests. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-9ce8590c6f] 2025-11-17 | LinkedIn Marketing API version 202411 (November 2024) sunset on November 17, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202411 (November 2024) to migrate to the latest versions. Sunset date: November 17, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-ee83a97d85] - | Predictive Audiences API (November 2025 - Version 202511) | announcement | published 2025-11 | Create High-intent, AI-powered Custom Audiences The Predictive Audiences API allows the customers to combine their first-party or third-party data with LinkedIn's predictive AI modeling to build audience segments tailored to specific business needs. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-76ed97bb07] - | Ad Lift Tests API (November 2025 - Version 202511) | announcement | published 2025-11 | Ad Lift Test Measurement by Campaign Groups The Ad Lift Tests API supports specifying multiple campaign groups in the liftEntity field when creating a new ad lift test using POST /adLiftTests. This enables measurement of the lift for specified campaign groups. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-9b885e9187] - | Lead Sync API (November 2025 - Version 202511) | tracking_signal | published 2025-11 | Dynamic URL Tracking Parameters on Lead Gen Forms Hidden fields for Lead Gen Forms support dynamic URL tracking parameters, enabling automatic tracking of campaigns, creatives, and other sources to associate leads with a particular lead gen form. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-492357757c] 2025-10-16 | Ad Analytics API (October 2025 - Version 202510) | breaking_change | published 2025-10 | Dwell Time Metric Update We recently improved the accuracy of the averageDwellTime metric in the adAnalytics API, which measures the duration that more than 50% of an ad’s pixels remain visible in the viewport. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-a68752c542] 2025-10-15 | LinkedIn Marketing API version 202410 (October 2024) sunset on October 15, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202410 (October 2024) to migrate to the latest versions. Sunset date: October 15, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-2d1ec74c76] 2025-10-10 | Campaigns API (September 2025 - Version 202509) | breaking_change, policy | published 2025-09 | Political Advertising Declaration for EU-Targeted Campaigns . Starting October 10, 2025, advertisers running campaigns targeting the EU region must self-declare whether their ads qualify as political advertising under the EU's Transparency and Targeting of Political Advertising (TTPA) regulation. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-6b6cb0ba03] 2025-10-10 | Campaigns API (August 2025 - Version 202508) | breaking_change, policy | published 2025-08 | Political Advertising Declaration for EU-Targeted Campaigns . Starting October 10, 2025, advertisers running campaigns targeting the EU region must self-declare if their ads qualify as political advertising under the EU's Transparency and Targeting of Political Advertising (TTPA) regulation. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-16f3f4e6e4] - | Company Intelligence API (October 2025 - Version 202510) | tracking_signal | published 2025-10 | Prove Business Impact with Company-level Insights Newly launched Company Intelligence API enables partners to surface company-level engagement across paid and organic LinkedIn touchpoints. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-f7d8ccae16] - | Ad Lift Tests API Updates: Ad Lift Test Schema (October 2025 - Version 202510) | policy, format_change | published 2025-10 | Ad Lift Test Schema : Starting with the 202510 version, the adLiftTests API includes a new optional field, reviewInfo , for Ad lift tests. This field indicates if the test content is under review, accepted, or rejected, and, if rejected, specifies the reasons. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-5ef5dc8254] - | OAuth Token Usage (October 2025 - Version 202510) | announcement | published 2025-10 | Monitor activity in the LinkedIn Developer Portal Starting September, the LinkedIn Developer Portal's Analytics dashboard includes a feature that lets developers monitor refresh token requests made by their applications. This update adds the ability to view OAuth token usage statistics for your application. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d5dba12ecb] - | LinkedIn Ads Agreement (October 2025 - Version 202510) | announcement | published 2025-10 | Updates to Improve Ad Performance LinkedIn is expanding its use of Microsoft data and customer tag data, which provide professional and B2B signals. This will help advertisers enhance their targeting, optimize campaigns with precision, and drive performance across the funnel. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b4f57d80a5] 2025-09-16 | Matched Audiences API (September 2025 - Version 202509) | api_version_sunset | published 2025-09 | Updated Endpoint for DMP Segment List Uploads . The DMP Segment List Uploads API endpoint for audience creation from static CSV files with POST /media/upload will sunset on September 16, 2025 . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d7426931a8] 2025-09-15 | LinkedIn Marketing API version 202409 (September 2024) sunset on September 15, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202409 (September 2024) to migrate to the latest versions. Sunset date: September 15, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-287f093778] - | Ad Account Trust Preferences API (September 2025 - Version 202509) | deprecation | published 2025-09 | Manage Publisher Restrictions at the Ad Account level . Starting with the 202509 version, we have introduced a new endpoint /adAccountTrustPreferences in the Advertising API that allows you to create and manage ad publisher restrictions at the ad account level. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-960df20404] 2025-08-18 | LinkedIn Marketing API version 202408 (August 2024) sunset on August 18, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202408 (August 2024) to migrate to the latest versions. Sunset date: August 18, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-fce49a568f] - | Conversions API Payload Builder (August 2025 - Version 202508) | tracking_signal | published 2025-08 | Enhanced Validation & Direct API Call Support . The Conversions API Payload Builder now supports capabilities to enable seamless and efficient integration process for Conversions API. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b71f610403] - | Developer AI Chatbot (August 2025 - Version 202508) | announcement | published 2025-08 | Now on the LinkedIn Developer Website Our AI-powered chatbot support has expanded from the Developer platform to the LinkedIn Developer website , making it easier for developers to discover and learn more about LinkedIn API products and access relevant technical information to get started. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-adb76ad92b] - | Creatives API (August 2025 - Version 202508) | format_change | published 2025-08 | Support for Innovid VAST Tags in Video Ads for CTV Starting with the 202507 version, partners can utilize VAST tags to streamline the setup and asset management of Connected TV (CTV) ad campaigns. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-70a4c8187c] 2025-07-22 | LinkedIn Marketing API version 202407 (July 2024) sunset on July 22, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202407 (July 2024) to migrate to the latest versions. Sunset date: July 22, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-6e71c05007] - | Creatives API (July 2025 - Version 202507) | format_change | published 2025-07 | Support for Innovid VAST Tags in Video Ads for CTV Starting with the 202507 version, partners can utilize VAST tags to streamline the setup and asset management of Connected TV (CTV) ad campaigns. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-02af8b0406] - | Community Management API Enhancements (July 2025 - Version 202507) | tracking_signal, format_change | published 2025-07 | Empower Customers to Measure and Grow Influence Partners can provide detailed analytics on executive, employee, and brand engagement with LinkedIn audiences. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-78b0e79798] 2025-06-16 | LinkedIn Marketing API version 202406 (June 2024) sunset on June 16, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202406 (June 2024) to migrate to the latest versions. Sunset date: June 16, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-87cc2096ec] - | Member Follower Statistics API (June 2025 - Version 202506) | tracking_signal | published 2025-06 | Power your platform by integrating LinkedIn’s member follower statistics API to report insights on gained member followers for authenticated members and motivate members to create high-quality content on LinkedIn. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-39a70ed697] - | Member Post Statistics API (June 2025 - Version 202506) | tracking_signal | published 2025-06 | Power your platform by integrating LinkedIn’s member post statistics API to report insights on member single post performance, as well as aggregated member posts, and motivate members to create high-quality content on LinkedIn. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-0ab75fd0de] - | Member Video Statistics API (June 2025 - Version 202506) | tracking_signal, format_change | published 2025-06 | Power your platform by integrating LinkedIn’s member video statistics API to report insights on video performance of the member post and motivate members to create high-quality video content on LinkedIn. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-a6f62baa2d] - | Sunset of Legacy Ad Lead Gen API on July 31, 2025: Legacy endpoints that will be sunset (June 2025 - Version 202506) | api_version_sunset, deprecation | published 2025-06 | Legacy endpoints that will be sunset: /adForms, /adFormResponses, /leadNotificationUrls. If not migrated to the new endpoints, follow the migration guide here . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-627976f9ff] - | Ad Analytics API (June 2025 - Version 202506) | tracking_signal | published 2025-06 | Revenue Attribution Metrics now available . Partners now have access to key business outcome metrics through the Ad Analytics API, allowing you to demonstrate LinkedIn’s impact, optimize sales and marketing strategies, and enhance lower funnel efficiency and effectiveness. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-8be9da8985] - | Add Business Email to Linkedin Application (June 2025 - Version 202506) | deprecation | published 2025-06 | Do not miss critical LinkedIn communications. We recommend partners to add their preferred business email address to their LinkedIn application to stay informed about critical LinkedIn Developer platform and product updates, including migration or deprecation notices, new APIs, or changes to current APIs. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-31946e16ad] 2025-05-15 | LinkedIn Marketing API version 202405 (May 2024) sunset on May 15, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202405 (May 2024) to migrate to the latest versions. Sunset date: May 15, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-8ff45c1361] - | LinkedIn Events Enhancements: Events Management API (May 2025 - Version 202505) | breaking_change, format_change | published 2025-05 | Events Management API: Create LinkedIn Live Test Events . Partners can now create LinkedIn Live Events on their customer's LinkedIn company page for testing purposes using a new optional field called testEvent in the request schema for POST /events. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-569f9589f8] - | Events Management API (May 2025 - Version 202505) | announcement | published 2025-05 | Partners can now create LinkedIn Live Events on their customer's LinkedIn company page for testing purposes using a new optional field called testEvent in the request schema for POST /events. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-870958bbee] - | Creatives Management API (May 2025 - Version 202505) | breaking_change, format_change | published 2025-05 | The POST /creatives endpoint now supports Event Ad creatives. For promoted LinkedIn Live events with registration forms, you can specify whether to display a video preview in the ad using the event ad boolean property hidePreviewVideo . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2112b12c70] - | Ad Analytics API (May 2025 - Version 202505) | tracking_signal | published 2025-05 | Launching Revenue Attribution Metrics We are excited to announce the availability of key business outcome metrics through the Ad Analytics API, enabling partners to demonstrate LinkedIn’s impact, optimize sales and marketing strategies, and enhance lower funnel efficiency and effectiveness. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-1f6edde8a7] - | Conversions API (May 2025 - Version 202505) | tracking_signal | published 2025-05 | The Conversions API now allows you to set a 365-day conversion lookback window for postClickAttributionWindowSize and viewThroughAttributionWindowSize when creating a new conversion rule with POST /conversions for the following conversion types: SUBMIT_APPLICATION, PURCHASE, ADD_TO_CART, QUALIFIED_LEAD, and LEAD. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-9f001dd1f5] - | Add Business Email to LinkedIn Application (May 2025 - Version 202505) | deprecation | published 2025-05 | Do not miss critical LinkedIn communications . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-5c265f9881] - | Verified on LinkedIn Pilot (May 2025 - Version 202505) | policy | published 2025-05 | Add LinkedIn Verification to your Platform . Partners now have the ability to leverage LinkedIn verification through Verified on LinkedIn feature. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-67da87e7e8] - | Ad Account Users API Updates: Find Ad Account Users by Accounts Update (May 2025 - Version 202505) | api_version_sunset, deprecation | published 2025-05 | Find Ad Account Users by Accounts Update: The GET /adAccountUsers endpoint with the q=accounts query parameter now limits user searches to only one ad account. It return matching results for only the first ad account ID, even if multiple ad account IDs are provided in the accounts query parameter. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-79a92c10aa] - | Find Ad Account Users by Accounts Update (May 2025 - Version 202505) | announcement | published 2025-05 | The GET /adAccountUsers endpoint with the q=accounts query parameter now limits user searches to only one ad account. It return matching results for only the first ad account ID, even if multiple ad account IDs are provided in the accounts query parameter. This change in behavior applies to all previous versions. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ebadc26db1] - | Unversioned Ad Account Users API Sunset (May 2025 - Version 202505) | api_version_sunset, deprecation | published 2025-05 | Starting from July 1st 2025, the deprecated unversioned API for Ad Account Users will be sunset. Please note that any calls to the API will return a 4xx error. You are recommended to use the versioned Ad Account Users API for continued access. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d8f640efb3] - | Campaign Recommendations API Sunset (May 2025 - Version 202505) | api_version_sunset, deprecation | published 2025-05 | Starting with the 202503 version, the adCampaignRecommendations and adCampaignInsights APIs have been fully sunset. Please note that any calls to these APIs using a deprecated version header will return a 426 status code error . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b394eaa68c] 2025-04-15 | LinkedIn Marketing API version 202404 (April 2024) sunset on April 15, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202404 (April 2024) to migrate to the latest versions. Sunset date: April 15, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-f7190ec8b9] - | Campaign Groups API (April 2025 - Version 202504) | announcement | published 2025-04 | Campaign Group Budget Optimization With Daily Budget . Starting with the version 202504, we’ve added an optional dailyBudget field to the campaign group object in the request payload for POST /adCampaignGroups. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-01b176ef45] - | Posts API (April 2025 - Version 202504) | announcement | published 2025-04 | Support for Buy/Shop Now Call to Action . Starting with the version 202504, partners can read and create Buy/Shop Now call to action (CTA) via the Posts API . Ecommerce advertisers frequently use this type of CTA to encourage their target audience to purchase their product or service. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-c6b5911933] 2025-03-17 | LinkedIn Marketing API version 202403 (March 2024) sunset on March 17, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202403 (March 2024) to migrate to the latest versions. Sunset date: March 17, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-618bc94c71] - | Conversions API Enhancements: Access Token Generation in Campaign Manager for Direct API (March 2025 - Version 202503) | deprecation, breaking_change, tracking_signal | published 2025-03 | Access Token Generation in Campaign Manager for Direct API : Advertisers that directly send their conversions data to LinkedIn Conversions API without integrating through supported partner platforms will now have the ability to generate access tokens for authentication directly from their Campaign Manager Ad Account. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b86a9346d1] - | Access Token Generation in Campaign Manager for Direct API (March 2025 - Version 202503) | deprecation, breaking_change, tracking_signal | published 2025-03 | Advertisers that directly send their conversions data to LinkedIn Conversions API without integrating through supported partner platforms will now have the ability to generate access tokens for authentication directly from their Campaign Manager Ad Account. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-fcb8df293b] - | Build Payload with ease ​ (March 2025 - Version 202503) | announcement | published 2025-03 | We are making it easy for developers to build the payload body of /conversionEvents endpoint and bring the auto formatted, syntactically correct json/CURL to the API call.​ This aims to reduce developer's effort to build the payload​, minimize the number of errors a developer would encounter​ and make integration… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-92407ee5f1] - | Ad Targeting Entities API (March 2025 - Version 202503) | announcement | published 2025-03 | Filter Geographies Eligible for CTV-Only Campaigns . Starting with the 202503 version, we have introduced a new optional field useCase in the typeahead finder of the Ad Targeting Entities API . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-5fe049a2a4] - | Audience Insights API Use Cases (March 2025 - Version 202503) | announcement | published 2025-03 | We’ve launched a new use cases page for the Audience Insights API. Please visit the page to explore how the API can be utilized. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e75caa5b14] 2025-02-18 | LinkedIn Marketing API version 202402 (February 2024) sunset on February 18, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202402 (February 2024) to migrate to the latest versions. Sunset date: February 18, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-774654550d] - | Events Management API (February 2025 - Version 202502) | announcement | published 2025-02 | We are excited to announce that partners can now create, schedule, and manage LinkedIn Events, including LinkedIn Live events or external events on LinkedIn, through a new Event Management API . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-480dd5fdc8] - | Media Planning API (February 2025 - Version 202502) | announcement | published 2025-02 | Forecast Cost-Per-KeyResult (CPX) Partners can now access forecast results for CPL (Cost-Per-Leads), CPR (Cost-Per-Reach), and CPM (Cost-Per-Thousand Impressions) directly through the Media Planning API. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-3bcd9f4dac] - | Event Ads API (February 2025 - Version 202502) | format_change | published 2025-02 | The Event Ads API enables campaign management partners to seamlessly create and manage Event Ads for their customers. LinkedIn Event Ads allow for scaled distribution of events directly in the LinkedIn feed to a specified target audience driving engagement, registrations, and generating live (and post-live) views. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-449d5b2975] - | DMP Segments Users API and DMP Segments Companies API (February 2025 - Version 202502) | announcement | published 2025-02 | The BATCH_CREATE method for streaming audience data of multiple users in POST /dmpSegments/users and multiple companies in POST /dmpSegments/companies has been enhanced. We now support partial batch request validation, allowing the processing of all valid elements in a batch sent in the request payload. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-69f3b22399] 2025-01-22 | LinkedIn Marketing API version 202401 (January 2024) sunset on January 22, 2025 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202401 (January 2024) to migrate to the latest versions. Sunset date: January 22, 2025. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-9472f6625c] - | Event Ads API (January 2025 - Version 202501) | format_change | published 2025-01 | The Event Ads API enables campaign management partners to seamlessly create and manage Event Ads for their customers. LinkedIn Event Ads allow for scaled distribution of events directly in the LinkedIn feed to a specified target audience driving engagement, registrations, and generating live (and post-live) views. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2ec34e69a1] - | Campaign Groups API (January 2025 - Version 202501) | announcement | published 2025-01 | Starting with the 202501 version, we’ve introduced an optional budgetOptimization field to the campaign group object in the request payload for POST /adCampaignGroups. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ae142ab615] - | Events API (January 2025 - Version 202501) | announcement | published 2025-01 | Starting with the 202411 version, we've made significant improvements to the Events schema to enhance and streamline the developer experience. Please ensure to use the updated schema to prevent any issues with event lead syncing. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ae0dd821ae] - | Media Planning API Use Cases (January 2025 - Version 202501) | announcement | published 2025-01 | We’ve launched a new use cases page for the Media Planning API. Please visit the page to explore how the API can be utilized. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-796593e8b6] 2024-12-16 | LinkedIn Marketing API version 202307 (July 2023) sunset on December 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202307 (July 2023) to migrate to the latest versions. Sunset date: December 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-1ffba4792c] 2024-12-16 | LinkedIn Marketing API version 202306 (June 2023) sunset on December 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202306 (June 2023) to migrate to the latest versions. Sunset date: December 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-4c47e098ec] 2024-12-16 | Migrate to the new Lead Sync API by December 16, 2024 (April 2024 - Version 202404) | api_version_sunset, deprecation, format_change | published 2024-04 | Collect leads from ads, events, and other organic sources via a single API The new Lead Sync API simplifies and enhances LinkedIn lead syncing capabilities by consolidating the legacy Ads Lead Sync and Events Lead Sync APIs into a single API. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-58b6c3aafd] 2024-11-15 | LinkedIn Marketing API version 202311 (November 2023) sunset on November 15, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202311 (November 2023) to migrate to the latest versions. Sunset date: November 15, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-18956f1993] - | Conversions API (November 2024 - Version 202411) | tracking_signal | published 2024-11 | External IDs Support Starting with the 202410 version, we’ve introduced an optional externalIds field to the user object in the request payload for POST /conversionEvents. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ab69e3247f] - | Ad Previews API (November 2024 - Version 202411) | format_change | published 2024-11 | Starting with the 202411 version, partners can preview ad creatives before the ads are created, through the Live Preview feature. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ccc8f5126c] - | Ad Analytics API (November 2024 - Version 202411) | format_change | published 2024-11 | New Metrics audiencePenetration and averageDwellTime We are introducing two new metrics via Ad Analytics API: Audience Penetration: This measures the approximate number of unique members reached by the advertiser divided by the approximate total target audience. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-27712bc1dc] - | Insight Tag Conversion Tracking API & Conversions API (November 2024 - Version 202411) | tracking_signal | published 2024-11 | New valueType Field Starting with the 202411 version, we have added an optional field valueType in request payload for POST /conversions. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-95a08ff9f5] - | Events API (November 2024 - Version 202411) | announcement | published 2024-11 | Starting with the 202411 version, we've made significant improvements to the Events schema to enhance and streamline the developer experience. Please ensure to use the updated schema to prevent any issues with event lead syncing. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b03ec79be3] - | Matched Audiences API (November 2024 - Version 202411) | announcement | published 2024-11 | Updated endpoint for DMP Segment List Uploads . Starting with the 202411 version, the CSV List File Upload endpoint used for audience creation has migrated from POST /media/upload to POST /dmpSegments?action=generateUploadUrl endpoint. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-eb24ba069e] - | Media Planning API (November 2024 - Version 202411) | announcement | published 2024-11 | Save and Retrieve Media Plans Starting with the 202411 version, Media Planning API will support saving and retrieving media plans via a new endpoint /mediaPlans. Use this endpoint to create and fetch media plans within an ad account. More details can be found here. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-fcb1f7ffbc] 2024-10-15 | LinkedIn Marketing API version 202310 (October 2023) sunset on October 15, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202310 (October 2023) to migrate to the latest versions. Sunset date: October 15, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-0dcbc46a36] 2024-10-15 | Offline Conversions API Sunset (September 2024 - Version 202409) | api_version_sunset, deprecation, tracking_signal | published 2024-09 | Last October, we launched the Conversions API , allowing our partners and customers to seamlessly connect both online and offline conversions directly to LinkedIn, replacing the legacy Offline Conversions API. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-cfe5b19dbf] - | Creatives API (October 2024 - Version 202410) | deprecation, format_change | published 2024-10 | Starting with the 202410 version, you can add creative names to your ads using the new name field in the Creatives API. This field is supported across all creative formats. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-9d2300ed0a] - | Ad Analytics API (October 2024 - Version 202410) | announcement | published 2024-10 | Event Stage Reporting In order to enable more granular reporting for Event Ads, the Analytics and Statistics finders now support EVENT_STAGE as a new ad analytics pivot to get analytics data for Event Ads based on the Event stage. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-8a8447aeb5] - | Associate and Verify your App (October 2024 - Version 202410) | breaking_change, policy | published 2024-10 | Please ensure that your developer app is associated with a LinkedIn Company Page to have access to the necessary features and functionality of LinkedIn Marketing API products. The organization that owns the Page you select will function as the publisher of the app. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d5515f00f7] - | AdAccounts , Campaign Groups , Campaigns , Creative API (October 2024 - Version 202410) | format_change | published 2024-10 | Starting with the January 2024 version (202401) we moved from index-based to cursor-based pagination for better scalability of our platform. To properly paginate you'll need to use the pageSize and pageToken query parameters. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-27f235daa1] 2024-09-16 | LinkedIn Marketing API version 202309 (September 2023) sunset on September 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202309 (September 2023) to migrate to the latest versions. Sunset date: September 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-e11987055a] - | Connected TV (CTV) Campaigns (September 2024 - Version 202409) | format_change | published 2024-09 | Brand Safety Capabilities Last month, we shared that our partners can now use the new boolean field connectedTelevisionOnly in Campaign API and Ad Supply Forecasts API to create and run Connected TV (CTV) video ad campaigns. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-457ffd386a] - | Media Planning API (September 2024 - Version 202409) | announcement | published 2024-09 | Forecast CTV Campaign Delivery Partners now have access to a new capability in LinkedIn’s Media Planning API to forecast CTV-only campaign delivery. Add an optional ctvOnly field in the API request to forecast CTV-only campaigns in your media plans. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-40ae905f21] - | Conversions API: Auto-campaign Association (September 2024 - Version 202409) | tracking_signal | published 2024-09 | Auto-campaign Association : A new field autoAssociateCampaigns has been added to the request query parameters for POST /conversions. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-c7647bffdb] - | AdCampaignRecommendation API Sunset (September 2024 - Version 202409) | api_version_sunset, deprecation | published 2024-09 | The AdCampaignRecommendation API endpoint was deprecated in July 2023 and has been sunset with no alternative endpoint. Please note any future calls to this API will return an error. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-c82acb386d] 2024-08-16 | LinkedIn Marketing API version 202308 (August 2023) sunset on August 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202308 (August 2023) to migrate to the latest versions. Sunset date: August 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-5f9df20ab0] - | Campaign API and Ad Supply Forecasts API (August 2024 - Version 202408) | format_change | published 2024-08 | We are excited to share that starting with the 202408 version, we have introduced a new boolean field connectedTelevisionOnly in the Campaign API and Ad Supply Forecasts . This new field enables the creation and delivery of Connected TV (CTV) video ad campaigns. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-41558d5ac8] - | Campaign API (August 2024 - Version 202408) | announcement | published 2024-08 | Now use a new field optimizationPreference in the Campaign API to set a maximum campaign-level frequency to better manage reach and frequency outcomes. Frequency is defined as the number of times an ad is served to a LinkedIn member over a specific time period. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d51f839dc6] - | Conversions API (August 2024 - Version 202408) | deprecation, tracking_signal | published 2024-08 | Deprecating MQL and SQL Conversion Types Starting with the 202408 version, we'll no longer support MARKETING_QUALIFIED_LEAD and SALES_QUALIFIED_LEAD conversion types when creating a new conversion rule. We recommend using QUALIFIED_LEAD as the conversion type, which has been available since version 202405. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ae8aa2ed8a] - | AdAnalytics API (August 2024 - Version 202408) | format_change | published 2024-08 | Reporting Changes to In-Feed Video & Sponsored Messaging Starting in July, we enhanced our measurement methodology for Video and Sponsored Messaging campaigns on LinkedIn.com and the LinkedIn mobile app to align more closely with industry standards. As a result, you may observe changes in your overall campaign reports. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-182a8044dd] - | AdAnalytics API (July 2024 - Version 202407) | format_change | published 2024-07 | Reporting changes to In-Feed Video & Sponsored Messaging At LinkedIn, we're committed to delivering measurement solutions that meet or exceed industry standards. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-665839da76] - | AdAnalytics API (July 2024 - Version 202407) | announcement | published 2024-07 | New metrics available for Sponsored Newsletter Articles We're introducing two new metrics to the API: subscriptionClicks and viralSubscriptionClicks . The subscriptionClicks metric measures the number of members whose first click on the ad in the feed is the Subscribe button. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-14c1bd86d0] - | Matched Audiences API and Conversions API (July 2024 - Version 202407) | deprecation, breaking_change, tracking_signal | published 2024-07 | To ensure the best audience match rates the following guidelines must be followed for email hashing: Convert all the email addresses to lowercase before hashing. Remove any whitespace in the email address and then generate appropriate hash. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-0bc6c1037a] - | Leadgen Forms (July 2024 - Version 202407) | announcement | published 2024-07 | Ability to apply custom Images We have introduced an enhancement to Leadgen Forms that allows advertisers to personalize their Leadgen Form backgrounds with custom images (for sponsored content only), instead of the form automatically defaulting to the ad image. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b2cc2d0ef8] - | AdCampaignGroups API (July 2024 - Version 202407) | announcement | published 2024-07 | Campaign groups may now be created with objective type. If created with an objective type, then all campaigns in the group will share the same objective type. This field is optional and immutable once created. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e0c7d0bbe2] - | Engagement Retargeting API (July 2024 - Version 202407) | announcement | published 2024-07 | New engagement source types We are introducing the ability to build retargeting audiences based on their engagement with the Document and Conversation ad formats. Once an engagement rule is created, these audiences will refresh automatically based on the trigger and time frame selected. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-52278f5b86] - | AdAnalytics API (July 2024 - Version 202407) | deprecation | published 2024-07 | Reminder to switch to approximateMemberReach field As communicated in January 2024, approximateUniqueImpressions field has been deprecated and is replaced by the new API field approximateMemberReach . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2be68ccb72] 2024-06-17 | LinkedIn Marketing API version 202305 (May 2023) sunset on June 17, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202305 (May 2023) to migrate to the latest versions. Sunset date: June 17, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-132771b420] - | DMP Segments API (June 2024 - Version 202406) | deprecation, breaking_change | published 2024-06 | We have removed the accessPolicy field due to low usage. Please note that including this in your create or update requests will fail and the field will no longer be returned in the response from READs (e.g. GET, BATCH_GET, FINDER). | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-a2bd3e0a05] 2024-05-31 | AdAccounts , Campaign Groups , Campaigns , Creative API (May 2024 - Version 202405) | format_change | published 2024-05 | Adopt cursor-based pagination by May 31, 2024 to improve scalability of our platform We're moving from index-based to cursor-based pagination. You need to use pageToken returned in the previous call to get to the next set of results, instead of accessing a random page using start and count. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-89de93b5ac] 2024-05-31 | AdAccounts , Campaign Groups , Campaigns , Creative API (April 2024 - Version 202404) | format_change | published 2024-04 | Adopt cursor-based pagination by May 31, 2024 to improve scalability of our platform We're moving from index-based to cursor-based pagination. You need to use pageToken returned in the previous call to get to the next set of results, instead of accessing a random page using start and count. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-e05f1c4270] 2024-05-31 | AdAccounts , Campaign Groups , Campaigns , Creative API (March 2024 - Version 202403) | format_change | published 2024-03 | Adopt cursor-based pagination by May 31, 2024 to improve scalability of our platform We're moving from index-based to cursor-based pagination. You need to use pageToken returned in the previous call to get to the next set of results, instead of accessing a random page using start and count. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-0d303d45ba] 2024-05-31 | AdAccounts , Campaign Groups , Campaigns , Creative API (February 2024 - Version 202402) | format_change | published 2024-02 | Adopt cursor-based pagination by May 31, 2024 to improve scalability of our platform We're moving from index-based to cursor-based pagination. You need to use pageToken returned in the previous call to get to the next set of results, instead of accessing a random page using start and count. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2cfaa317f6] 2024-05-31 | AdAccounts , Campaign Groups , Campaigns , Creative API (January 2024 - Version 202401) | breaking_change, format_change | published 2024-01 | Adopt cursor-based pagination by May 31, 2024 We are moving from index-based to cursor-based pagination. You must use pageToken returned in the previous call to get to the next set of results, instead of accessing a random page using start and count. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-09531c02f2] - | Conversions API (May 2024 - Version 202405) | tracking_signal | published 2024-05 | New Conversion Type Partners can access a new conversion type that has been added for creating conversion rules: QUALIFIED_LEAD with LinkedIn’s Conversions API . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-48336889ee] - | Media Planning API (May 2024 - Version 202405) | announcement | published 2024-05 | Forecast Lead Generation Partners now have access to a new capability in LinkedIn’s Media Planning API to forecast lead generation. With a deeper insight into forecasted leads you can now plan and launch more effective campaigns on LinkedIn. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-893e934dc5] - | Creatives API & Legacy Creatives API (May 2024 - Version 202405) | deprecation, format_change | published 2024-05 | Updates to Ad Creative Rejection Reasons . The description for a few existing rejection reasons have been updated along with a new rejection reason symbol, which could be returned as rejection reasons from the API: MISSING_UK_FCA_FINANCIAL . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-30988196ce] - | Campaign API (May 2024 - Version 202405) | announcement | published 2024-05 | The publisher blocklists and allowlists under the Brand Safety feature have been updated to include a validation logic to prevent incorrect application of blocklists and allowlists during the campaign creation or update process. For example, allowlists can only be applied as an allowlist. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-d7e14c4458] 2024-04-15 | LinkedIn Marketing API version 202304 (April 2023) sunset on April 15, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202304 (April 2023) to migrate to the latest versions. Sunset date: April 15, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-67b9da8b87] - | Posts API (April 2024 - Version 202404) | announcement | published 2024-04 | Capability to Fetch Celebration Posts API partners can now fetch celebration content type posts by using the latest 202404 version. Learn more here . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-da06e4beb2] 2024-03-15 | LinkedIn Marketing API version 202303 (March 2023) sunset on March 15, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202303 (March 2023) to migrate to the latest versions. Sunset date: March 15, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-8097af1ecc] - | Media Planning API (March 2024 - Version 202403) | announcement | published 2024-03 | Improve Campaign Results by Optimizing Audiences and Budgets | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-ebc32d0b4b] - | Campaign Recommendations (March 2024 - Version 202403) | api_version_sunset, deprecation | published 2024-03 | Endpoints to be Deprecated The adCampaignRecommendations and adCampaignInsights APIs let advertisers determine if active LinkedIn campaigns are achieving the desired reach and impact. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-64c452b564] - | LeadGenNotificationSubscription API (March 2024 - Version 202403) | announcement | published 2024-03 | New Associated Entity Type Now access a new field LeadGenNotificationAssociatedEntity to support LeadGenNotificationSubscription creation by campaign. This would allow advertisers to receive lead notifications at a campaign level. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-c5dea1f8aa] - | LinkedIn in Europe (March 2024 - Version 202403) | announcement | published 2024-03 | Changes for the Digital Markets Act Starting in February, LinkedIn made changes for members in the EEA and Switzerland to comply with new requirements imposed on us by the Digital Markets Act (DMA). | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-95a517dfbc] 2024-02-29 | Lookalike Audiences API (February 2024 - Version 202402) | api_version_sunset | published 2024-02 | Sunset on February 29 On February 29, 2024, we'll sunset the ability to create new Lookalike Audiences in both Campaign Manager and via API, as we evolve our audience solutions and invest in new solutions to help scale marketers’ first- and third-party data. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-9dfcf4f246] 2024-02-29 | Ad Preview API (January 2024 - Version 202401) | api_version_sunset | published 2024-01 | Migrate to Latest Version On February 29, 2024 we'll sunset ads preview from all API versions before 202311. To continue to support ads preview, make sure to migrate to the latest version. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-031cb81782] 2024-02-29 | Lookalike Audiences API (January 2024 - Version 202401) | api_version_sunset | published 2024-01 | Sunset on February 29 On February 29, 2024, we'll sunset the ability to create new Lookalike Audiences in both Campaign Manager and via API, as we evolve our audience solutions and invest in new solutions to help scale marketers’ first- and third-party data. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-7b28c4ee82] 2024-02-15 | LinkedIn Marketing API version 202302 (February 2023) sunset on Feb 15, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202302 (February 2023) to migrate to the latest versions. Sunset date: Feb 15, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-886560d58f] - | Conversions API (CAPI) (February 2024 - Version 202402) | deprecation, tracking_signal | published 2024-02 | Attribute LinkedIn campaigns to business outcomes Help your customers navigate measurement uncertainty and impending cookie deprecation with a solution designed to improve full funnel measurement and unlock optimization by connecting online and offline conversions to LinkedIn and using those insights to power… | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-a973e25583] - | New Lead Sync API (February 2024 - Version 202402) | announcement | published 2024-02 | Collect more leads The Lead Sync API is easier to access than ever before and includes both organic and paid leads in a single API to help your customers collect leads from more LinkedIn sources. Check out what you can do with the new API . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-64ff0396fe] - | Migrate to the new Lead Sync API (February 2024 - Version 202402) | deprecation, format_change | published 2024-02 | Collect leads from ads, events, and other organic sources via a single API The Ads Lead Sync and Events Lead Sync APIs will be deprecated and replaced with the new Lead Sync API. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-b132d22844] 2024-01-16 | LinkedIn Marketing API version 202301 (January 2023) sunset on Jan 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202301 (January 2023) to migrate to the latest versions. Sunset date: Jan 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-bb2ea16141] 2024-01-16 | LinkedIn Marketing API version 202212 (December 2022) sunset on Jan 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202212 (December 2022) to migrate to the latest versions. Sunset date: Jan 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-bac64251c0] 2024-01-16 | LinkedIn Marketing API version 202211 (November 2022) sunset on Jan 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202211 (November 2022) to migrate to the latest versions. Sunset date: Jan 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-628148684a] 2024-01-16 | LinkedIn Marketing API version 202210 (October 2022) sunset on Jan 16, 2024 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202210 (October 2022) to migrate to the latest versions. Sunset date: Jan 16, 2024. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-21ef39a4a7] - | Ad Analytics API (January 2024 - Version 202401) | deprecation, format_change | published 2024-01 | Upcoming Reach Metric Changes Starting in January 2024, approximateUniqueImpressions will be deprecated and the new API field will be called approximateMemberReach . | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-6486c00f21] - | approximateMemberReach will only be supported with pivot(s) (January 2024 - Version 202401) | format_change | published 2024-01 | CREATIVE, CAMPAIGN, CAMPAIGN_GROUP, CAMPAIGN_TYPE, OBJECTIVE_TYPE and/or SERVING_LOCATION. All requests which supply additional pivot(s) won't include approximateMemberReach in the response. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-2af06d06e6] - | Page Statistics API (January 2024 - Version 202401) | deprecation | published 2024-01 | Improving location standardization for professional demographic analytics We replace the Page professional demographic breakdown by legacy geo region and country/region with the Bing Geo market area and country/region. This provide more accurate and comprehensive geographical data. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-996d77c2a0] - | Migrate to the new Lead Sync API (January 2024 - Version 202401) | deprecation, format_change | published 2024-01 | Collect leads from ads, events, and other organic sources via a single API The Ads Lead Sync and Events Lead Sync APIs will be deprecated and replaced with the new Lead Sync API. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/recent-changes - [linkedin-4d4e917202] 2023-09-15 | LinkedIn Marketing API version 202209 (September 2022) sunset on September 15, 2023 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202209 (September 2022) to migrate to the latest versions. Sunset date: September 15, 2023. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-1c503a7197] 2023-08-16 | LinkedIn Marketing API version 202208 (August 2022) sunset on August 16, 2023 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202208 (August 2022) to migrate to the latest versions. Sunset date: August 16, 2023. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-61f3d6fbad] 2023-07-25 | LinkedIn Marketing API version 202207 (July 2022) sunset on July 25, 2023 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202207 (July 2022) to migrate to the latest versions. Sunset date: July 25, 2023. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations - [linkedin-ccf0591aec] 2023-06-15 | LinkedIn Marketing API version 202206 (June 2022) sunset on June 15, 2023 | api_version_sunset | published n/a | Developers using LinkedIn Marketing APIs version 202206 (June 2022) to migrate to the latest versions. Sunset date: June 15, 2023. Status listed: Deprecated. | https://learn.microsoft.com/en-us/linkedin/marketing/integrations/migrations ## TikTok Ads - [tiktok-4bb33d838c] 2027-01-01 | TikTok API: non-Search Legacy Manual Flow campaign creation ends; migrate to Upgraded Smart+ APIs | deprecation, breaking_change | published n/a | Starting January 1, 2027, /campaign/create/ , /campaign/copy/task/create/ , /adgroup/create/ , /ad/create/ , and /ad/aco/create/ will no longer support creating or copying non-Search Legacy Manual Flow campaigns, or creating ad groups or ads under them, for Sales, App Promotion, and Lead Generation objectives. Please migrate affected workflows to the Upgraded Smart+ APIs as soon as possible. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-5f50ba16bb] - | TikTok API guide marked to be deprecated: Create Video Shopping Ads with products from TikTok Commerce | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) Create Video Shopping Ads with products from TikTok Commerce". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-c8adf66c0b] - | TikTok API guide marked to be deprecated: Create Product Shopping Ads | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) Create Product Shopping Ads". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-418eeae377] - | TikTok API guide marked to be deprecated: Create Catalog Listing Ads | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated)Create Catalog Listing Ads". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-6ead65f05c] - | TikTok API guide marked to be deprecated: Create a Legacy Smart+ Campaign | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Create a Legacy Smart+ Campaign". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-7aff992a4a] - | TikTok API guide marked to be deprecated: Create Legacy Smart+ Lead Generation Campaigns | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Create Legacy Smart+ Lead Generation Campaigns". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-16accd7779] - | TikTok API guide marked to be deprecated: Create Legacy Smart+ Web Campaigns | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Create Legacy Smart+ Web Campaigns". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-0cccee23ef] - | TikTok API guide marked to be deprecated: Create Legacy Smart+ App Campaigns | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Create Legacy Smart+ App Campaigns". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-9e077fe0ce] - | TikTok API guide marked to be deprecated: Legacy Smart+ Campaign | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Legacy Smart+ Campaign". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-4faf11dad0] - | TikTok API guide marked to be deprecated: GMV max ads reports | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) GMV max ads reports". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-c37d89c29e] - | TikTok API guide marked to be deprecated: Supported dimensions | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) Supported dimensions". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-ff71c059a0] - | TikTok API guide marked to be deprecated: Supported metrics | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) Supported metrics". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-5d5f68c5ce] - | TikTok API guide marked to be deprecated: Get details of videos in customized posts | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Get details of videos in customized posts". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-e4523ac607] - | TikTok API guide marked to be deprecated: Legacy Smart+ | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Legacy Smart+". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-2c456f1279] - | TikTok API guide marked to be deprecated: Get the dynamic quota on Legacy Smart+ Campaigns | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Get the dynamic quota on Legacy Smart+ Campaigns". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-aa53dc4aa8] - | TikTok API guide marked to be deprecated: Update a Legacy Smart+ Campaign | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Update a Legacy Smart+ Campaign". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-60d7839788] - | TikTok API guide marked to be deprecated: Get Legacy Smart+ Campaigns | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Get Legacy Smart+ Campaigns". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-f3a9b62e0c] - | TikTok API guide marked to be deprecated: Disable or enable creatives in a Legacy Smart+ Campaign | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Disable or enable creatives in a Legacy Smart+ Campaign". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-8295a98245] - | TikTok API guide marked to be deprecated: Run a Legacy Smart+ Campaign report | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Run a Legacy Smart+ Campaign report". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-d5f126e786] - | TikTok API guide marked to be deprecated: Metrics in Legacy Smart+ Campaign reports | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To be deprecated) Metrics in Legacy Smart+ Campaign reports". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-3aaa958680] - | TikTok API guide marked to be deprecated: Get recommended budgets | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) Get recommended budgets". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 - [tiktok-36d66f2fe8] - | TikTok API guide marked to be deprecated: Get recommended bids | deprecation | published n/a | TikTok's official API docs navigation labels this guide as to-be-deprecated: "(To-be-deprecated) Get recommended bids". No date given on the label. | https://business-api.tiktok.com/portal/docs?id=1740029171730433 ## Shopify - [shopify-20201458a4] 2027-05-01 | Polaris 2.0 release candidate | deprecation | published 2026-09-24 | The Polaris 2.0 release candidate is now available for embedded App Home interfaces. It includes the Shopify admin’s new visual styles, allowing your app to adopt the new look. The new Shopify admin design began rolling out progressively to merchants on September 15, 2026. | https://shopify.dev/changelog/polaris-2-0-release-candidate - [shopify-c6bf4ebc4f] 2027-01-01 | Expiring offline access tokens required for all public apps as of January 1, 2027 | breaking_change | published 2026-05-20 | We're changing how public apps handle offline access tokens to enhance merchant data protection. Starting January 1, 2027, all public apps must use expiring offline access tokens when calling the Admin API. After that date, public apps still using non-expiring tokens will receive authentication errors. | https://shopify.dev/changelog/expiring-offline-access-tokens-required-for-all-public-apps-as-of-january-1-2027 - [shopify-3298dec977] 2026-12-01 | Built for Shopify requirements for Returns and exchanges apps and Subscription apps (effective December 1, 2026) | breaking_change, tracking_signal, policy | published 2026-06-17 | Effective December 1, 2026 , Returns and exchanges apps and Subscription apps that provide buyer-facing self-service experiences must authenticate customers using the Customer Account API. Apps that don't meet this requirement by the deadline are at risk of losing Built for Shopify status . | https://shopify.dev/changelog/built-for-shopify-requirements-for-returns-and-exchanges-and-subscription-apps - [shopify-b9a63bd92b] 2026-11-02 | Global Catalog REST API stops serving traffic on November 2, 2026 | deprecation | published 2026-10-09 | The Global Catalog REST API, which was deprecated in April 2026, stops serving traffic on November 2, 2026. If your app still calls it, you need to migrate to Global Catalog MCP, which implements the Universal Commerce Protocol (UCP), before that date. | https://shopify.dev/changelog/global-catalog-rest-api-stops-serving-traffic-on-november-2-2026 - [shopify-6c57d48c76] 2026-10-23 | New tax fields for return shipping fees in the GraphQL Admin API | announcement | published 2026-10-01 | As of API version 2026-10, the GraphQL Admin API exposes the tax amounts calculated for return shipping fees. These amounts reflect the tax calculated by the merchant's tax provider for the fee. | https://shopify.dev/changelog/new-return-shipping-fee-tax-fields - [shopify-1901086875] - | Checkout MCP and Cart MCP now support UCP buyer consent | tracking_signal, policy | published 2026-10-16 | Checkout MCP and Cart MCP now support the UCP buyer consent extension ( dev.ucp.shopping.buyer_consent ) starting with UCP 2026-08-25 . Buyers can now make the same privacy and marketing choices in your agent that they'd make in a shop's own checkout, like opting in to email or SMS. | https://shopify.dev/changelog/checkout-mcp-and-cart-mcp-now-support-ucp-buyer-consent - [shopify-27ce7057e1] - | Build with confidence: Shopify AI Toolkit's security check | policy | published 2026-10-15 | Shopify AI Toolkit now includes shopify app security check , a security command that checks your app for common vulnerabilities before you ship. You can run it before you submit an app, and on every release, to find problems in your own code and get guidance to fix them. | https://shopify.dev/changelog/build-more-secure-apps-with-shopify-s-ai-toolkit-security-check - [shopify-bd609ccaaf] - | Hydrogen 2026-10 is now available | tracking_signal | published 2026-10-14 | The new Hydrogen is generally available today. Since the developer preview started in June, we've shipped seven releases based on feedback from developers using it. The big deal about the new Hydrogen is that it isn't a big deal: Hydrogen now works with any JavaScript framework. | https://shopify.dev/changelog/hydrogen-2026-10-is-now-available - [shopify-54967f6447] - | Add shopping and Shop Pay checkout to any agent with Shop MCP | breaking_change, tracking_signal | published 2026-10-13 | Shop MCP lets your agent or app search Shopify Catalog, build carts, and complete Shop Pay checkout through a single MCP connection. It works with over 1 billion products in Shopify Catalog and doesn't require an API key for search. Nothing changes for existing Catalog API integrations, and no action is required. | https://shopify.dev/changelog/add-shopping-and-shop-pay-checkout-to-any-agent-with-shop-mcp - [shopify-216c5d8b21] - | Cart updates that result in no changes to the cart no longer trigger carts/update webhooks | announcement | published 2026-10-12 | Cart operations that leave the cart unchanged, for example, resubmitting the same values a cart already has, no longer trigger a carts/update webhook. Shopify sends a webhook every time a cart's contents or properties change. Previously, every cart operation produced a carts/update webhook. | https://shopify.dev/changelog/unchanged-carts-no-longer-trigger-carts-update-webhooks - [shopify-047a1f2c89] - | Detect when a POS extension screen finishes navigating | deprecation, breaking_change | published 2026-10-12 | The POS Navigation API adds the navigatesuccess event. It fires after the destination screen finishes its native transition, and its callback receives a standard Event. currententrychange can fire before the screen finishes appearing, and the navigate() promise doesn’t wait for the transition. | https://shopify.dev/changelog/detect-when-a-pos-extension-screen-finishes-navigating - [shopify-b72ba0cc73] - | Identify the published version running in a POS extension | breaking_change | published 2026-10-12 | shopify.extension.version returns the version of the extension that is running. It’s the same name shown on the Versions page in the Dev Dashboard and chosen when running shopify app deploy. The value is an opaque name, not a version number, so compare it for equality rather than sorting it. | https://shopify.dev/changelog/identify-the-published-version-running-in-a-pos-extension - [shopify-69e11b3ccf] - | Catalog API now returns compare-at prices as `list_price` | breaking_change | published 2026-10-09 | The Catalog API now returns a merchant’s compare-at price as list_price on each product variant. Your app or agent can use list_price to tell when a product is marked down and by how much. The price field doesn’t change. | https://shopify.dev/changelog/catalog-api-now-returns-compare-at-prices-as-list_price - [shopify-9b068e95b8] - | New `owner_type` field for metafield declarations in Checkout and Customer Account UI extensions, required in 2027-01 | breaking_change | published 2026-10-08 | Starting with API version 2026-10 , Checkout and Customer Account UI extensions can specify an owner_type for each metafield declaration in shopify.extension.toml . Starting with API version 2027-01 , owner_type is required for every metafield declaration, and deployments without it will be blocked. | https://shopify.dev/changelog/metafield-owner-types-required-for-checkout-and-customer-account-ui-extensions - [shopify-8a550391ec] - | Shopify Flow: Flow Trigger Lifecycle Callback extensions now support relative url paths | breaking_change | published 2026-10-08 | Flow Trigger Lifecycle Callback extensions now support relative URLs in addition to absolute HTTPS URLs. This works similarly to relative URLs with Flow action extensions. | https://shopify.dev/changelog/shopify-flow-flow-trigger-lifecycle-callback-extensions-now-support-relative-url-paths - [shopify-732182ba92] - | Cart mutations reject unconfirmed writes in POS UI extensions 2026-10 | breaking_change | published 2026-10-07 | In POS UI extensions API version 2026-10 , Cart API mutations reject when Shopify POS doesn't confirm that the cart changed. In earlier versions these mutations resolve whether or not POS applied the write. | https://shopify.dev/changelog/cart-mutations-reject-unconfirmed-writes-in-pos-ui-extensions-2026-10 - [shopify-7b42738ade] - | POS UI extensions now return percentage values for percentage discounts | breaking_change | published 2026-10-07 | Shopify POS 11.15 corrects the value returned by Discount.amount for Percentage discounts to match the Cart API contract. Extensions that used this value as money need to update their logic. A 25% discount on a $200 line item now returns amount: 25 . | https://shopify.dev/changelog/pos-ui-extensions-now-return-percentage-values-for-percentage-discounts - [shopify-728bc48197] - | Per-customer request limit for the Customer Account API | announcement | published 2026-10-07 | The Customer Account API now enforces a per-customer rate limit of 3000 requests per minute per store, shared across all apps. This affects all apps that call the Customer Account API, but you typically don't need to make changes because normal buyer traffic stays well under this limit. | https://shopify.dev/changelog/per-customer-request-limit-for-the-customer-account-api - [shopify-a50de090d9] - | Downgrade app access scopes from write to read | breaking_change | published 2026-10-07 | Starting with Admin GraphQL API version 2027-01 , apps that use Shopify-managed installation can call appDowngradeAccessScopes to replace optional write scopes with their matching read scopes. No action is required for existing apps. The mutation affects only the calling app’s installation. | https://shopify.dev/changelog/downgrade-app-access-scopes-from-write-to-read - [shopify-0771893028] - | What's new in Polaris 2.0.0-rc.1 | announcement | published 2026-10-01 | Polaris 2.0.0-rc.1 brings more components in line with the new admin style update, fixes several layout and event-handling bugs, and improves mounting and update performance. Table now matches the updated Shopify admin design. Tooltip can now be placed in Section's supplemental slot. | https://shopify.dev/changelog/what-s-new-in-polaris-2-0-0-rc-1 - [shopify-1078e14e8e] - | More control over commerce updates with Next Gen Events | announcement | published 2026-10-01 | With the 2026-10 API version Next Gen Events, Shopify's successor to classic webhooks, is now generally available. Events give you more customization than classic webhooks, letting you choose what changes your app receives, and what data comes with the payload. | https://shopify.dev/changelog/next-generation-events-are-now-generally-available - [shopify-b2ab7a9d22] - | New Shop Campaigns metrics and dimensions in ShopifyQL API version 2026-10 | announcement | published 2026-10-01 | Starting in API version 2026-10, ShopifyQL adds Shop Campaigns fields to two schemas. The shop_campaign_insights schema adds a shop_campaign_orders metric and country and country_code dimensions. The sales schema adds four Shop Campaign dimensions, so you can break down sales by the campaign that drove them. | https://shopify.dev/changelog/new-shop-campaigns-metrics-and-dimensions-on-api-version-2026-10 - [shopify-855598c815] - | Rollouts queries and webhooks in the Admin GraphQL API | announcement | published 2026-10-01 | Apps can now discover Rollouts, inspect their schedules, traffic allocation, and resource changes, and receive notifications when they change. | https://shopify.dev/changelog/read_rollouts - [shopify-3c9b81cdde] - | Discounts can now be included in Rollouts | breaking_change | published 2026-10-01 | Admin GraphQL API version 2026-10 adds a read-only rollouts connection across Discount types. Apps that read discounts should use Discount.rollouts alongside existing discount fields to account for Rollout-driven schedules and buyer reach. | https://shopify.dev/changelog/discounts-can-now-be-included-in-rollouts - [shopify-76e4b67ef8] - | Orders webhooks now include selling_plan_id on line items | breaking_change | published 2026-10-01 | Line items in Orders webhook payloads now include a selling_plan_id field. This field identifies the selling plan applied to a subscription line item, which helps you avoid extra API calls to look up that information. | https://shopify.dev/changelog/orders-webhooks-now-include-selling_plan_id-on-line-items - [shopify-a74e41f637] - | New fiscalDeviceIdentifier field on PointOfSaleDevice | policy | published 2026-10-01 | As of the 2026-10 GraphQL Admin API version, the PointOfSaleDevice object includes a new fiscalDeviceIdentifier field. This field returns the Shopify-assigned fiscal register identifier (manufacturing number) for a POS device. You only need to adopt it if your app supports in-person fiscal compliance workflows. | https://shopify.dev/changelog/new-fiscaldeviceidentifier-field-on-pointofsaledevice - [shopify-6ff919501d] - | `metafieldInteger` collection condition removed in API version 2027-01 | deprecation, breaking_change | published 2026-10-01 | As of API version 2027-01 , the metafieldInteger collection source condition inputs and types is removed from GraphQL Admin API. If you use metafieldInteger to create or read collection source conditions, you need to migrate to metafieldInt before you upgrade to API version 2027-01 . | https://shopify.dev/changelog/metafieldinteger-collection-condition-removed-in-api-version-2027-01 - [shopify-496aceead1] - | Added parseWarnings to ShopifyqlQueryResponse | deprecation | published 2026-10-01 | Starting in API version 2026-10, the shopifyqlQuery query in the GraphQL Admin API returns a new parseWarnings field on ShopifyqlQueryResponse . | https://shopify.dev/changelog/added-parsewarnings-to-shopifyqlqueryresponse - [shopify-13f30054ab] - | The `orderCancel` mutation now returns a structured `jobResult` | breaking_change | published 2026-10-01 | As of the 2026-10 GraphQL Admin API version, the orderCancel mutation returns a new jobResult field of type OrderCancelJobResult . Order cancellations run asynchronously. The jobResult field provides a structured, cancellation-specific result, including the cancellation status, any errors, and the affected order. | https://shopify.dev/changelog/the-ordercancel-mutation-now-returns-a-structured-jobresult - [shopify-6dcaca97ef] - | SMS marketing consent now available on the CustomerPhoneNumber object | breaking_change, deprecation, tracking_signal | published 2026-10-01 | SMS marketing consent is now available through the new smsMarketingConsent field on the CustomerPhoneNumber object. This field uses the same structured consent model as WhatsApp. The existing flat SMS marketing consent fields on CustomerPhoneNumber remain available for backward compatibility but are now deprecated. | https://shopify.dev/changelog/sms-marketing-consent-now-available-on-the-customerphonenumber-object - [shopify-9df229320f] - | Tax webhook summary and calculation requests now use Global IDs | breaking_change, format_change | published 2026-10-01 | Starting with API version 2027-01, third-party tax apps will receive Global IDs (GIDs) in tax calculation requests and tax summary webhook payloads for all entity references of the summary section. This aligns with how Partners interact with other Shopify APIs. | https://shopify.dev/changelog/tax-webhook-summary-and-calculation-requests-now-use-global-ids - [shopify-9324d5b65c] - | New SubscriptionContractCalculation API for subscription management | breaking_change | published 2026-10-01 | A new SubscriptionContractCalculation API is now available to manage subscriptions. | https://shopify.dev/changelog/new-subscriptioncontractcalculation-api-for-subscription-management - [shopify-bce29dc8bb] - | Inventory shipment webhooks include inventory transfer IDs | deprecation | published 2026-10-01 | We are introducing the inventory_transfer_id to several inventory_shipment webhook payloads to make it easier for developers to identify which inventory_transfer records, if any, a given shipment is related to. | https://shopify.dev/changelog/inventory-shipment-webhooks-include-inventory-transfer-ids - [shopify-c08a2cad6f] - | Updated function syntax on the segment query language | breaking_change, deprecation | published 2026-10-01 | As of GraphQL Admin API version 2026-10, functions in the segment query language now use the operators MATCHES / NOT MATCHES instead of = true / = false . For example, the previous query shopify_email.opened() = true would now be represented as shopify_email.opened MATCHES () . | https://shopify.dev/changelog/updated-function-syntax-on-the-segment-query-language - [shopify-c07590a776] - | Return policy profiles are now available in the GraphQL Admin API | deprecation, policy | published 2026-10-01 | API version 2026-10 adds return policy profiles to the GraphQL Admin API. A return policy profile is a set of return rules that you associate with markets, and it supersedes a store’s return policy text. Your app can now query each market's return rules as structured data, such as the length of the return window. | https://shopify.dev/changelog/return-policy-profiles-are-now-available-in-the-graphql-admin-api - [shopify-4bcfec42d3] - | New APIs for buyer-requested order edits | deprecation, policy | published 2026-10-01 | You can now manage buyer-requested order edits through the GraphQL Admin API, Customer Account API, and three new webhook topics in API version 2026-10 . Buyers can request the removal of unfulfilled line items from an order, and merchants (or apps acting on their behalf) can review, resolve, or decline those requests. | https://shopify.dev/changelog/new-apis-for-buyer-requested-order-edits - [shopify-48afb4fef2] 2026-10-01 | Script tags are deprecated and will stop running on March 1, 2027 | breaking_change, deprecation | published 2026-08-24 | Starting October 1, 2026, the scriptTagCreate and scriptTagUpdate mutations will return an user error, and the ScriptTag REST Admin API resource will reject POST and PUT . The deprecation applies to all API versions, including older ones, so pinning won't defer it. | https://shopify.dev/changelog/online-store-script-tags-deprecation - [shopify-6c2d61e03b] 2026-10-01 | Invalid metafield queries now return errors in the GraphQL Admin API | breaking_change | published 2026-07-24 | Starting in API version 2026-10, the GraphQL Admin API returns an error when a query filters by a metafield that isn't set up for filtering, instead of silently returning incorrect results. This is a breaking change. | https://shopify.dev/changelog/invalid-metafield-queries-now-return-errors-in-the-graphql-admin-api - [shopify-b18a2c544d] 2026-10-01 | Market-driven shipping now available in feature preview | breaking_change, deprecation | published 2026-07-01 | Market-driven shipping moves merchant-owned shipping configuration out of delivery profiles and into Markets. Merchants will attach shipping options directly to each market, and then vary rates by product and location conditions within a single option. | https://shopify.dev/changelog/market-driven-shipping-now-available-in-feature-preview - [shopify-3ff763580e] 2026-10-01 | Shopify AI Toolkit for upgrading extensions to Polaris web components | deprecation, breaking_change | published 2026-06-11 | The Shopify AI Toolkit now supports upgrading checkout and customer account UI extensions to new API versions, including the migration to Polaris web components. Use the AI Toolkit with your preferred AI coding agent to skip repetitive manual work and speed up the heavy lifting. | https://shopify.dev/changelog/shopify-ai-toolkit-for-upgrading-extensions-to-polaris-web-components - [shopify-35509f39e3] - | Use app intents for your discount app | announcement | published 2026-09-30 | Apps that create new discount types using Shopify Functions can now register shopify/Discount app intents. This lets Sidekick launch an app’s create and edit flows and promote them in the disambiguation picker. | https://shopify.dev/changelog/use-app-intents-for-your-discount-app - [shopify-1bdc4e06fd] - | More resilient token exchanges when migrating tokens without a user session | announcement | published 2026-09-29 | When you migrate an app from non-expiring offline tokens to expiring offline access tokens without a user session, you can now recover a lost migration response by retrying the exchange with the original non-expiring token for up to seven days. | https://shopify.dev/changelog/more-resilient-token-exchanges-when-migrating-tokens-without-a-user-session - [shopify-3e0bd72874] - | Manage packed product dimensions with the GraphQL Admin API | announcement | published 2026-09-29 | Starting with GraphQL Admin API version 2027-01 , apps can read and write packed product dimensions using InventoryItemMeasurement.packedDimensions and InventoryItemMeasurementInput.packedDimensions . Shopify uses these measurements for automatic package selection on eligible multi-item orders. | https://shopify.dev/changelog/manage-packed-product-dimensions-with-the-graphql-admin-api - [shopify-0ae65cdf61] - | Move existing subscriptions to Shopify App Pricing | announcement | published 2026-09-29 | Apps that bill with the Billing API can now move their existing subscriptions to Shopify App Pricing by using the migration tool in the Partner Dashboard or new commands in Shopify CLI. Subscriptions move at the start of their next billing cycle, and merchants don’t need to re-approve charges. | https://shopify.dev/changelog/move-existing-subscriptions-to-shopify-app-pricing - [shopify-8fa8b64372] - | Sidekick can now invoke app intents without tools | breaking_change, format_change | published 2026-09-28 | Sidekick now surfaces app extensions that declare only intents , with no tools file. Previously an extension had to declare tools to be eligible for Sidekick, so an admin.app.intent.link or admin.app.intent.render extension that registered only an intent was skipped and Sidekick never suggested the app. | https://shopify.dev/changelog/sidekick-can-now-invoke-app-intents-without-tools - [shopify-c6da071a28] - | WebMCP support for checkout | breaking_change | published 2026-09-28 | Browser agents can now read and update Shopify checkouts using WebMCP tools for checkout . The tools let agents interact with the active checkout in the buyer’s browser session. When the buyer’s input is required, such as 3D Secure authentication or for blocking UI extensions, the tools hand back control to the buyer. | https://shopify.dev/changelog/webmcp-support-for-checkout - [shopify-a58e8daef6] - | AI Toolkit skills have been consolidated to `shopify` | breaking_change, deprecation, policy | published 2026-09-25 | With today's release of AI Toolkit , all existing shopify- skills are consolidated into a single shopify skill. If you use AI Toolkit skills with agents or npx skills , you might need to update your environment. | https://shopify.dev/changelog/ai-toolkit-skills-have-been-consolidated - [shopify-84f1dd8e07] - | The new Dev Dashboard: your command center for building | announcement | published 2026-09-25 | Today we're sharing the newest wave of improvements to the Dev Dashboard. You told us, in the community forums and in support conversations, that common work like managing collaborator access or understanding app health took too much juggling. | https://shopify.dev/changelog/the-new-dev-dashboard - [shopify-7ad732c3c3] - | Shopify Payments Balance Transaction GraphQL type supports currency conversion type | announcement | published 2026-09-25 | As of GraphQL Admin API version 2026-10 , ShopifyPaymentsTransactionType now includes CURRENCY_CONVERSION type. Learn more about ShopifyPaymentsTransactionType on Shopify.dev . | https://shopify.dev/changelog/shopify-payments-balance-transaction-graphql-type-supports-currency-conversion-type - [shopify-a980724cfa] 2026-09-23 | Password Protected Shop Dev flows on Shopify Theme CLI v3.83.x and older to be deprecated | breaking_change, deprecation | published 2026-08-27 | Starting September 23, 2026, Theme commands on Shopify CLI for password protected storefronts will require version 3.84.0 or later . Versions 3.83.x and earlier will no longer be supported for theme development workflows on password protected storefronts. | https://shopify.dev/changelog/password-protected-shop-dev-flows-on-shopify-theme-cli-v3-83-x-and-older-to-be-deprecated - [shopify-7d378e15e3] - | Events subscription query complexity limit is changing to 100 points | breaking_change, policy | published 2026-09-22 | We’re reducing the query complexity limit for Events subscriptions from 250 to 100 points. This change does not affect Classic Webhooks. | https://shopify.dev/changelog/events-subscription-query-complexity-limit-is-changing-to-100-points - [shopify-f4b3ea45ac] - | Polaris CDN 1.1 is now stable | breaking_change | published 2026-09-22 | Polaris Web Components 1.1 is now available on the stable Polaris CDN channels. This is the first minor release under the CDN's new semantic versioning model . | https://shopify.dev/changelog/polaris-cdn-1-1-is-now-stable - [shopify-a88c40d5ae] - | Removing marketCurrencySettingsUpdate mutation | deprecation, breaking_change | published 2026-09-22 | As of GraphQL Admin API version 2027-01 , the marketCurrencySettingsUpdate mutation is removed, along with the MarketCurrencySettingsUpdatePayload , MarketCurrencySettingsUserError , and MarketCurrencySettingsUserErrorCode types. | https://shopify.dev/changelog/removing-marketcurrencysettingsupdate-mutation - [shopify-b7287ec6d3] - | Unlimited private plans and target stores in Shopify App Pricing | deprecation, breaking_change, policy | published 2026-09-21 | Developers using Shopify App Pricing can now create unlimited private plans per app and add unlimited target stores to each plan, replacing the previous limits of 15 private plans and 20 stores per plan. No action is required to continue using existing plans. | https://shopify.dev/changelog/unlimited-private-plans-and-target-stores-in-shopify-app-pricing - [shopify-8e4bafc745] - | New translatable boolean field for Metafield GraphQL Object | deprecation | published 2026-09-21 | API version 2026-10 adds a non-null translatable field to the Metafield object in the GraphQL Admin API. Apps that fetch translatable metafields and migrate to 2026-10 can now see whether a metafield’s value is translatable directly on the metafield itself. | https://shopify.dev/changelog/is-translatable-metafield-field - [shopify-e851e2a21b] - | The `automaticDiscounts` query is removed in API version 2027-01 | breaking_change, deprecation | published 2026-09-18 | The deprecated automaticDiscounts query is removed from the GraphQL Admin API in version 2027-01 . If your app reads a shop’s automatic discounts through automaticDiscounts , you need to move to the discountNodes query with a method:automatic filter before you upgrade to 2027-01 . | https://shopify.dev/changelog/automaticdiscounts-query-is-removed-in-api-version-2027-01 - [shopify-4cebe104f2] - | Request a bundle size exception for existing UI extensions | breaking_change, policy | published 2026-09-17 | UI extensions using API version 2025-10 or later are limited to a 64 KB compressed JavaScript bundle per extension. Full page customer account extensions may use up to 128 KB. | https://shopify.dev/changelog/request-a-bundle-size-exception-for-existing-ui-extensions - [shopify-0928c5b5b3] - | Adding a canceled receive action to the inventory shipments API | breaking_change | published 2026-09-17 | The GraphQL Admin API now supports a CANCELED receive action for inventory shipments in version 2026-10 . You can mark inventory shipment line item units as canceled when they’ll never arrive, and you can read canceled quantities on shipments and their line items. | https://shopify.dev/changelog/adding-a-canceled-receive-action-to-the-inventory-shipments-api - [shopify-92a8a39c4a] - | Removed session.currentSession.staffMemberId from POS UI Extensions (2026-10) | breaking_change, deprecation | published 2026-09-17 | As of API version 2026-10, the static session.currentSession.staffMemberId field has been removed from the POS UI Extensions Session API. It was deprecated in 2026-07 in favour of session.staffMember, a reactive signal that updates when a different staff member pins into POS. | https://shopify.dev/changelog/removed-session-currentsession-staffmemberid-from-pos-ui-extensions-2026-10 - [shopify-1e2b733880] - | Purchase Order Read API | deprecation, breaking_change | published 2026-09-17 | You can now read purchase orders through the inventoryPurchaseOrder and inventoryPurchaseOrders queries in GraphQL Admin API version 2026-10 and later. | https://shopify.dev/changelog/purchase-order-read-api - [shopify-dae7855dd7] - | Query market hierarchies with the GraphQL Admin API | breaking_change | published 2026-09-17 | The GraphQL Admin API now includes fields for querying and traversing a store’s market hierarchy in API version 2026-10 . Apps that use the read_markets access scope can retrieve parent-child relationships, navigate between related markets, and check if the asynchronously rebuilt relationship data has changed. | https://shopify.dev/changelog/market-relationships - [shopify-011f74815c] - | New Pricing audit trail for contextual product variant prices | announcement | published 2026-09-17 | The GraphQL Admin API now includes the auditTrail field on ProductVariantContextualPricing in API version 2026-10 . Apps with the read_products access scope can use this field to inspect the ordered adjustments that Shopify applied to a contextual product variant price. Existing apps do not need to take action. | https://shopify.dev/changelog/pricing-audit-trail-for-contextual-product-variant-prices - [shopify-65863b7774] - | Updates to Events payloads and subscription configuration | deprecation, breaking_change | published 2026-09-16 | Starting today, we're updating Events payloads, trigger syntax, and delivery headers. Classic Webhook subscriptions are unaffected. The flat array becomes an object containing three arrays: added , updated , and removed . | https://shopify.dev/changelog/updates-to-events-payloads-and-subscription-configuration - [shopify-7b62085a49] - | Filter Catalog search results by media type | format_change | published 2026-09-15 | The Catalog API now returns video and 3D model media on products that have it, and supports filtering search results by media type. You can request only products that have video or 3D model media attached, and matching products return links to those assets in the same response. | https://shopify.dev/changelog/filter-catalog-search-results-by-media-type - [shopify-42956c6d96] - | Dynamic complexity cost for `metafieldsSet` mutation | announcement | published 2026-09-15 | The metafieldsSet mutation now uses dynamic complexity costing. Instead of a flat cost for every call, a request's cost reflects how many distinct resources metafields were changed. Most apps need no changes, as updating a single resource remains cheap. | https://shopify.dev/changelog/dynamic-complexity-cost-for-metafieldsset-mutation - [shopify-36ff264684] 2026-09-15 | Prepare your app for the Shopify admin's new look | announcement | published 2026-09-15 | Starting September 15, 2026, the Shopify admin has a new look, rolling out progressively to merchants. Apps that use Admin UI extensions and App Home UI extensions pick up the new styles automatically. Apps that render their own interface in App Home keep their current styles until you choose to move to Polaris 2.0. | https://shopify.dev/changelog/prepare-your-app-for-the-shopify-admins-new-look - [shopify-86de7eaf56] - | family_name is optional for B2B orders in Payments Apps API requests | announcement | published 2026-09-15 | B2B checkout treats the buyer’s surname as optional, so payment session requests for B2B orders can omit family_name in shipping_address and billing_address . This affects payments apps that handle B2B orders through the Payments Apps API and currently require family_name in these addresses. | https://shopify.dev/changelog/family_name-is-optional-for-b2b-orders-in-payments-apps-api-requests - [shopify-2bfcade92e] - | Delivery options in Shopify Functions input now expose their metafields | breaking_change | published 2026-09-15 | Shopify Functions can now read metafields attached to delivery options in the cart. On API version 2026-10 , you can call metafield(namespace:, key:) on any option in cart.deliveryGroups.deliveryOptions . | https://shopify.dev/changelog/delivery-options-in-shopify-functions-input-now-expose-their-metafields - [shopify-87067d66b8] - | Discounts Allocator Function API developer preview has ended | breaking_change, deprecation | published 2026-09-10 | The Discounts Allocator Function API, available only through the Discounts Allocator developer preview, has been removed and won’t be released. The developer preview is closed. Most developers don’t need to take action. | https://shopify.dev/changelog/discounts-allocator-function-api-developer-preview-has-ended - [shopify-77e96c6af5] - | Create and delete dev stores in Shopify CLI | deprecation | published 2026-09-09 | Shopify CLI 4.8 adds shopify store commands that let you create and manage dev stores from your terminal or coding agent. These commands are available after you update to Shopify CLI 4.8. | https://shopify.dev/changelog/create-and-delete-dev-stores-in-shopify-cli - [shopify-d7b3e42f17] - | Variants now support multiple barcodes | breaking_change, deprecation | published 2026-09-08 | Merchants often sell the same variant under more than one identifier: a manufacturer UPC alongside a private-label EAN, a GTIN, a reissued ISBN, or an ASIN for a marketplace listing. Until now a variant held a single barcode value, so the extras ended up in metafields, tags, or outside Shopify entirely. | https://shopify.dev/changelog/product-variant-barcode-is-being-replaced-by-barcodes - [shopify-8d42e9d739] - | Customer Address APIs now support countryCode | deprecation | published 2026-09-08 | Starting with Customer Account API version 2026-10, customer address inputs and objects support countryCode . The existing territoryCode field is deprecated but remains fully supported, so current integrations continue working without interruption. | https://shopify.dev/changelog/customer-address-apis-now-support-countrycode - [shopify-5304db39b0] - | Shopify storefronts now support UCP 2026-08-25 | format_change | published 2026-09-04 | Shopify storefronts now advertise support for Universal Commerce Protocol (UCP) version 2026-08-25 in their discovery profiles at /.well-known/ucp . This update adds compatibility with the 2026-08-25 protocol release and doesn’t require any changes to your existing integrations. | https://shopify.dev/changelog/08-25-is-now-supported - [shopify-e3b6121d9a] - | Hydrogen developer preview update: September 2, 2026 | announcement | published 2026-09-03 | The Hydrogen developer preview adds new capabilities to the toolkit and extends the ways developers can build Shopify storefronts: Variant links: Links that name a variant, like the ones Shopify submits to a Google Shopping feed, now open on that variant instead of the product's default. | https://shopify.dev/changelog/hydrogen-developer-preview-update-september-2-2026 - [shopify-bb5040e941] - | New paymentInstrumentSendAddEmail mutation emails customers a link to add a payment method for a subscription, order, or draft order | breaking_change | published 2026-09-03 | You can now use the paymentInstrumentSendAddEmail mutation in the GraphQL Admin API to email a customer a link for adding a payment method to a specific resource (for example, a subscription contract). | https://shopify.dev/changelog/new-paymentinstrumentsendaddemail-mutation - [shopify-a5907d08a8] - | Polaris CDN 1.1 release candidate | announcement | published 2026-08-31 | Polaris Web Components loaded from the Shopify CDN are moving to semantic versioning, read more about that change here . You can test out the Polaris CDN 1.1 release candidate by updating the URL you load polaris from to this: EmptyState . | https://shopify.dev/changelog/polaris-cdn-1-1-release-candidate - [shopify-6c3c939b28] - | The Polaris CDN is adopting semantic versioning | breaking_change, policy | published 2026-08-31 | Polaris Web Components loaded from the Shopify CDN are moving to semantic versioning. Most apps will continue receiving compatible improvements automatically, while developers can choose when to adopt breaking changes. Existing apps don’t need to take immediate action. | https://shopify.dev/changelog/the-polaris-cdn-is-adopting-semantic-versioning - [shopify-1d7e46a1b9] 2026-08-31 | Storefront MCP cart tools are being deprecated in favour of UCP Cart MCP | breaking_change, deprecation | published 2026-06-24 | The cart tools on the Storefront MCP server are being deprecated in favour of the UCP-conforming Cart MCP tools: get_cart and update_cart on https://{shop}.myshopify.com/api/mcp are deprecated. | https://shopify.dev/changelog/storefront-mcp-cart-tools-are-being-deprecated-in-favour-of-ucp-cart-mcp - [shopify-f3210430c0] - | More resilient refreshes for expiring offline access tokens | api_version_sunset, breaking_change | published 2026-08-28 | Expiring offline access token refreshes now retain the previously used refresh token until an app begins using its replacement. This rollout helps apps recover when a refresh response is lost or isn’t persisted. No migration is required, but apps should continue to store every refreshed token pair atomically. | https://shopify.dev/changelog/more-resilient-refreshes-for-expiring-offline-access-tokens - [shopify-83b0e68c36] - | Four additional topics are now available for Events | announcement | published 2026-08-26 | Apps can now subscribe to events for Metaobject , MetafieldDefinition , MetaobjectDefinition , and InventoryTransfer . Apps can also subscribe to targeted metafield changes on InventoryTransfer . | https://shopify.dev/changelog/four-additional-topics-are-now-available-for-events - [shopify-97fa77548f] - | Build Shopify apps in PHP and Python with new official packages | deprecation, policy | published 2026-08-26 | Shopify now publishes official, open-source packages for building apps in PHP and Python. shopify/shopify-app-php on Packagist and shopifyapp on PyPI have reached version 1.0 . They provide framework-agnostic primitives for request verification, token exchange, and Admin GraphQL requests. | https://shopify.dev/changelog/build-shopify-apps-in-php-and-python-with-new-official-packages - [shopify-73c7dddc99] - | GitHub commits now name the last theme editor | announcement | published 2026-08-26 | When you edit a theme in the Shopify admin, the commit Shopify pushes to your connected branch now includes the editor's name in the body: Update from Shopify for theme Dawn Committed from shop: Snowdevil Theme last edited by: Bob Bobsen The name is plain text in the commit body. | https://shopify.dev/changelog/github-commits-now-name-the-last-theme-editor - [shopify-f406f87bf6] - | Oxygen is now available on trial plan stores | breaking_change | published 2026-08-25 | You can now deploy Hydrogen storefronts to Oxygen from trial plan stores . Previously, Oxygen hosting required a paid plan. Note that trial plan stores don't include public environments, so deployment URLs always require a store login. Learn more about supported plans . | https://shopify.dev/changelog/oxygen-is-now-available-on-trial-plan-stores - [shopify-32137d86ea] - | App intents on `admin.app.intent.link` now open as a full-page navigation | announcement | published 2026-08-19 | When Sidekick invokes an app intent declared on the admin.app.intent.link extension target, the Shopify admin now navigates the merchant to your extension's url as a full page, matching how Shopify's own admin intents behave. | https://shopify.dev/changelog/app-intents-on-admin-app-intent-link-now-open-as-a-full-page-navigation - [shopify-6ae2b6e1f2] - | Hydrogen developer preview update: August 18, 2026 | tracking_signal | published 2026-08-18 | The Hydrogen developer preview adds new capabilities to the toolkit and extends the ways developers can build Shopify storefronts: Cart session attribution: Carts and Customer Account sessions stay in step, so signed-in shoppers reach checkout with their saved details instead of a guest flow. | https://shopify.dev/changelog/hydrogen-developer-preview-update-august-18-2026 - [shopify-faede96959] - | Shop Campaigns performance data now available via ShopifyQL | breaking_change | published 2026-08-10 | The shop_campaign_insights schema is now available in the ShopifyQL . Analytics and reporting apps can query Shop Campaigns performance data on behalf of authorized merchants using the existing shopifyqlQuery field with read_reports scope. | https://shopify.dev/changelog/shop-campaigns-shopifyql - [shopify-78a396b7cc] - | Standard storefront events and actions now support cart attributes | announcement | published 2026-08-06 | The updateCart standard action now updates cart attributes, and a new shopify:cart:attributes-update event fires whenever an attributes update is initiated. Before this, changing an attribute meant calling the Storefront API yourself, and nothing told your app when one changed. | https://shopify.dev/changelog/events-and-actions-cart-attributes-support - [shopify-77bd13a4d4] - | Draft order and transfer/shipment inventory is moving from reserved to committed | deprecation | published 2026-08-05 | We're consolidating how in-progress inventory holds are represented. Inventory that was previously tracked under the reserved quantity state for draft orders, transfers, and shipments is being moved to the committed quantity state. | https://shopify.dev/changelog/draft-order-and-transfer-shipment-inventory-is-moving-from-reserved-to-committed - [shopify-a56892fff9] - | WebMCP support for Liquid and Hydrogen storefronts | announcement | published 2026-08-05 | Online stores now expose WebMCP tools that AI agents can call. Agents can search your catalog, manage the shopper's cart, and go to checkout on the shopper's behalf, all in the tab they're looking at. The tools work through WebMCP , a proposed web standard that lets a page register tools with the browser. | https://shopify.dev/changelog/webmcp-liquid-hydrogen - [shopify-3d125c9e66] - | Oxygen is now available on development stores | breaking_change | published 2026-08-03 | You can now deploy Hydrogen storefronts to Oxygen from dev stores . Previously, Oxygen hosting required a paid plan. Note that development stores don't include public environments, so deployment URLs always require a store login. Learn more about supported plans . | https://shopify.dev/changelog/oxygen-is-now-available-on-development-stores - [shopify-92f2461e4d] - | The `orderCreate` mutation now supports multiple tracking numbers for each fulfillment | tracking_signal | published 2026-08-03 | We’ve added a trackingNumbers field to OrderCreateFulfillmentInput , so you can attach multiple tracking numbers to a fulfillment when importing orders. | https://shopify.dev/changelog/order-create-fulfillment-tracking-numbers - [shopify-7b6335933f] - | Updated Built for Shopify requirements for Fulfillment services apps | breaking_change | published 2026-08-01 | We've updated three Built for Shopify requirements for Fulfillment services apps . The updated thresholds better reflect how fulfillment operations run in practice, making Built for Shopify achievable for more high-quality fulfillment apps. No action is required. | https://shopify.dev/changelog/updated-built-for-shopify-requirements-for-fulfillment-services-apps - [shopify-5dbc8eb74f] - | Hydrogen developer preview update: July 30, 2026 | tracking_signal | published 2026-07-31 | The Hydrogen developer preview adds new capabilities to the toolkit and extends the ways developers can build Shopify storefronts: Vue bindings: Build your storefront in Vue with the same Hydrogen APIs you know from React, through the new @shopify/hydrogen/vue entrypoint. | https://shopify.dev/changelog/hydrogen-developer-preview-update-july-30 - [shopify-0611cd3bdf] - | New fields for cash management activities and drawers in POS | announcement | published 2026-07-31 | New fields are now available on cash management resources in the GraphQL Admin API, providing more detail about cash drawer balances and cash count activities. The CashDrawer object now exposes the current drawer balance directly: | Field | Description | | | https://shopify.dev/changelog/new-fields-for-cash-management-activities-and-drawers - [shopify-6504c55b01] - | Merchants now see partner details on collaborator requests | policy | published 2026-07-30 | When a merchant approves a request, they're giving a partner access to a live store — and merchants need enough context to make that decision with confidence. Building on identity verification for partners , merchants now see details about your partner organization on every new collaborator request. | https://shopify.dev/changelog/partner-details-on-collaborator-requests - [shopify-f44d7ce0b6] - | The shopify-account component for customer accounts is now a Theme Store requirement | deprecation, breaking_change | published 2026-07-30 | In February 2026, we introduced the shopify-account component , which lets customers sign in and manage their account directly on the storefront. It supports passwordless sign-in, automatic Sign in with Shop recognition, and social sign-in providers. | https://shopify.dev/changelog/the-shopify-account-component-for-customer-accounts-is-now-a-theme-store-requirement - [shopify-5560bb9a1d] - | createdAt is now available on the Customer object in Shopify Functions | breaking_change | published 2026-07-30 | Shopify Functions API version 2026-10 adds a createdAt field to the Customer object. You can now use the date and time a customer account was created in Function logic. This is an additive change; no action is required for existing Functions. | https://shopify.dev/changelog/createdat-is-now-available-on-the-customer-object-in-shopify-functions - [shopify-b9de270b79] - | Updating an order's shipping address recalculates taxes as of API version 2026-10 | breaking_change | published 2026-07-30 | As of API version 2026-10 , changing the shipping address on an unfulfilled order through the orderUpdate GraphQL mutation or the REST Admin API order update endpoint recalculates the order's taxes against the new destination. | https://shopify.dev/changelog/updating-an-orders-shipping-address-returns-accurate-financial-data - [shopify-16352d01b7] - | POS UI extensions can now print directly to hardware receipt printers | deprecation, breaking_change | published 2026-07-27 | POS UI Extensions 2026-07 introduces the Printing API ( shopify.printing ), which enables extensions to discover hardware printers with getPrinters() and send documents directly to a connected receipt printer with print() . The Printing API supersedes shopify.print , which is now deprecated. | https://shopify.dev/changelog/pos-ui-extensions-can-now-print-directly-to-hardware-receipt-printers - [shopify-473193ce4e] - | SubscriptionContractCalculation API now available in early access | announcement | published 2026-07-27 | The new SubscriptionContractCalculation object on the GraphQL Admin API is now available in early access on the 2026-10 release candidate API version. | https://shopify.dev/changelog/subscription-contract-calculation-api-now-available-in-early-access - [shopify-207a006a5f] - | Meet the 2026 Shopify Build Award winners | format_change | published 2026-07-22 | Every year at DotDev, we hand out the Build Awards. Not for the biggest company or the flashiest launch, but for the partners building what matters most to merchants. This year we are recognizing excellence across four categories: apps, storefronts, merchant impact, and community. | https://shopify.dev/changelog/shopify-build-award-2026 - [shopify-2474495023] - | Metafield triggers and additional topics are now available for Events | breaking_change | published 2026-07-21 | Apps can now subscribe to events for Order , Collection , InventoryItem , InventoryShipment , Location , and can subscribe to metafield changes on Product , Order , Customer , Collection and Location . ProductVariant metafields are supported through the Product topic. | https://shopify.dev/changelog/metafield-triggers-and-additional-topics-are-now-available-for-events - [shopify-93341757eb] - | Liquid templates can now compose pages with blocks and partials | announcement | published 2026-07-21 | The Liquid July ’26 developer preview introduces a simpler way to build theme pages. Page structure can live directly in a Liquid template, where developers and coding agents can read and edit everything in one place. The peview adds two Liquid tags: {% block %} renders a reusable theme block directly from a template. | https://shopify.dev/changelog/developer-preview-liquid-block-and-partial-tags - [shopify-b013777684] - | Full-stack capabilities to power app analytics | announcement | published 2026-07-21 | For app developers, building merchant-facing analytics has always meant standing up your own stack: a charting library, a data warehouse to sync merchant data into, handling currencies and locales, and a UI that never quite matched the Shopify admin. | https://shopify.dev/changelog/full-stack-capabilities-to-power-app-analytics - [shopify-a51ec39d39] - | Identity verification for Shopify Partners starts today | breaking_change, policy | published 2026-07-09 | Trust is foundational to the Shopify Partner ecosystem. Partners take actions across Shopify that can directly affect merchants, and merchants need confidence when granting access to their stores. | https://shopify.dev/changelog/identity-verification-for-partners - [shopify-d185346d2c] - | POS UI extensions 2026-07 uses per-unit fixed-amount line item discounts | breaking_change | published 2026-07-08 | Starting with POS UI extensions API version 2026-07, FixedAmount line item discounts passed to setLineItemDiscount and bulkSetLineItemDiscounts from the Cart API must represent a per-unit discount. | https://shopify.dev/changelog/pos-ui-extensions-2026-07-uses-per-unit-fixed-amount-line-item-discounts - [shopify-3899938c1a] - | Customer Account API Customer.lastIncompleteCheckout and Checkout types removed in 2026-10 | deprecation, breaking_change | published 2026-07-06 | As of Customer Account API version 2026-10, the deprecated Customer.lastIncompleteCheckout field is removed. | https://shopify.dev/changelog/customer-account-api-last-incomplete-checkout-and-checkout-types-removed - [shopify-b7e8e9336d] - | OrderDisplayFulfillmentStatus now returns FULFILLMENT_NOT_REQUIRED for orders with no items to fulfill | breaking_change, deprecation | published 2026-07-03 | As of API version 2026-10, the OrderDisplayFulfillmentStatus enum can return a new value: FULFILLMENT_NOT_REQUIRED . It is returned for orders that are not fulfilled but have no items remaining to fulfill — for example, an order that was fully cancelled or fully refunded before any items were fulfilled. | https://shopify.dev/changelog/orderdisplayfulfillmentstatus-now-returns-fulfillmentnotrequired - [shopify-6b7f7093dd] - | Deprecating the useBuyerJourneyIntercept API on checkout UI extensions | breaking_change, deprecation | published 2026-07-02 | Starting in version 2026-07 , the useBuyerJourneyIntercept hook on checkout UI extensions, and the block_progress capability it depends on, are deprecated. Existing extensions will continue to work on current and prior API versions, but this API will be removed in a future version , so you should plan to migrate. | https://shopify.dev/changelog/deprecating-the-usebuyerjourneyintercept-api-on-checkout-ui-extensions - [shopify-a40ef6c364] - | Deprecation of cumulative marketing engagements | breaking_change, deprecation | published 2026-07-01 | The isCumulative argument to the marketingEngagementCreate mutation is being deprecated, defaulting to false . Please update your integration to send non-cumulative engagements, as needed. Existing activities that have been sending cumulative metrics can migrate to non-cumulative at any time. | https://shopify.dev/changelog/deprecation-of-cumulative-marketing-engagements - [shopify-dbb116eab2] - | `discountedUnitPrice` on `DraftOrderLineItem` Customer Account API deprecation | deprecation | published 2026-07-01 | The discountedUnitPrice field on the DraftOrderLineItem object in the Customer Account API is now deprecated. Use approximateDiscountedUnitPrice instead. This new field calculates the discounted total divided by the quantity, resulting in an approximate per-unit price reduction. | https://shopify.dev/changelog/discountedunitprice-on-draftorderlineitem-customer-account-api-deprecation - [shopify-ad32ddb511] - | Merchant-owned delivery profile APIs are deprecated for market-driven shipping | deprecation, breaking_change | published 2026-07-01 | We’re moving merchant-owned shipping configuration from legacy delivery profiles to Markets as part of market-driven shipping, a new model where shipping is configured per Market. | https://shopify.dev/changelog/merchant-owned-delivery-profile-apis-are-deprecated-for-market-driven-shipping - [shopify-64f11d06b8] - | Carrier services will no longer be automatically added to the default shipping profile | deprecation, breaking_change | published 2026-06-26 | Starting with GraphQL Admin API version 2026-10, creating a carrier service no longer automatically adds it to the shop’s General shipping profile. | https://shopify.dev/changelog/carrier-services-will-no-longer-be-automatically-added-to-the-default-shipping-profile - [shopify-ff669646ae] - | `DraftOrderDiscountNotAppliedWarning.priceRule` removed in GraphQL Admin API 2026-10 | deprecation, breaking_change | published 2026-06-23 | Starting with GraphQL Admin API version 2026-10 , the deprecated priceRule field on the DraftOrderDiscountNotAppliedWarning object is removed. | https://shopify.dev/changelog/remove-pricerule-from-draft-order-discount-warning - [shopify-c4d0b218b2] - | Removal of ITEM_NOT_STOCKED_AT_LOCATION error | breaking_change, deprecation | published 2026-06-19 | The ITEM_NOT_STOCKED_AT_LOCATION error will be removed from InventoryAdjustQuantities , InventoryMoveQuantities , InventorySetOnHandQuantities , and InventorySetQuantitiesUserErrorCode as of API version 2026-10. Following the changes described here , inventory quantities can now be adjusted at any location. | https://shopify.dev/changelog/removal-of-itemnotstockedatlocation-error - [shopify-453b6b02e7] - | WhatsApp marketing consent now available in the Admin API and Customer Account API | breaking_change, tracking_signal | published 2026-06-17 | WhatsApp marketing consent can now be managed through both the Customer Account and Admin APIs. Use the customerWhatsAppMarketingConsentUpdate mutation to update a customer’s WhatsApp marketing consent status for their default phone number. | https://shopify.dev/changelog/whatsapp-marketing-consent-now-available - [shopify-47616e53d3] - | New Collection model and APIs now available | deprecation, breaking_change | published 2026-06-17 | The 2026-07 release replaces a collection’s single ruleSet with a multi-source model in the GraphQL Admin API. Each collection now has one or more CollectionSource objects that define typed inclusion and exclusion conditions, plus manual selections. | https://shopify.dev/changelog/new-collection-model-and-apis-now-available - [shopify-773bb18343] - | Metafields now require a definition to be accessed through the Customer Account API | deprecation, breaking_change | published 2026-06-16 | Starting today, metafields stored on the app resource must have a metafield definition and customer accounts permissions to be accessible through the Customer Account API. Going forward, when calling the Customer Accounts API, app metafields without a definition will no longer return a value. | https://shopify.dev/changelog/metafields-now-require-a-definition-to-be-accessed-through-the-customer-account-api - [shopify-cccf5bd326] 2026-06-15 | Storefront Catalog MCP now implements UCP | breaking_change, deprecation | published 2026-04-22 | The following UCP catalog tools in Storefront Catalog are now available: - `search_catalog`: Search a store's product catalog with filters, pagination, and buyer context - `lookup_catalog`: Batch lookup products or variants by identifier with inputs correlation - `get_product`: Retrieve full product details with… | https://shopify.dev/changelog/storefront-catalog-mcp-now-implements-ucp - [shopify-6e8d77fa92] - | Removing deprecated PRIVATE and PUBLIC_READ enums on metaobject definitions | deprecation, breaking_change | published 2026-05-20 | We are updating the MetaobjectAdminAccess enum by deprecating the PRIVATE and PUBLIC_READ values. These values are now obsolete and are never returned by the API. This change removes ambiguity, as the deprecated access values do not accurately reflect the actual access behaviors. | https://shopify.dev/changelog/removing-deprecated-private-and-publicread-enums-on-metaobject-definitions - [shopify-49b0a274d0] - | Bots and agents should identify themselves via Web Bot Auth | breaking_change, policy | published 2026-05-07 | Shopify now applies stricter rate limits to bots and agents that access the Storefront API and Shopify-hosted online store pages. Bots and agents that don't sign their requests are subject to the strictest limits. To qualify for higher rate limits, operators should sign their requests with Web Bot Auth. | https://shopify.dev/changelog/bots-and-agents-should-identify-themselves-via-web-bot-auth - [shopify-f84dd603ea] - | App deployment in CI/CD is now available for all apps | breaking_change, policy | published 2026-05-06 | App deployment in CI/CD is now available for all apps through app automation tokens on the Dev Dashboard. These tokens offer app-scoped authentication, allowing you to use the latest Shopify CLI to automate app releases in GitHub Workflows and similar tools. | https://shopify.dev/changelog/app-deployment-in-cicd-is-now-available-for-all-apps - [shopify-6c4ca60d42] - | Ship and pickup in one order now available in feature preview | breaking_change, policy | published 2026-05-06 | Shopify Plus and Enterprise merchants will soon be able to enable a single checkout experience where customers can choose both shipping and store pickup within the same order. Previously, customers had to place separate orders for each delivery method. | https://shopify.dev/changelog/ship-and-pickup-in-one-order-feature-preview - [shopify-c6258a438e] - | Deprecation of checkout metafields in checkout and customer account UI extensions | deprecation, breaking_change | published 2026-04-27 | As of API version 2026-04, the ability to read and write checkout metafields in checkout and customer account UI extensions has been removed. Instead, checkout metafields have been replaced by cart metafields in checkout UI extensions and order metafields in customer account UI extensions. | https://shopify.dev/changelog/deprecation-of-checkout-metafields-in-checkout-and-customer-account-ui-extensions - [shopify-614290c6be] - | `totalUnsettledSet` calculation fixed for pending captures | breaking_change, policy | published 2026-04-24 | The totalUnsettledSet field on the OrderTransaction object now correctly calculates the unsettled amount when a capture is in pending status. The affected field is OrderTransaction.totalUnsettledSet . | https://shopify.dev/changelog/totalunsettledset-calculation-fixed-for-pending-captures - [shopify-3bfad053f7] - | Automatic CSS subsetting for `{% stylesheet %}` tags | breaking_change | published 2026-04-23 | Shopify is introducing CSS content subsetting for {% stylesheet %} tags to improve storefront performance. | https://shopify.dev/changelog/automatic-css-subsetting-for-stylesheet-tags - [shopify-7108c79ef2] - | `inventoryActivate` now preserves `available` quantity | breaking_change, deprecation, tracking_signal, policy | published 2026-04-17 | As of API version 2026-04, using the inventoryActivate mutation without specifying an available or onHand argument will no longer default these values to zero. If an item was previously active at a location, any existing active and onHand quantities for the inactive InventoryLevel will be retained. | https://shopify.dev/changelog/inventoryactivate-now-preserves-available-quantity - [shopify-4eb1ac1629] - | `ActionBar` removed on mobile: `TitleBar` primary action now renders as an icon button | breaking_change, deprecation | published 2026-04-15 | On mobile, the primary and secondary actions defined on your TitleBar are changing how they render: The primary action now displays as an icon-only button in the mobile header, rather than in a bottom bar with icon and text. Secondary actions now appear in the overflow menu, creating a more consistent mobile interface. | https://shopify.dev/changelog/primary-action-icon-replaces-actionbar-on-mobile - [shopify-47b4ddddf9] 2026-04-15 | Shopify Scripts will be deprecated on June 30, 2026 | deprecation | published 2026-04-09 | We are enhancing Shopify Functions with new capabilities for discounts, shipping, and payments. These improvements aim to replace the functionalities you previously achieved using Shopify Scripts, allowing you to build custom logic tailored to your unique business needs. | https://shopify.dev/changelog/shopify-scripts-will-be-deprecated-on-june-30-2026 - [shopify-1c395fa864] - | New CSS variable for mobile safe area insets | breaking_change, tracking_signal | published 2026-04-13 | A new CSS custom property, --shopify-safe-area-inset-bottom , is now available for embedded apps running on Shopify Mobile. This property provides the exact pixel value of host UI overlays, such as the floating bottom navigation bar, to prevent apps from placing fixed-position content over these overlays. | https://shopify.dev/changelog/new-css-variable-for-mobile-safe-area-insets - [shopify-de04b16ca0] - | DraftOrderLineItem.grams field removed in 2026-07 | breaking_change, api_version_sunset, deprecation | published 2026-04-13 | We are removing the grams field from the DraftOrderLineItem object in the Admin GraphQL API, starting with version 2026-07. This field was deprecated over 8 years ago. After the 2026-04 API version becomes unsupported, any queries referencing DraftOrderLineItem.grams will return an error. | https://shopify.dev/changelog/draftorderlineitemgrams-field-removed-in-2026-07 - [shopify-2d55234848] - | New discount fields in the Storefront API's cart types | deprecation | published 2026-04-10 | As of API version 2026-07, several changes have been introduced to the discount fields and amounts in the Storefront API . Deprecated Fields : The cart.discountAllocations field is deprecated. Use cart.lines[].discountAllocations(lineLevelOnly: false) and cart.deliveryGroups[].discountAllocations instead. | https://shopify.dev/changelog/new-discount-fields-in-the-storefront-cart-graphql-api - [shopify-f62257bcd0] 2026-04-07 | Replacing or deleting a Shopify-hosted file no longer purges its CDN URL | breaking_change, deprecation | published 2026-04-07 | As of April 7, 2026, when you replace or delete a file in the Shopify admin, Shopify will no longer proactively purge the file's URL on cdn.shopify.com/.... The previously cached content will continue to be served until the URL's TTL (Time to Live) expires. | https://shopify.dev/changelog/replacing-or-deleting-a-shopify-hosted-file-no-longer-purges-its-cdn-url - [shopify-de7df48cf5] 2026-04-02 | Removing `visible_to_storefront_api` field on metaobject field definitions | deprecation, breaking_change | published 2026-03-30 | The visibleToStorefrontApi field/input field is deprecated and removed from the unstable version of the GraphQL Admin API for the following types: MetaobjectFieldDefinition MetaobjectFieldDefinitionCreateInput MetaobjectFieldDefinitionUpdateInput StandardMetaobjectDefinitionFieldTemplate Anyone using… | https://shopify.dev/changelog/removing-storefront-visibility-field-on-metaobject-field-definitions - [shopify-bd286c7443] - | Payment method identifier now required for customerPaymentMethodRemoteCreate | breaking_change | published 2026-04-01 | As of API version 2026-07, the payment method identifier field is now required when using the customerPaymentMethodRemoteCreate mutation with Stripe, Authorize.net, or Braintree inputs. | https://shopify.dev/changelog/payment-method-identifier-now-required-for-customerpaymentmethodremotecreate - [shopify-2cdc12d054] 2026-04-01 | Expiring offline access tokens required for new public apps as of April 1, 2026 | deprecation, breaking_change, policy | published 2026-03-20 | We're updating how public apps handle offline access tokens to enhance merchant data protection. Starting April 1, 2026, all new public apps must request and use expiring offline access tokens . | https://shopify.dev/changelog/expiring-offline-access-tokens-required-for-public-apps-april-1-2026 - [shopify-7ab8a14f0a] 2026-03-26 | Clearer standards for app listing images | breaking_change | published 2026-03-12 | We've updated requirement 4.4.4 and added a new requirement 4.4.5 for Shopify App Store apps. Requirement 4.4.4 now provides clearer standards for image quality: images should primarily show your app's actual user interface and features. Screenshots must not include desktop backgrounds or browser windows. | https://shopify.dev/changelog/clearer-standards-for-app-listing-images - [shopify-b7d026a555] - | The Shopify CLI app release `--force` flag is deprecated and will be removed | breaking_change, deprecation | published 2026-03-25 | We are deprecating the --force flag on the shopify app deploy and shopify app release commands. The flag will be removed in a Shopify CLI release in May 2026. The --force flag skips all confirmation prompts, including for extension deletions that can permanently remove data on installed shops. | https://shopify.dev/changelog/the-shopify-cli-app-release-force-flag-is-deprecated-and-will-be-removed - [shopify-b59deab7bf] 2026-03-24 | Bare query strings no longer bust the cache for assets | deprecation, breaking_change, format_change | published 2026-03-02 | We're enhancing Shopify's asset caching to improve load times. As part of this update, we are modifying the URL query parameters recognized for cache busting. Effective March 24, 2026, bare query strings (a ? followed by a value with no key) will not refresh cached assets. | https://shopify.dev/changelog/bare-query-strings-no-longer-bust-the-cache-for-assets - [shopify-021378b8cd] - | Removal of pre_tax_price from the Order REST Admin API | breaking_change, deprecation | published 2026-03-23 | The pre_tax_price and pre_tax_price_set fields on order line items in the REST Admin API are being removed. These fields were previously available to stores with the Avalara AvaTax 1.0 integration enabled, which was deprecated in April 2025. Use the GraphQL Admin API to access order line item pricing data. | https://shopify.dev/changelog/removal-of-pretaxprice-from-the-order-rest-admin-api - [shopify-1252c53b5b] - | Process refunds only through the original payment processor – Requirement update | breaking_change | published 2026-03-20 | We've updated requirement 1.1.15 for Shopify App Store apps. Apps must now process refunds only through the original payment processor. Previously, apps were prohibited from offering methods for processing refunds outside of the original payment processor. | https://shopify.dev/changelog/process-refunds-only-through-the-original-payment-processor-requirement-update - [shopify-a37de94642] - | New payment decline codes added to `OrderTransactionErrorCode` enum | breaking_change | published 2026-03-16 | We're adding new error codes to the OrderTransactionErrorCode enum to provide more granular detail about the transaction failure. You can use this more detailed response to improve customer interactions. These error codes enable precise identification of transaction issues: | Error Code | Description | | | https://shopify.dev/changelog/new-payment-decline-codes-added-to-ordertransactionerrorcode-enum - [shopify-3a85678499] - | ShopifyQL returns fields deprecated and replaced with sales reversals fields | breaking_change, deprecation | published 2026-03-14 | In GraphQL Admin API version 2026-04 , several Returns fields in analytics, which can be queried through ShopifyQL , have been deprecated and replaced with renamed versions (e.g., sales_reversals , reversed_quantity ) to better reflect that they capture all order adjustments, including refunds, returns, order edits,… | https://shopify.dev/changelog/shopifyql-returns-fields-deprecated-and-replaced-with-sales-reversals-fields - [shopify-af6b07f81e] - | `inventorySetScheduledChanges` mutation is being removed with no replacement | breaking_change, deprecation, policy | published 2026-03-09 | The inventorySetScheduledChanges mutation will be removed from the GraphQL Admin API in version 2026-07 . This mutation has no replacement, so any apps currently using it should stop relying on it to avoid disruptions. | https://shopify.dev/changelog/inventorysetscheduledchanges-mutation-is-being-removed-with-no-replacement - [shopify-4abff14312] - | Removed Checkout ID from checkout and order webhooks | breaking_change, deprecation | published 2026-03-06 | To simplify and standardize our checkout references, Shopify has removed the following fields from checkout and orders webhooks. Merchants and partners should update their webhook handlers to use the token or checkout_token fields going forward. | https://shopify.dev/changelog/removed-checkout-id-from-checkouts-and-orders-webhooks - [shopify-7d50dd91de] - | Legacy customer accounts are now deprecated | api_version_sunset, deprecation | published 2026-02-26 | Legacy customer accounts are no longer available to new stores and existing stores not using it. Shopify will stop providing feature updates and technical support for this older version. A final sunset date for legacy customer accounts will be announced later in 2026. | https://shopify.dev/changelog/legacy-customer-accounts-are-deprecated - [shopify-f11a5a1e71] - | New APIs to read and write shipping options in delivery profile | deprecation, breaking_change | published 2026-02-24 | As part of the enhanced UI for creating shipping options, a shipping option can now include multiple tiered rates grouped together. | https://shopify.dev/changelog/new-apis-to-read-and-write-shipping-options-in-delivery-profile - [shopify-574a393754] - | JSON metafield values limited to 128KB | breaking_change | published 2026-02-19 | When using API version 2026-04 or later, JSON type metafield writes will be limited to 128KB. Limits for all other metafield types remain unchanged ( current limits ). All apps that use JSON fields (prior to April 1st, 2026), will be grandfathered at the current 2MB limit. | https://shopify.dev/changelog/reduced-metafield-value-sizes - [shopify-45a42d2294] - | Ensuring POS UI extension stability by hardening callback handling | breaking_change | published 2026-01-27 | Starting with POS 10.19.0 , unhandled errors in extension callbacks trigger an error page instead of failing silently. This change ensures a more stable and predictable experience for merchants and helps developers identify issues proactively. | https://shopify.dev/changelog/ensuring-pos-ui-extension-stability-by-hardening-callback-handling - [shopify-6ac025e315] - | Events data now limited to one year retention | deprecation, policy | published 2026-01-27 | Access to events data older than one year is no longer available via the Admin GraphQL Event interface or the Admin REST events resource . This update is part of our ongoing efforts to optimize data management and improve system performance. Please review and update any dependencies on these events. | https://shopify.dev/changelog/events-data-now-limited-to-one-year-retention - [shopify-7bf70ca963] - | Shop Minis development now requires Partner account permissions | breaking_change | published 2026-01-17 | The Shop Minis CLI has been updated to ensure only authorized team members can create and manage Shop Minis. This is done by verifying the necessary permissions within your Partner organization. To develop Shop Minis, you must now have the Manage apps permission enabled on your Partner account. | https://shopify.dev/changelog/shop-minis-development-now-requires-partner-account-permissions - [shopify-c34f45a48b] - | Standardization of Asset URL Version Parameters | breaking_change, format_change | published 2026-01-12 | We're updating the format of versioning query parameters appended to store assets such as CSS and JS. Previously, some assets used a bare numeric query parameter, (for example, ?108 ), while others used a key-value format with the v query parameter. | https://shopify.dev/changelog/standardization-of-asset-url-version-parameters - [shopify-790d6b8a91] - | Deprecated `deliveryShippingOriginAssign` mutation | deprecation | published 2026-01-08 | Support for legacy mode profiles in shipping has been discontinued, as this feature has been inactive for some time. Consequently, the GraphQL Admin API is being updated to align with this change. | https://shopify.dev/changelog/deprecate-deliveryshippingoriginassign-mutation - [shopify-005a6e49ad] 2026-01-01 | Deprecation of the checkout_and_accounts_configurations/update webhook | deprecation, breaking_change, tracking_signal | published 2025-08-12 | The checkout_and_accounts_configurations/update webhook, originally introduced in API version 2025-04 to help track updates to checkout and accounts configurations, will be removed on January 1, 2026. | https://shopify.dev/changelog/deprecation-of-checkoutandaccountsconfigurationsupdate-webhook - [shopify-3dd5147724] 2026-01-01 | _shopify_y and _shopify_s cookies will no longer be set | deprecation, breaking_change, tracking_signal | published 2025-08-04 | Starting on January 1st, 2026 Shopify will no longer set the following cookies on merchant storefronts: _shopify_s _shopify_y While accessing internal cookie values is never recommended as they frequently change, any code that currently accesses the cookie values will need to be adapted to use documented APIs. | https://shopify.dev/changelog/shopifyy-and-shopifys-cookies-will-no-longer-be-set - [shopify-0ede6b2c7e] 2026-01-01 | Deprecation Notice: CalculatedOrder for committed order edits | breaking_change, deprecation | published 2024-12-12 | We are deprecating the CalculatedOrder object for committed order edits. There are no changes to CalculatedOrder for uncommitted order edits. CalculatedOrders are temporary objects that represent an order's state with unsaved edits. Use the Order object to access the current state of an order after edits are committed. | https://shopify.dev/changelog/deprecation-notice-calculatedorder-for-committed-order-edits - [shopify-016909058c] - | Deprecation of `Shop.billingAddress` in favor of `Shop.shopAddress` | deprecation, breaking_change | published 2025-12-22 | As of API version 2026-01, the shopAddress field will be introduced to the Shop object in the GraphQL Admin API. This new field replaces the now-deprecated billingAddress field, which will be removed in a future version. shopAddress will have identical structure and values as billingAddress . | https://shopify.dev/changelog/deprecation-of-shop-billingaddress-in-favor-of-shop-shopaddress - [shopify-b157d84221] - | Removing `permitsSkuSharing` field from fulfillment service | breaking_change, deprecation, policy | published 2025-12-19 | As of API version 2026-04, we've removed the permitsSkuSharing field from the FulfillmentService object and from the fulfillmentServiceCreate and fulfillmentServiceUpdate mutations. SKU sharing will be enabled by default for all fulfillment services. | https://shopify.dev/changelog/removing-permitsskusharing-field-from-fulfillment-service - [shopify-d1d0a581cb] - | Customer marketing URL fields now require write access | deprecation, breaking_change, tracking_signal, policy | published 2025-12-18 | Effective immediately : The following customer-related fields now require the write_customers scope and the create_and_edit_customers permission: Customer.emailOpenTrackingUrl (deprecated) Customer.unsubscribeUrl (deprecated) CustomerEmailAddress.openTrackingUrl CustomerEmailAddress.marketingUnsubscribeUrl… | https://shopify.dev/changelog/customer-marketing-url-fields-now-require-write-access - [shopify-dd9eaf2126] - | Venmo and PayPal are now treated as separate payment methods | breaking_change, format_change | published 2025-12-15 | Starting in API version 2026-01 , Venmo and PayPal are treated as separate payment methods when using payment customization functions. Previously, hiding PayPal's express checkout placement would automatically hide Venmo as well. | https://shopify.dev/changelog/venmo-and-paypal-are-now-treated-as-separate-payment-methods - [shopify-3fcfd895bd] - | Deprecation of `OrderTransaction.authorizationCode` in favor of `OrderTransaction.paymentId` | deprecation, tracking_signal, format_change | published 2025-12-12 | Starting with the 2026-01 API version, the authorizationCode field on the OrderTransaction object is deprecated. We recommend using the paymentId field instead. The paymentId field provides a consistent, standardized identifier for payment reconciliation across all payment providers on Shopify. | https://shopify.dev/changelog/deprecation-of-ordertransaction-authorizationcode-in-favor-of-ordertransactionpaymentid - [shopify-087d36fb43] - | New compare and swap syntax for the `inventorySetQuantities` mutation | deprecation, breaking_change | published 2025-12-12 | This changelog is relates to concurrency protection features . We're making the changeFromQuantity field introduced in 2026-01 mandatory and removing the compareQuantity and ignoreCompareQuantity fields for the inventorySetQuantities mutation. This is a breaking change. | https://shopify.dev/changelog/finalizing-compare-and-swap-redesign-for-inventory-set-quantities - [shopify-480e9660c2] - | Concurrency protection features for inventory and refund mutations | deprecation, breaking_change | published 2025-12-12 | This changelog consolidates all updates related to concurrency protection features for inventory and refund mutations. | https://shopify.dev/changelog/concurrency-protection-features - [shopify-fa124c0953] - | Making `changeFromQuantity` field required (with explicit opt-out) | breaking_change | published 2025-12-12 | This changelog relates to concurrency protection features . | https://shopify.dev/changelog/making-changefromquantity-field-required - [shopify-9ede8ec178] - | Making idempotency mandatory for inventory adjustments and refund mutations | breaking_change | published 2025-12-12 | This changelog relates to concurrency protection features . | https://shopify.dev/changelog/making-idempotency-mandatory-for-inventory-adjustments-and-refund-mutations - [shopify-1e8999fcf6] - | Improved compare and swap inventory updates for the `inventorySetQuantities` mutation | deprecation, breaking_change | published 2025-12-12 | This changelog relates to concurrency protection features . We've enhanced the compare-and-swap functionality in the inventorySetQuantities mutation to make concurrent inventory updates more intuitive. | https://shopify.dev/changelog/compare-and-swap-redesign-for-inventory-set-quantities - [shopify-016f514694] 2025-12-10 | Protected customer data scopes required for web pixel PII access starting on December 10th | breaking_change, tracking_signal, policy | published 2025-11-10 | We will be enforcing Shopify's protected customer data policy for all web pixel extensions starting on December 10th, 2025. | https://shopify.dev/changelog/protected-customer-data-scopes-required - [shopify-45cab52806] - | InventoryItem.variant field deprecated in favor of InventoryItem.variants connection | deprecation | published 2025-12-02 | The InventoryItem.variant field has been deprecated and will be removed in a future API version. Use the new InventoryItem.variants connection instead. To learn more, see InventoryItem object or inventoryItem query in the GraphQL Admin API reference. | https://shopify.dev/changelog/inventory-item-variant-field-deprecation - [shopify-78ff47c891] - | Tax summary webhook `created_at` field now returns UTC timezone | breaking_change, format_change | published 2025-11-20 | The created_at field from tax_summaries/create webhook for tax partners will now return timestamps in UTC format with the Z suffix, including millisecond precision. Update your parsing logic to handle the new format. | https://shopify.dev/changelog/tax-summary-webhook-created-at-field-now-returns-utc-timezone - [shopify-61516772a2] - | The `cartDiscountCodeUpdate` mutation now requires the `discountCodes` field | breaking_change | published 2025-10-30 | As part of the GraphQL Storefront API 2026-01 release , the cartDiscountCodesUpdate mutation now requires the discountCodes argument to be included. Previously, mutation calls without the discountCodes argument were allowed, but would not actually modify the cart in any way. | https://shopify.dev/changelog/the-cartdiscountcodeupdate-mutation-now-requires-the-discountcodes-field - [shopify-bbd857fadc] - | Bulk operations group objects default changed to `false` | breaking_change, deprecation, format_change | published 2025-10-29 | We have optimized the output of bulk operations in the GraphQL Admin API to enhance speed and reliability. The groupObjects argument now defaults to false . Grouping objects can slow down operations and increase failure rates, especially with large datasets. The groupObjects argument is now deprecated. | https://shopify.dev/changelog/bulk-operations-group-objects-default-changed-to-false - [shopify-252ca3d986] 2025-10-09 | Your app may be affected by remote products | breaking_change | published 2025-09-20 | Starting October 9, 2025, products displayed on storefronts may originate from a "remote" source, such as another store. This feature is optional and available to a select group of eligible US-based stores. | https://shopify.dev/changelog/your-app-may-be-affected-by-remote-products - [shopify-513857b05f] - | Deprecate delivery legacy modes fields | deprecation | published 2025-10-08 | Support for legacy mode profiles in shipping has been discontinued. This feature has been disabled for a while, and the the GraphQL Admin API is being updated to reflect this. | https://shopify.dev/changelog/deprecate-delivery-legacy-modes-fields - [shopify-9abf1356cc] - | Introducing `functionHandle` for Shopify Functions | deprecation, breaking_change | published 2025-10-01 | As of the 2025-10 API version, we’re introducing support for user-defined handles as the identifier for Shopify Functions in GraphQL mutations. | https://shopify.dev/changelog/introducing-functionhandle - [shopify-4b855c7582] - | Subscription contract shipping requirements now sync with product variants | breaking_change | published 2025-10-01 | We've improved how subscription contracts handle shipping requirements to ensure accurate tax calculations, delivery details, and order totals. These changes apply when using the subscriptionBillingAttemptCreate mutation. | https://shopify.dev/changelog/subscription-contract-shipping-requirements-now-sync-with-product-variants - [shopify-d533bd7e3b] - | Upcoming Markets pricing support for Draft Order checkouts | breaking_change | published 2025-09-30 | Starting from October 31 2025, when a customer updates their shipping address during a Draft Order checkout, product prices may change based on the shop's Markets configuration . | https://shopify.dev/changelog/upcoming-markets-pricing-support-for-draft-order-checkouts - [shopify-cf848ff1e1] - | Removal of deprecated `Shop.draftOrders` connection in the GraphQL Admin API | breaking_change, deprecation | published 2025-09-26 | We are removing the Shop.draftOrders connection, which has already been deprecated for some time. This change is part of our ongoing efforts to streamline and improve the API's efficiency and functionality. | https://shopify.dev/changelog/removal-of-deprecated-shopdraftorders-connection-in-admin-graphql-api - [shopify-8ce4348fed] 2025-09-15 | _tracking_consent, _landing_page, _orig_referrer cookies will no longer be set | deprecation, breaking_change, tracking_signal | published 2025-08-04 | Starting on September 15th, 2025, Shopify will no longer set the following cookies on merchant storefronts: _landing_page _orig_referrer _tracking_consent While accessing internal cookie values is never recommended as they frequently change, any code that currently accesses the cookie values will need to be adapted… | https://shopify.dev/changelog/trackingconsent-landingpage-origreferrer-cookies-will-no-longer-be-set - [shopify-1b5dad1963] - | Upgrade to the latest version of Checkout Kit to avoid issues with iOS 26 | breaking_change | published 2025-09-09 | Checkout Kit’s preloading feature is not compatible with the upcoming release of iOS 26. This incompatibility will prevent buyers from completing their checkout process within the app. | https://shopify.dev/changelog/upgrade-to-the-latest-version-of-checkout-kit-to-avoid-issues-with-ios-26 - [shopify-b95929109b] - | Setting `permitsSkuSharing` argument to `false` when creating a fulfillment service returns an error | breaking_change, deprecation | published 2025-09-05 | With the 2025-10 API version, the permitsSkuSharing argument has been updated for both the fulfillmentServiceCreate mutation and the FulfillmentService#create REST endpoint to return an error if a false value is passed in. | https://shopify.dev/changelog/setting-permitsskusharing-argument-to-false-when-creating-a-fulfillment-service-returns-an-error - [shopify-ac5bc86194] - | Next-Gen developer platform now available to all app developers | breaking_change, deprecation | published 2025-09-03 | What’s new for you: Create developer stores with any plan: Easily create dev stores on any Shopify plan, including Plus, to align with your target environments. Build and test without deploying: Instantly iterate on your app using the new app dev preview. Deploy only when you're ready. | https://shopify.dev/changelog/next-gen-dev-platform-ga - [shopify-8f0cd8c807] - | CollectionReorderProducts operation userErrors now includes code field | breaking_change | published 2025-09-01 | Starting with version 2025-10, the userErrors GraphQL type in the GraphQL Admin API's collectionReorderProducts mutation will be updated to CollectionReorderProductsUserError . This new type retains all the fields of the previous type and introduces an additional code field. | https://shopify.dev/changelog/collectionreorderproducts-operation-usererrors-now-includes-code-field - [shopify-d8061889d9] - | Introducing the new `context` field to specify discount eligibility | breaking_change, deprecation | published 2025-08-18 | As of API version 2025-10, you can use context to specify whether code or automatic discounts are eligible for all customers, specific customers, or customer segments. Specifying customer eligibility is a new feature for automatic discounts. | https://shopify.dev/changelog/discount-eligibility-management - [shopify-f91c64da1b] 2025-08-18 | The `_ab` cookie will no longer be set | deprecation, tracking_signal | published 2025-07-12 | Starting on August 18th, 2025, Shopify will no longer set the _ab cookie on merchant storefronts or checkout. This cookie was used to enable/disable the preview bar. You can hide the preview bar while previewing a theme by adding the pb=0 parameter to the URL. | https://shopify.dev/changelog/the-ab-cookie-will-no-longer-be-set - [shopify-a60631b8eb] 2025-08-15 | The `_shopify_country` cookie will no longer be set | deprecation, breaking_change, tracking_signal | published 2025-06-16 | Starting on August 15th, 2025, Shopify will no longer set the _shopify_country cookie on merchant storefronts or checkout. Developers looking to establish the customer's location can use the Customer Privacy API's getRegion method , which will be more reliable than the cookie now being removed. | https://shopify.dev/changelog/shopifycountry-cookie-no-longer-set - [shopify-3913d6e3e7] - | The `cartDeliveryAddressesUpdate` mutation now supports removing all addresses from a cart | deprecation, breaking_change, policy | published 2025-08-08 | To clear all delivery addresses associated with a cart, you can now call the cartDeliveryAddressesUpdate mutation and set addresses to an empty array( [] ). Previously, to clear a cart’s addresses, you could call the cartBuyerIdentityUpdate mutation and set buyerIdentity.deliveryAddressPreferences to an empty array. | https://shopify.dev/changelog/the-cartdeliveryaddressesupdate-mutation-now-supports-removing-all-addresses-from-a-cart - [shopify-0d086a53a5] 2025-08-01 | Deprecation of POST requests without a Content-Length or Transfer-Encoding: chunked header | deprecation, breaking_change, policy | published 2025-06-28 | We're making changes to our HTTP/1.0 and HTTP/1.1 request handling to improve security and compliance with web standards. Starting August 1, 2025, all POST requests to Shopify APIs must include either a Content-Length header or Transfer-Encoding: chunked header, or they'll return an HTTP 411 error. | https://shopify.dev/changelog/deprecation-of-post-requests-without-a-content-length-or-transfer-encoding-chunked-header - [shopify-1bb543cd58] 2025-08-01 | Buy Button JS must be upgraded to the latest version | deprecation, breaking_change | published 2025-06-27 | Last year, we announced the deprecation of the Checkout APIs , which Buy Button JS is dependent on. As part of this deprecation, checkout functionality will stop working on older versions of Buy Button JS on August 1, 2025 11:00 AM ET. | https://shopify.dev/changelog/buy-button-js-must-be-upgraded-to-the-latest-version - [shopify-5f3237b6b2] - | Deprecation of the `ProductVariant.taxCode` field | deprecation, breaking_change, policy | published 2025-07-30 | As of Admin GraphQL API version 2025-10 , we are deprecating the taxCode field from the ProductVariant object. This change is part of the Avalara AvaTax app deprecation and will affect how you handle tax classification for product variants. | https://shopify.dev/changelog/deprecation-of-tax-code-field - [shopify-3258be7f83] - | Sunsetting Flex sections developer preview | api_version_sunset, deprecation | published 2025-07-14 | We've closed the Flex sections developer preview as of July 14th. This preview included theme blocks and style settings. Theme blocks are now available to all theme developers. You can start using theme blocks immediately to create reusable modules for structuring content within sections. | https://shopify.dev/changelog/sunsetting-flex-sections-developer-preview - [shopify-f5d63eef52] 2025-07-03 | POS UI Extensions 2025-07 update | deprecation, breaking_change | published 2025-07-03 | As of July 3, 2025, we've made the following updates to POS UI Extensions: We've removed the deprecated FormattedTextField component. Update your code to use TextField instead. FormattedTextField still works in POS 10.6.0, but will no longer function in POS 10.7.0. | https://shopify.dev/changelog/pos-ui-extensions-2025-07-update - [shopify-409414bc41] - | Changes to Cart token format for AJAX and Storefront GraphQL Cart APIs | breaking_change, format_change | published 2025-07-02 | Cart tokens will now be returned with a new format for both the AJAX and Storefront GraphQL Cart APIs. API features and functionality remain unchanged. Apps and themes should be designed to handle cart tokens in any format and of any length. Treat the cart token as a random identifier that will change in the future. | https://shopify.dev/changelog/changes-to-cart-token-format-for-ajax-and-storefront-graphql-cart-apis - [shopify-5f39f0c3bd] 2025-07-01 | New Built for Shopify requirements for marketing apps – Effective July 1, 2025 | breaking_change, policy | published 2025-07-01 | Starting July 1, 2025, new category-specific requirements apply to marketing apps in the Built for Shopify (BFS) program. | https://shopify.dev/changelog/new-built-for-shopify-requirements-for-marketing-apps-effective-july-1-2025 - [shopify-932825f6ca] - | Order cancellation now supports refunds to store credit | deprecation, breaking_change | published 2025-07-01 | As of GraphQL Admin API version 2025-07 , the orderCancel mutation allows you to issue refunds as store credit, in addition to the original payment methods, when orders are cancelled. | https://shopify.dev/changelog/ordercancel-mutation-now-supports-refunds-to-store-credit - [shopify-6f482adf5c] - | New field for discount classes on `DraftOrderPlatformDiscount` | breaking_change, deprecation | published 2025-07-01 | The discountClass field in the DraftOrderPlatformDiscount object has been deprecated. Please use the discountClasses field instead, which allows for the representation of multiple discount classes associated with the backing price rule of the DraftOrderPlatformDiscount . | https://shopify.dev/changelog/new-field-for-discount-classes-on-draftorderplatformdiscount - [shopify-7ec70a555b] - | Returns Processing APIs replaces Return Refund APIs | deprecation, breaking_change | published 2025-07-01 | As announced previously , we're introducing important changes to simplify and enhance return management in the Shopify Admin API. The returnRefund mutation is deprecated and replaced by the new returnProcess mutation. | https://shopify.dev/changelog/returns-processing-api - [shopify-2d25de0932] 2025-07-01 | Now available: JS Buy SDK v3.0 | deprecation, breaking_change | published 2025-03-13 | We released the last and final version of JavaScript Buy SDK v3.0 to extend its useful life following the Checkout API deprecation . | https://shopify.dev/changelog/now-available-js-buy-sdk-v30 - [shopify-448c839070] 2025-07-01 | JS Buy SDK Deprecation Notice | deprecation, breaking_change | published 2024-12-03 | The JS Buy SDK is deprecated as of January, 2025. It will no longer be updated or maintained by Shopify past that point. A final major version will be released in early 2025 to remove the SDK's dependency on the deprecated Checkout APIs , replacing them with Cart APIs . | https://shopify.dev/changelog/js-buy-sdk-deprecation-notice - [shopify-7f8dd75f4d] - | Removed tax-related fields from the `ShopFeatures` object | breaking_change, deprecation | published 2025-06-30 | The EligibleForShopifyTaxReporting and ShopifyTaxReportingLegacyAutoTaxMigrated fields have been removed from the ShopFeatures object as it is no longer utilized in Shopify tax reporting. There are no replacements for these fields for external-facing apps. | https://shopify.dev/changelog/removed-tax-related-fields-from-the-shopfeatures-object - [shopify-d89993a950] - | New pagination limits for Liquid & Storefront GraphQL API | breaking_change | published 2025-06-17 | The Liquid and Storefront GraphQL API now limits pagination of arrays of objects to 25,000 items. This affects: For paginated GraphQL queries (using first , last , before , after parameters), queries will now return an error when paginating past the 25,000th item in the array. | https://shopify.dev/changelog/new-pagination-limits-for-liquid-storefront-graphql-api - [shopify-9cc287fad2] - | `productCreate` surfaces input errors as `userErrors` | breaking_change | published 2025-06-14 | Starting from 2025-07, the following productCreate input issues will be surfaced as userErrors : Linking multiple options to the same metafield Linking an option to an already-linked metafield Attempting to specify linkedMetafieldValue for an option that is not linked to a metafield Specifying both options and… | https://shopify.dev/changelog/product-create-serves-input-errors-as-user-errors - [shopify-35d0b5031c] - | Contextual pricing and publishing APIs use backup region fallback | breaking_change | published 2025-06-01 | We're changing the fallback behavior when determining the pricing and publishing that applies to a customer in a specific context. Currently, if a country that doesn't belong to a market is passed as a buyer signal, we use the store defaults. | https://shopify.dev/changelog/contextual-pricing-and-publishing-apis-use-backup-region-fallback - [shopify-e397bf4635] - | Deprecation of legacy return APIs and improvements to return management | deprecation, breaking_change | published 2025-05-21 | We're introducing important changes to simplify and enhance return management in the Shopify Admin API. The returnRefund mutation is deprecated and replaced by the new returnProcess mutation. | https://shopify.dev/changelog/deprecation-of-legacy-return-apis-and-improvements-to-return-management - [shopify-766a83a983] - | Deprecation of Product, Order, and Shipping Discount Function APIs | breaking_change, deprecation | published 2025-05-21 | As of API version 2025-04, the following Function APIs are deprecated: Product Discount Function API Order Discount Function API Shipping Discount Function API These APIs will be removed from all future stable and unstable API versions. | https://shopify.dev/changelog/deprecation-product-order-shipping-discount-function-apis - [shopify-0dd94fd5ea] - | Uncapped counts in GraphQL | breaking_change | published 2025-05-21 | All count APIs in GraphQL now return uncapped results. To retrieve an uncapped count, set the limit argument to null . As part of this update, we've standardized the implementation across all GraphQL APIs. This change introduces a breaking change: all APIs now include a limit argument, with a default value of 10000 . | https://shopify.dev/changelog/uncapped-graphql-counts - [shopify-c4c27c9ca2] - | Public access for app owned metafields and metaobjects is now disabled | deprecation, breaking_change | published 2025-05-19 | In line with last year's announcement regarding metafields access simplification, we are now implementing the removal of PUBLIC access for app-owned metafields and metaobjects. | https://shopify.dev/changelog/public-access-for-app-owned-metafields-and-metaobjects-is-now-disabled - [shopify-2c3cf2e3d9] 2025-05-15 | Updated Shopify Theme Store Requirements and Submission Process – Effective May 15, 2025 | breaking_change | published 2025-05-15 | Starting May 15, 2025, all Shopify themes must meet the updated Theme Store requirements for new submissions and updates. Key changes include: Theme Zip File Structure: New /listings folder is now required in theme zip files. Preset Naming Requirements: Theme name requirements now apply to each preset. | https://shopify.dev/changelog/updated-shopify-theme-store-requirements-and-submission-process-effective-may-15-2025 - [shopify-a0a349080b] - | Deprecating `gates` types and fields across the GraphQL Admin, Storefront, and Functions APIs | breaking_change, api_version_sunset, deprecation | published 2025-05-06 | Shopify is retiring gates types and fields due to limited usage and our commitment to enhancing developer tools with more robust APIs. To ensure your applications continue to function optimally, we recommend transitioning your implementations to metafields and metaobjects. | https://shopify.dev/changelog/gates-api-sunset - [shopify-140d376180] - | The `UnitPriceMeasurementMeasuredUnit` enum now includes imperial units and counts | breaking_change | published 2025-05-02 | In the release candidate for version 2025-07 of the Storefront , GraphQL Admin , and Customer Account API , the UnitPriceMeasurementMeasuredUnit enum now supports values for imperial units and counts. For example: $10/oz or $5/ft $2/item This update enables merchants to display more relevant and transparent pricing. | https://shopify.dev/changelog/unit-pricing-api-update - [shopify-c0f177bd70] - | Deprecation of `draftOrderCreateMerchantCheckout` mutation | deprecation | published 2025-05-01 | As of API version 2025-07, the draftOrderCreateMerchantCheckout mutation has been deprecated. Please use the draftOrderComplete mutation instead. For more information, please visit our help docs . | https://shopify.dev/changelog/deprecation-of-draftordercreatemerchantcheckout-mutation - [shopify-983bfc363f] - | Web Pixels API: `event.data.checkout.subtotalPrice.amount` value change on the new `/thank-you` page and checkout events | breaking_change, tracking_signal | published 2025-04-30 | The event.data.checkout.subtotalPrice.amount value in the Web Pixels API has been updated. Previously, this value included the sum of all line item prices and product-level discounts, but not order-level discounts. | https://shopify.dev/changelog/web-pixels-api-eventdatacheckoutsubtotalpriceamount-value-change-on-the-new-thank-you-page-and-checkout-events - [shopify-7c3f3eec3b] 2025-04-30 | Payment apps can no longer be embedded in the Shopify admin | breaking_change | published 2025-04-16 | As of April 30, 2025, payment apps are no longer eligible to be embedded apps within the Shopify admin. The Payment Apps requirements have been updated to reflect this change. | https://shopify.dev/changelog/payment-apps-can-no-longer-be-embedded-in-the-shopify-admin - [shopify-3171c93483] - | Cash transaction rounding for Point of Sale purchases in selected countries | breaking_change | published 2025-04-24 | For specific currencies, cash transactions on Point of Sale now automatically round to the nearest denomination. | https://shopify.dev/changelog/new-cash-rounding-on-order-and-order-transaction - [shopify-f13de67eb4] - | POS UI Extensions - Cart API: Customer fields removed from `subscribable` hook | deprecation, breaking_change | published 2025-04-22 | The POS UI Extensions Cart API has been updated, removing the email , firstName , lastName , and note Customer fields from the subscribable hook . Any extension used in POS version 10.0.0 or higher, and any extension targeting API version 2025-01 or higher, won't have access to these fields. | https://shopify.dev/changelog/pos-ui-extensions-cart-api-customer-fields-removed-from-subscribable-hook - [shopify-3d777bd215] - | New arguments added to `statusPageUrl` field on the `Order` object | breaking_change, api_version_sunset, policy | published 2025-04-22 | We're enhancing the security of order status URLs by replacing static keys with purpose-specific capability tokens. This change helps protect customer data while giving you more control over URL access patterns. Order status URLs now use dynamically generated capability tokens instead of static key parameters. | https://shopify.dev/changelog/new-arguments-added-to-statuspageurl-field-on-order-object - [shopify-43d6d76c92] - | Change in `productSet` mutation error code for suspended product | breaking_change | published 2025-04-17 | As of the 2025-07 version of the GraphQL Admin API, an attempt to update a suspended product using productSet mutation will now return PRODUCT_SUSPENDED error code instead of INVALID_PRODUCT . For more detailed information and examples, visit our productSet documentation on Shopify.dev. | https://shopify.dev/changelog/change-in-productset-mutation-error-code-for-suspended-product - [shopify-5e3055ac3b] 2025-04-01 | Checkout APIs will be shut down April 1, 2025 | breaking_change, deprecation | published 2025-03-02 | Reminder: The Checkout APIs (Storefront Checkout Mutations and REST Checkout Endpoints) are deprecated and will be shut off on April 1, 2025. Customers will not be able to create or complete checkouts using the deprecated Checkout APIs after the deadline. | https://shopify.dev/changelog/checkout-apis-will-be-shut-down-april-1-2025 - [shopify-2efe216b79] - | FeeSale fee field is nullable as of 2025-07 | breaking_change | published 2025-03-18 | As of 2025-07, the FeeSale.fee field is now nullable, meaning a Fee can be null if it has been deleted. In versions prior to 2025-07, the fee field will still return the deleted fee. For more information, visit the Shopify.dev documentation on FeeSale . | https://shopify.dev/changelog/feesale-fee-field-is-nullable-as-of-2025-07 - [shopify-a4c106acfd] - | Deprecating PriceListUserErrorCode values | breaking_change, deprecation | published 2025-03-17 | Starting in API version 2025-04, PriceListErrorCode values that are currently not returned by the API will be hidden. These error codes include: CATALOG_ASSIGNMENT_NOT_ALLOWED CATALOG_CANNOT_CHANGE_CONTEXT_TYPE APP_CATALOG_PRICE_LIST_ASSIGNMENT CONTEXT_RULE_MARKET_LOCKED | https://shopify.dev/changelog/deprecating-pricelistusererrorcode-values - [shopify-3442db5bd4] - | End of Compatibility for Old POS UI Extensions Versions | breaking_change, api_version_sunset, deprecation, policy | published 2025-03-07 | Shopify's API version policy supports stable versions for 12 months. | https://shopify.dev/changelog/end-of-compatibility-for-old-pos-ui-extensions-versions - [shopify-745707fa17] 2025-02-28 | POS Legacy Extensions Will Be Deprecated in February 2025 | breaking_change, deprecation | published 2024-11-06 | On February 28, 2025, POS Links, POS cart app extensions, and POS product recommendations will be deprecated. Developers and merchants will no longer be able to view or access these extensions in Shopify POS. We recommend you rebuild legacy extensions with POS UI Extensions . | https://shopify.dev/changelog/pos-legacy-extensions-will-be-deprecated-in-february-2025 - [shopify-d6f6cc229c] - | Metafield description input field removal | breaking_change, deprecation | published 2025-02-27 | The description field on metafield is being removed from the MetafieldInput GraphQL input object. The change will appear in unstable and will be included in the 2025-07 API version. The description field is optional and isn't exposed to merchants. You can safely stop including the field in queries and mutations. | https://shopify.dev/changelog/metafield-description-field-removal - [shopify-04de42e501] 2025-02-24 | Explicit access grants for metafields removed | breaking_change, deprecation | published 2025-02-17 | Completing the transition that began with the deprecation of explicit grants , existing explicit grants in the system will stop working on February 24, 2025. | https://shopify.dev/changelog/explicit-access-grants-for-metafields-full-deprecation - [shopify-e90d06c4b9] - | Updated Country Harmonized System Code validations on Product Variant mutations | breaking_change | published 2025-02-14 | Starting with the Admin GraphQL API version 2025-04, all Product Variant mutations will include validations to ensure that any country-specific harmonized system codes provided in the input are compatible with the existing codes on the Inventory Item. | https://shopify.dev/changelog/updated-country-harmonized-system-code-validations-on-product-variant-mutations - [shopify-13bd9ee023] - | Removing unnecessary `RELEVANCE` sort options | breaking_change, deprecation | published 2025-02-01 | RELEVANCE will no longer be included in connection sort options by default as of 2025-04 API versions. This will eliminate cases where the option offered no unique behavior, and acted as a basic ID sort. Legitimate cases where this option provides unique capabilities and services regular traffic will not change. | https://shopify.dev/changelog/removing-unnecessary-relevance-sort-options - [shopify-76080692d7] - | New Catalog APIs | deprecation, breaking_change | published 2025-01-29 | As of April 2025, the Catalog APIs have been updated to support changes in how markets are managed. For more details, see the New Markets APIs . With these updates, multiple markets can now be assigned to a single catalog. | https://shopify.dev/changelog/new-catalog-apis - [shopify-6939fb4156] - | Payout statuses In Transit and Scheduled have been merged | deprecation, tracking_signal | published 2025-01-29 | We’ve made a significant update to the payout statuses in our system. As part of our ongoing efforts to streamline and enhance your experience, we have merged the payout statuses "In Transit" and "Scheduled" into a single status: Scheduled . | https://shopify.dev/changelog/payout-statuses-in-transit-and-scheduled-have-been-merged - [shopify-896ae2bfbc] - | Continuous cart authentication | breaking_change, deprecation, policy | published 2025-01-16 | We’ve recently rolled out a change that enables continuous authentication when a customerAccessToken is appended to the cart in the buyerIdentity object. The obtained checkoutUrl allows authenticated customers to navigate to a logged-in checkout experience. | https://shopify.dev/changelog/continuous-cart-authentication - [shopify-5e100b76d0] - | New Buyer Consent Requirement | breaking_change, tracking_signal | published 2025-01-16 | As of Tuesday, February 18, 2025, all published apps must display costs and obtain explicit buyer consent before adding any optional paid items to Storefront, Cart, or Checkout. These requirements are already being enforced on unpublished apps. | https://shopify.dev/changelog/new-buyer-consent-requirement - [shopify-4a1a0cd0c4] 2025-01-06 | Public apps must use new GraphQL Product APIs to be accepted in the Shopify App Store | deprecation, breaking_change | published 2025-01-01 | Starting January 6, 2025, all new apps submitted to the Shopify App Store must use the new GraphQL Product APIs . After this date, apps that query deprecated REST API product resources won’t be approved. As of February 1, 2025, all public apps must migrate to the new GraphQL Product APIs . | https://shopify.dev/changelog/public-apps-must-use-new-graphql-product-apis-to-be-accepted-in-the-shopify-app-store - [shopify-6a1aa7e79a] 2025-01-06 | Updated requirement: Draft apps must not make calls to APIs that will be deprecated in 90 days or less | deprecation, breaking_change, policy | published 2024-12-19 | Starting January 6, 2025, draft apps that make calls to APIs that will be deprecated in 90 days or less will not be able to submit their apps for review. This is an updated requirement. Be sure to check your API Health report in your Partner Dashboard to ensure your app is querying supported APIs. | https://shopify.dev/changelog/updated-requirement-draft-apps-must-not-make-calls-to-apis-that-will-be-deprecated-in-90-days-or-less - [shopify-4739b31659] 2025-01-06 | Session tokens and app listings automatically checked before submitting for app review | deprecation, breaking_change, policy | published 2024-12-17 | Starting January 6, 2025, we are introducing additional preliminary steps in the app review process. | https://shopify.dev/changelog/session-tokens-and-app-listings-automatically-checked-before-submitting-for-app-review - [shopify-eb7c4b584d] - | New Markets APIs | deprecation, breaking_change | published 2025-01-03 | As of 2025-04 , the Markets APIs have been updated to support additional customizations and conditions for each market, enabling merchants to tailor their shops' buyer experiences. | https://shopify.dev/changelog/new-markets-apis - [shopify-d29b0ee621] 2025-01-03 | Changes to our Font Library | deprecation, breaking_change | published 2024-11-12 | As part of a move towards open-source fonts, and in an effort to refine our font offerings, we have deprecated some fonts in our library. We’re also expanding the library of open-source fonts, with 32 new high quality typefaces available today. | https://shopify.dev/changelog/changes-to-our-font-library - [shopify-024d261d26] - | Unused PriceListUserErrorCode values removed | breaking_change, deprecation | published 2025-01-01 | Starting in API version 2025-01, PriceListErrorCode values that are currently not returned by the API will be hidden. | https://shopify.dev/changelog/unused-pricelistusererrorcode-values-removed - [shopify-88f04c5cc1] - | Deprecation of `storefrontCustomerAccessTokenCreate` Mutation | deprecation | published 2025-01-01 | As of API version 2025-01 , the storefrontCustomerAccessTokenCreate mutation is deprecated. This mutation, which was used to exchange the Customer Access Token in the Authorization header for a Storefront Customer Access Token, is no longer necessary. | https://shopify.dev/changelog/deprecation-of-storefrontcustomeraccesstokencreate-mutation - [shopify-509d462d2b] - | Cart Delivery Address Management | deprecation, breaking_change | published 2025-01-01 | We've refined and improved how delivery addresses are handled by making deliveryAddresses a required input field within a new delivery object. As of API version 2025-01, the deliveryAddressPreferences field on the CartBuyerIdentity object is deprecated. Use the new addresses field on the CartDelivery object instead. | https://shopify.dev/changelog/cart-delivery-address-management - [shopify-5ce0419333] - | Fulfillment Hold Access Update For Node Queries | breaking_change | published 2025-01-01 | As of the Admin API version 2025-01, apps using the node or nodes GraphQL queries to fetch fulfillment holds will only be able to fetch those that belong to a fulfillment order that they have access to. | https://shopify.dev/changelog/fulfillment-hold-access-update-for-node-queries - [shopify-9d3cfd5df3] - | New customer's webhook and changes to existing customer's webhooks payload | breaking_change, deprecation | published 2025-01-01 | As of 2025-01, we're changing how a customer is represented in webhooks: We added the customers/purchasing_summary webhook. We made some changes affecting webhooks containing a customer payload: We removed tags in favour of the customer.tags_added and customer.tags_removed webhooks. | https://shopify.dev/changelog/new-customer-s-webhook-and-changes-to-existing-customer-s-webhooks-payload - [shopify-83c7275d90] - | Change to FulfillmentOrderSortKeys | deprecation | published 2025-01-01 | Starting in API version 2025-01 , RELEVANCE will be removed as a valid value from FulfillmentOrderSortKeys in the GraphQL Admin API. | https://shopify.dev/changelog/change-to-fulfillmentordersortkeys - [shopify-4c5fa534e4] - | Introduce 3DS support for verifications | deprecation, breaking_change, policy | published 2025-01-01 | As of version 2025-01 , payments extensions that support vaulting will now be able to process 3DS challenges for verifications. That is possible through : A new mutation, VerificationSessionRedirect New arguments to the existing VerificationSessionResolve and VerificationSessionReject mutations. | https://shopify.dev/changelog/introduce-3ds-support-for-verifications - [shopify-3ffe0fcb2a] - | Apply multiple holds to a single fulfillment order | breaking_change | published 2025-01-01 | With the introduction of support for placing more than one hold per fulfillment order, you can quickly and easily add another hold each time an issue arises. | https://shopify.dev/changelog/apply-multiple-holds-to-a-single-fulfillment-order - [shopify-98d221ef25] - | Tax and Duties are deprecated in Storefront Cart API | breaking_change, deprecation | published 2025-01-01 | As of API version 2025-01 , we're deprecating the tax and duty fields in Storefront API Cart. Tax and Duties are calculated at Checkout where they can be finalized with the complete context of the buyer's information, ensuring greater accuracy. | https://shopify.dev/changelog/tax-and-duties-are-deprecated-in-storefront-cart-api - [shopify-d741687528] - | New validation against duplicate handles in productCreate, productUpdate, and productSet mutation inputs | breaking_change, deprecation | published 2025-01-01 | As of the 2025-01 version of the Admin GraphQL API, the handle field in productInput for productCreate and productUpdate , as well as in productSetInput for productSet will be validated for uniqueness. This means that you will no longer be able to input a duplicate handle. | https://shopify.dev/changelog/new-validation-against-duplicate-handles-in-productcreate-productupdate-and-productset-mutation-inputs - [shopify-22d1fdd9ae] 2025-01-01 | Updates effective December 30 to our Partner Program Agreement and API License and Terms of Use | breaking_change, policy | published 2024-12-30 | EFFECTIVE DECEMBER 30, 2024 ACTION REQUIRED We've made changes to our Partner Program Agreement and API License and Terms of Use . | https://shopify.dev/changelog/updates-effective-december-30-to-our-partner-program-agreement-and-api-license-and-terms-of-use - [shopify-23d76aec41] 2025-01-01 | Built for Shopify Requirements for embedded apps and apps in marketing categories | breaking_change | published 2024-12-11 | Apps must meet the following criteria to achieve or maintain Built for Shopify status by the specified effective dates: New design requirements – Effective January 1, 2025 We’re introducing new design requirements including: Using tabs for secondary navigation Following UX best practices New category-specific… | https://shopify.dev/changelog/built-for-shopify-requirements-for-embedded-apps-and-apps-in-marketing-categories-effective-july-2025 - [shopify-67e6b0f008] 2025-01-01 | Simplifying how metafield and metaobject permissions work | breaking_change, deprecation | published 2024-12-10 | In the new year we’re simplifying how metafield and metaobject permissions work. This makes the system easier to work with and will further improve API response times. | https://shopify.dev/changelog/simplifying-how-metafield-and-metaobject-permissions-work - [shopify-6bd6862397] - | Deprecate customer_payment_method_remote_credit_card_create | deprecation | published 2024-12-31 | The mutation for CustomerPaymentMethodRemoteCreditCardCreate has been deprecated and is now hidden. This mutation, which was used to create remote credit card payment methods for customers, is no longer supported as of API version 2025-01. | https://shopify.dev/changelog/deprecate-customerpaymentmethodremotecreditcardcreate - [shopify-6a773537fe] - | Deprecated `SubscriptionMailingAddress` in favor of `MailingAddress` | breaking_change, deprecation | published 2024-12-19 | As of the 2025-07 version of the GraphQL Admin API, we've deprecated the SubscriptionMailingAddress object. Use the MailingAddress object instead. | https://shopify.dev/changelog/deprecate-subscriptionmailingaddress-in-favour-of-mailingaddress - [shopify-996523f4b7] - | Removal of deprecated shop fields | breaking_change, deprecation | published 2024-12-18 | As of Admin GraphQL API 2025-01 , some previously deprecated fields have been removed which have replacements: Shop.collectionByHandle → QueryRoot.collectionByHandle Shop.collectionSavedSearches → QueryRoot.collectionSavedSearches Shop.customerSavedSearches → QueryRoot.customerSavedSearches… | https://shopify.dev/changelog/removal-of-unused-deprecated-fields - [shopify-bf3655e92d] - | Changes to ScriptTag displayScope field on Admin GraphQL API | breaking_change, deprecation | published 2024-12-13 | As of Admin GraphQL API version 2025-01, the only valid value for the displayScope field on the ScriptTagInput object is ONLINE_STORE . The displayScope field remains optional when creating and updating Script tags. | https://shopify.dev/changelog/changes-to-scripttag-displayscope-field-on-admin-graphql-api - [shopify-c2daa2b469] - | Product image resource in REST now returns a media image GID to streamline migration to GraphQL | breaking_change, deprecation | published 2024-12-12 | As of 2025-01 , the admin REST API for the product image resource will return a media image GID instead of a product image GID. This is designed to help make it easier to migrate to GraphQL from REST when interfacing with product images that were created before the introduction of a unified media id. | https://shopify.dev/changelog/product-image-resource-in-rest-now-returns-a-media-image-gid-to-streamline-migration-to-graphql - [shopify-886d2b5fb6] - | Admin REST API product image is now deprecated | deprecation | published 2024-12-09 | As of 2025-01 , the admin REST API for the product image resource is now deprecated. It is recommended to migrate to GraphQL and use media IDs going forward. The admin_graphql_api_id will return a media image ID to streamline the migration process. More information and a migration guide can be found in the dev docs . | https://shopify.dev/changelog/admin-rest-api-product-image-is-now-deprecated - [shopify-641c408d0c] 2024-12-05 | App extensions can’t be used for self-promotion or related activities | breaking_change | published 2024-12-05 | Starting December 5, 2024, app extensions, including admin links, checkout extensibility, and theme app extensions can’t be used to advertise your app, promote related apps, or request reviews. | https://shopify.dev/changelog/app-extensions-can-t-be-used-for-self-promotion-or-related-activities - [shopify-cee337efee] - | PrivateMetafield is now deprecated | breaking_change, deprecation | published 2024-12-05 | Starting in API version 2025-01 , PrivateMetafield will be removed from the GraphQL Admin API. Use app-data metafields instead. If the metafield is needed per resource, consider the migration guide for using app-reserved namespaces. | https://shopify.dev/changelog/privatemetafield-is-now-deprecated - [shopify-36edc12d85] - | Conditionally disable gift cards in checkout using custom logic with the Payment Customization API | breaking_change | published 2024-11-12 | As of Nov 12, 2024, you can use the HideOperation in the Payment Customization Function API to disable native gift card functionality and Shopify-integrated third-party gift card systems. | https://shopify.dev/changelog/conditionally-disable-gift-cards-in-checkout-using-custom-logic-with-the-payment-customization-api - [shopify-9496db3a8d] - | Remove `metafieldDelete` in favor of `metafieldsDelete` | breaking_change, deprecation | published 2024-11-05 | As of 2025-01 the metafieldDelete Admin API method is being removed. The metafieldsDelete method should be used instead. The former relies on the Metafield GID, while the latter takes an array of Metafield Identifiers composed of ownerId , namespace , and key . | https://shopify.dev/changelog/remove-metafielddelete-in-favor-of-metafieldsdelete - [shopify-fb3574335a] - | Content type `application/graphql` is deprecated | deprecation, breaking_change, format_change | published 2024-11-01 | The Content-Type: application/graphql request format is deprecated and will no longer be accepted as of 2025-01 schema versions. As of 2025-01 schemas, all requests must specify Content-Type: application/json and post a spec encoded body . See GraphQL Over HTTP update for more details. | https://shopify.dev/changelog/content-type-application-graphql-is-deprecated - [shopify-92544c3aca] - | Removing `multiLocation` field from `ShopFeatures` | breaking_change, deprecation | published 2024-11-01 | As of the 2025-01 release of the Admin GraphQL API, the deprecated multiLocation field on ShopFeatures will be removed. Use the locationsCount query to determine how many locations a shop has. | https://shopify.dev/changelog/removing-multilocation-field-from-shopfeatures - [shopify-29bb895184] - | Change to metafield type handling in liquid | breaking_change, deprecation | published 2024-10-28 | Effectively immediately, metafields without a type value will return "string" instead of blank . | https://shopify.dev/changelog/change-to-metafield-type-handling-in-liquid - [shopify-a0a2c33376] - | Updates to Theme Information Access in Shopify | deprecation, breaking_change | published 2024-10-28 | Action Required: Developers currently using the BOOMR variables for theme identification and customization should begin transitioning to window.Shopify.theme properties. | https://shopify.dev/changelog/updates-to-theme-information-access-in-shopify - [shopify-89b93cb597] - | Breaking Changes to CAPTCHA protection on Storefront forms | deprecation, breaking_change | published 2024-10-28 | From the week commencing 28th October 2024, the following changes to CAPTCHA protection will occur: Legacy Customer Accounts: Removal of the /challenge page for Login, Create Account and Reset Password flows If hCaptcha is enabled in Admin for these forms, they will now require a valid hCaptcha token as part of the… | https://shopify.dev/changelog/breaking-changes-to-captcha-protection-on-storefront-forms - [shopify-7ecffb1a32] - | Update to `fulfillmentHold.heldByApp` field from `fulfillmentHold.heldBy` field | breaking_change, deprecation | published 2024-10-24 | As of the 2025-01 API version, the heldBy string field on the fulfillmentHold GraphQL object will be replaced by the newly introduced heldByApp object field. This new field provides access to all attributes of the App object , unlike the deprecated heldBy field, which only indicated the app's title. | https://shopify.dev/changelog/update-to-fulfillmenthold-heldbyapp-field-from-fulfillmenthold-heldby-field ## HubSpot - [hubspot-cb3daa6483] 2026-12-04 | Pipelines API V1 Sunset: December 4, 2026 | api_version_sunset, deprecation | published 2026-08-14 | HubSpot will sunset the Pipelines API V1 on December 4, 2026 . After this date, the API will no longer be supported. If your integration relies on V1 endpoints, you'll need to migrate to the 2026-03 or newer version before the deadline to avoid disruption. | https://developers.hubspot.com/changelog/pipelines-api-v1-sunset - [hubspot-32d44c2df3] - | Upcoming Automatic Update: HubSpot domain security settings will move to TLS 1.2 | policy | published 2026-10-06 | On October 14th, HubSpot will automatically update the minimum TLS version for your HubSpot-hosted domains from TLS 1.0 or 1.1 to TLS 1.2. | https://developers.hubspot.com/changelog/upcoming-automatic-update-hubspot-domain-security-settings-to-tls-1.2 - [hubspot-67237bed79] - | Legacy APIs and Apps: What's Going Unsupported and When | api_version_sunset, deprecation, breaking_change | published 2026-09-15 | At Fall Spotlight on September 15, HubSpot is announcing the end of support for v1-v3 APIs, legacy public apps, and legacy private apps, all with a September 2027 enforcement date. If your integration or app uses any of these, you have a 12-month window to migrate. This changelog covers v1-v3. | https://developers.hubspot.com/changelog/legacy-apis-and-legacy-apps-whats-going-unsupported-and-when - [hubspot-d7a7c65c7e] - | Fall 2026 Spotlight - Developer / Builder Updates | api_version_sunset, deprecation, breaking_change | published 2026-09-15 | This changelog rounds up the developer and builder updates in HubSpot's Fall Spotlight 2026 release: what's now generally available on Developer Platform version 2026.09, the new and updated APIs , the APIs entering public beta , and the latest AI builder tools . | https://developers.hubspot.com/changelog/fall-2026-spotlight - [hubspot-ca8e3356b8] 2026-09-08 | Breaking Change: CRM API Write Validation Enforcement Starting with the 2026-09 API Version | breaking_change | published 2026-08-11 | Starting with the /2026-09/ API version shipping on September 8, 2026, HubSpot will enforce admin-configured validation rules on all CRM API write paths. If your integration creates or updates CRM records, please make sure that it conforms to the below changes before updating your version of the API. | https://developers.hubspot.com/changelog/crm-api-write-validation-enforcement - [hubspot-385c32d65c] 2026-08-31 | Node 18.x and 20.x Runtimes Deprecated for Chatflow Custom Code Snippets | deprecation | published 2026-08-12 | Node 18.x and 20.x are being deprecated as supported runtimes for Chatflows custom code snippets . If you have bot code snippets running on either of these versions, you need to upgrade them to Node 24.x before August 31st, 2026 , or you will lose the ability to edit those snippets until the upgrade is completed. | https://developers.hubspot.com/changelog/node18-20-chatflow-deprecation - [hubspot-e2297e03bb] - | August 2026 Rollup | announcement | published 2026-08-27 | August’s developer updates expand how teams bring data into HubSpot and automate CRM operations. This month introduces webhook data sources for Data Studio, preserves active workflow enrollments when records are merged, and adds app object support to association workflow actions. | https://developers.hubspot.com/changelog/august-2026-rollup - [hubspot-127d583d15] - | Legacy Private App Creation Being Disabled | api_version_sunset, deprecation | published 2026-08-27 | HubSpot is permanently removing the ability to create new legacy, non-Project based, private apps through the account UI. Users needing similar functionality should use Service Keys, available via Developer Platform Projects version 2026.09 or later, which supports system-to-system integrations. | https://developers.hubspot.com/changelog/legacy-private-app-creation-sunset - [hubspot-529926edc3] - | July 2026 Rollup | announcement | published 2026-07-31 | This month's updates include a raised owner property limit, larger Webhooks Journal batch sizes, and a new historical API usage chart — plus public betas for Contract Imports and the Payment Links API. Read on for the details. | https://developers.hubspot.com/changelog/july-2026-rollup - [hubspot-e7a770d5ad] - | Breaking Change: Pipeline and pipeline stage delete endpoints will validate references by default starting with the 2026-09 API version | breaking_change | published 2026-07-21 | 7/23/2026 Edit - The post has been updated to include the Deal object specific validateDealStageUsagesBeforeDelete query parameter. Availability: This is a breaking change for the next GA date-based API version, /2026-09/. It does not change the behavior of the current GA API version or earlier versions. | https://developers.hubspot.com/changelog/pipeline-stage-validation-true ## Salesforce - [salesforce-3e54362c25] 2028-06 | Salesforce retirement: Salesforce Platform API Versions 31.0 through 40.0 (Summer '28 - June 2028) | api_version_sunset | published n/a | Salesforce lists "Salesforce Platform API Versions 31.0 through 40.0" on its Active Product & Feature Retirements page with timing: Summer '28 - June 2028. | https://help.salesforce.com/s/articleView?id=005321531&type=1&language=en_US - [salesforce-6486e2a52f] 2028-05-01 | Salesforce retirement: Vlocity Public Sector Managed Package (May 1, 2028) | deprecation | published n/a | Salesforce lists "Vlocity Public Sector Managed Package" on its Active Product & Feature Retirements page with timing: May 1, 2028. | https://help.salesforce.com/s/articleView?id=005384463&type=1&language=en_US - [salesforce-9fe74cd1d2] 2028-02 | Salesforce retirement: Open CTI (Spring '28 - February 2028) | deprecation | published n/a | Salesforce lists "Open CTI" on its Active Product & Feature Retirements page with timing: Spring '28 - February 2028. | https://help.salesforce.com/s/articleView?id=005317712&type=1&language=en_US - [salesforce-ed27f3cb6b] 2027-06 | Salesforce retirement: SOAP API login() (Summer '27 - June 2027) | api_version_sunset | published n/a | Salesforce lists "SOAP API login()" on its Active Product & Feature Retirements page with timing: Summer '27 - June 2027. | https://help.salesforce.com/s/articleView?language=en_US&id=005132110&type=1 - [salesforce-19d624ed01] 2027-04-01 | Salesforce retirement: Einstein Relationship Insights (April 1, 2027) | deprecation | published n/a | Salesforce lists "Einstein Relationship Insights" on its Active Product & Feature Retirements page with timing: April 1, 2027. | https://help.salesforce.com/s/articleView?id=005385568&type=1&language=en_US - [salesforce-76ded56eff] 2027-04-01 | Salesforce retirement: Lightning Sync (April 1, 2027) | deprecation | published n/a | Salesforce lists "Lightning Sync" on its Active Product & Feature Retirements page with timing: April 1, 2027. | https://help.salesforce.com/s/articleView?id=005321528&type=1&language=en_US - [salesforce-cbf6080a45] 2027-02 | Salesforce retirement: EAC Activity Metrics, Dashboard, Recommended Connections and A360 Reports (Spring '27 - Feb 2027) | deprecation | published n/a | Salesforce lists "EAC Activity Metrics, Dashboard, Recommended Connections and A360 Reports" on its Active Product & Feature Retirements page with timing: Spring '27 - Feb 2027. | https://help.salesforce.com/s/articleView?id=005384640&type=1&language=en_US - [salesforce-fad6492a77] 2027-02 | Salesforce retirement: Salesforce-to-Salesforce (Spring '27 - Feb 2027) | deprecation | published n/a | Salesforce lists "Salesforce-to-Salesforce" on its Active Product & Feature Retirements page with timing: Spring '27 - Feb 2027. | https://help.salesforce.com/s/articleView?id=005103355&type=1&language=en_US - [salesforce-0da1bbb931] 2027-01-30 | Salesforce retirement: Salesforce for Outlook (January 30, 2027) | deprecation | published n/a | Salesforce lists "Salesforce for Outlook" on its Active Product & Feature Retirements page with timing: January 30, 2027. | https://help.salesforce.com/s/articleView?id=000353024&language=en_US&type=1&mode=1 - [salesforce-071936ef8e] 2026-12-31 | Salesforce retirement: Data Mask Managed Package End of Support (December 31, 2026) | deprecation | published n/a | Salesforce lists "Data Mask Managed Package End of Support" on its Active Product & Feature Retirements page with timing: December 31, 2026. | https://help.salesforce.com/s/articleView?id=005299299&type=1&language=en_US - [salesforce-9749b01f80] 2026-12-15 | Salesforce retirement: Standard-Volume Platform Events (December 15, 2026) | deprecation | published n/a | Salesforce lists "Standard-Volume Platform Events" on its Active Product & Feature Retirements page with timing: December 15, 2026. | https://help.salesforce.com/s/articleView?id=002280033&type=1&language=en_US - [salesforce-24ef1660c2] 2026-10-04 | Salesforce retirement: Marketing Cloud Engagement (MCE) User Domain (October 4, 2026) | deprecation | published n/a | Salesforce lists "Marketing Cloud Engagement (MCE) User Domain" on its Active Product & Feature Retirements page with timing: October 4, 2026. | https://help.salesforce.com/s/articleView?id=005321533&type=1&language=en_US - [salesforce-14908380d8] 2026-08-31 | Salesforce retirement: Maps Mobile App (August 31, 2026) | deprecation | published n/a | Salesforce lists "Maps Mobile App" on its Past Product & Feature Retirements page with timing: August 31, 2026. | https://help.salesforce.com/s/articleView?id=005314199&type=1&language=en_US - [salesforce-23b69c32bd] 2026-06-01 | Salesforce retirement: Optimizer App (June 1, 2026) | deprecation | published n/a | Salesforce lists "Optimizer App" on its Past Product & Feature Retirements page with timing: June 1, 2026. | https://help.salesforce.com/s/articleView?id=005132112&language=en_US&type=1 - [salesforce-c1ddab93e2] 2026-06 | Salesforce retirement: Standard Omni-Channel (Summer '26 - June 2026) | deprecation | published n/a | Salesforce lists "Standard Omni-Channel" on its Past Product & Feature Retirements page with timing: Summer '26 - June 2026. | https://help.salesforce.com/s/articleView?id=004868010&type=1&language=en_US - [salesforce-e53de8022e] 2026-05-31 | Salesforce retirement: Legacy Agentforce Analytics (May 31, 2026) | deprecation | published n/a | Salesforce lists "Legacy Agentforce Analytics" on its Past Product & Feature Retirements page with timing: May 31, 2026. | https://help.salesforce.com/s/articleView?id=005197695&type=1&language=en_US - [salesforce-22a55d67ee] 2026-03-01 | Salesforce retirement: Classic Knowledge Data Model End of Support (March 1, 2026) | deprecation | published n/a | Salesforce lists "Classic Knowledge Data Model End of Support" on its Past Product & Feature Retirements page with timing: March 1, 2026. | https://help.salesforce.com/s/articleView?id=005239564&type=1&language=en_US - [salesforce-0eb7a49afa] 2026-02-14 | Salesforce retirement: Chat & Live Agent (February 14, 2026) | deprecation | published n/a | Salesforce lists "Chat & Live Agent" on its Past Product & Feature Retirements page with timing: February 14, 2026. | https://help.salesforce.com/s/articleView?id=001790618&type=1&language=en_US - [salesforce-8dd54f800a] 2026-02-02 | Salesforce retirement: Data Detect End of Support (February 2, 2026) | deprecation | published n/a | Salesforce lists "Data Detect End of Support" on its Past Product & Feature Retirements page with timing: February 2, 2026. | https://help.salesforce.com/s/articleView?id=005132108&type=1&language=en_US - [salesforce-46fce91ffa] 2025-12-31 | Salesforce retirement: Article Answers for Einstein Bots (December 31, 2025) | deprecation | published n/a | Salesforce lists "Article Answers for Einstein Bots" on its Past Product & Feature Retirements page with timing: December 31, 2025. | https://help.salesforce.com/s/articleView?id=005134861&type=1&language=en_US - [salesforce-ad19dc71af] 2025-12-31 | Salesforce retirement: Workflow Rules & Process Builder End of Support (December 31, 2025) | deprecation | published n/a | Salesforce lists "Workflow Rules & Process Builder End of Support" on its Past Product & Feature Retirements page with timing: December 31, 2025. | https://help.salesforce.com/s/articleView?id=001096524&type=1&language=en_US - [salesforce-61e58644ba] 2025-09-16 | Salesforce retirement: Tableau Data Connect (September 16, 2025) | deprecation | published n/a | Salesforce lists "Tableau Data Connect" on its Past Product & Feature Retirements page with timing: September 16, 2025. | https://help.salesforce.com/s/articleView?id=005167106&type=1&language=en_US - [salesforce-77553dabf0] 2025-06 | Salesforce retirement: Platform API Versions 21.0 through 30.0 (Summer '25 - June 2025) | api_version_sunset | published n/a | Salesforce lists "Platform API Versions 21.0 through 30.0" on its Past Product & Feature Retirements page with timing: Summer '25 - June 2025. | https://help.salesforce.com/s/articleView?id=000389618&type=1&utm_source=techcomms&utm_medium=email&utm_campaign=eol&language=en_US - [salesforce-7c2fe5dfce] 2025-06 | Salesforce Platform API versions 21.0–30.0 retired (Summer '25) | api_version_sunset | published n/a | These API versions are deprecated (as of Summer ‘22 release), are no longer supported, and retired (as of the Summer '25 release). Applications that consume these versions will be disrupted because calls will fail and respond with an error that the requested endpoint is not found and can’t be processed by the platform. | https://help.salesforce.com/s/articleView?id=000389618&type=1 - [salesforce-186c0df3be] 2024-11-18 | Salesforce retirement: MC Social Studio (November 18, 2024) | deprecation | published n/a | Salesforce lists "MC Social Studio" on its Past Product & Feature Retirements page with timing: November 18, 2024. | https://help.salesforce.com/s/articleView?id=000364458&type=1&language=en_US - [salesforce-ed3de52ced] 2024-11-18 | Salesforce retirement: Social Customer Service and Social Customer Service Starter Pack (November 18, 2024) | deprecation | published n/a | Salesforce lists "Social Customer Service and Social Customer Service Starter Pack" on its Past Product & Feature Retirements page with timing: November 18, 2024. | https://help.salesforce.com/s/articleView?id=000396466&type=1&language=en_US - [salesforce-6120b5690d] 2024-08-01 | Salesforce retirement: Personalization Account Profiles (August 1, 2024) | deprecation | published n/a | Salesforce lists "Personalization Account Profiles" on its Past Product & Feature Retirements page with timing: August 1, 2024. | https://help.salesforce.com/s/articleView?id=001744617&type=1&language=en_US - [salesforce-ad327097ee] 2024-07-01 | Salesforce retirement: Google Analytics 360 Resell (July 1, 2024) | deprecation | published n/a | Salesforce lists "Google Analytics 360 Resell" on its Past Product & Feature Retirements page with timing: July 1, 2024. | https://help.salesforce.com/s/articleView?id=000391055&type=1&language=en_US - [salesforce-e6aadb98af] 2024-02-01 | Salesforce retirement: MC Audience Studio (February 1, 2024) | deprecation | published n/a | Salesforce lists "MC Audience Studio" on its Past Product & Feature Retirements page with timing: February 1, 2024. | https://help.salesforce.com/s/articleView?id=000879892&type=1&language=en_US - [salesforce-f6fac0c0b6] 2024-02-01 | Salesforce retirement: Salesforce Inbox Mobile App (February 1, 2024) | deprecation | published n/a | Salesforce lists "Salesforce Inbox Mobile App" on its Past Product & Feature Retirements page with timing: February 1, 2024. | https://help.salesforce.com/s/articleView?id=000396123&type=1&language=en_US - [salesforce-c9b5995b15] - | Salesforce retirement: Quip (Order End Date) | deprecation | published n/a | Salesforce lists "Quip" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005299603&type=1&language=en_US - [salesforce-40da93edc5] - | Salesforce retirement: OWN Archive (Managed Packaged) (Order End Date) | deprecation | published n/a | Salesforce lists "OWN Archive (Managed Packaged)" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005385570&type=1&language=en_US - [salesforce-cbd5d58e2b] - | Salesforce retirement: Heroku Data Bridge (Order End Date) | deprecation | published n/a | Salesforce lists "Heroku Data Bridge" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?language=en_US&id=005227650&type=1 - [salesforce-589a318042] - | Salesforce retirement: Rebate Management (Order End Date) | deprecation | published n/a | Salesforce lists "Rebate Management" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005393495&type=1&language=en_US - [salesforce-16ccae2251] - | Salesforce retirement: Tableau Cloud Sandbox (Order End Date) | deprecation | published n/a | Salesforce lists "Tableau Cloud Sandbox" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005393494&type=1&language=en_US - [salesforce-0401d955c2] - | Salesforce retirement: Conga Quote and Invoice Generation (Order End Date) | deprecation | published n/a | Salesforce lists "Conga Quote and Invoice Generation" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005317711&type=1&language=en_US - [salesforce-625efe1107] - | Salesforce retirement: Admin Assist (Order End Date) | deprecation | published n/a | Salesforce lists "Admin Assist" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?language=en_US&type=1&id=Admin-Assist-Feature-Retirement - [salesforce-4f4cc7da7e] - | Salesforce retirement: Sales Enablement (Order End Date) | deprecation | published n/a | Salesforce lists "Sales Enablement" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=002475099&type=1&language=en_US - [salesforce-6c153a9083] - | Salesforce retirement: Tableau Server Legacy Products (Order End Date) | deprecation | published n/a | Salesforce lists "Tableau Server Legacy Products" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?language=en_US&id=005317674&type=1 - [salesforce-1eb04961b6] - | Salesforce retirement: Multi-Site Pilot Program (Order End Date) | deprecation | published n/a | Salesforce lists "Multi-Site Pilot Program" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005227648&type=1&language=en_US - [salesforce-d6d0f9200e] - | Salesforce retirement: Einstein Prediction Builder (Order End Date) | deprecation | published n/a | Salesforce lists "Einstein Prediction Builder" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=004980243&type=1&language=en_US - [salesforce-124520dc6d] - | Salesforce retirement: Files Connect for SharePoint On-Premises (Order End Date) | deprecation | published n/a | Salesforce lists "Files Connect for SharePoint On-Premises" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000389071&type=1&language=en_US - [salesforce-cb1ec37b2b] - | Salesforce retirement: Pulse for Salesforce (P4SF) (Order End Date) | deprecation | published n/a | Salesforce lists "Pulse for Salesforce (P4SF)" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005385569&type=1&language=en_US - [salesforce-5fc40e0060] - | Salesforce retirement: Public Sector Foundation (Order End Date) | deprecation | published n/a | Salesforce lists "Public Sector Foundation" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005228500&type=1&language=en_US - [salesforce-aa80697b29] - | Salesforce retirement: Subscription Management (Order End Date) | deprecation | published n/a | Salesforce lists "Subscription Management" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005227649&type=1&language=en_US - [salesforce-8aff446d9f] - | Salesforce retirement: Tableau Support Plan (Order End Date) | deprecation | published n/a | Salesforce lists "Tableau Support Plan" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=002475101&type=1&language=en_US - [salesforce-9dc34f55c4] - | Salesforce retirement: Nonprofit Integration Apps for Marketing Cloud Managed Packages (Order End Date) | deprecation | published n/a | Salesforce lists "Nonprofit Integration Apps for Marketing Cloud Managed Packages" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005317709&type=1&language=en_US - [salesforce-a449be6128] - | Salesforce retirement: WhatsApp Products (Order End Date) | deprecation | published n/a | Salesforce lists "WhatsApp Products" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000396465&type=1&language=en_US - [salesforce-552cb1b43e] - | Salesforce retirement: Elastic Services (Order End Date) | deprecation | published n/a | Salesforce lists "Elastic Services" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=001096523&type=1&language=en_US - [salesforce-8e4ab33481] - | Salesforce retirement: Einstein Vision and Language APIs (Order End Date) | api_version_sunset | published n/a | Salesforce lists "Einstein Vision and Language APIs" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=001927663&type=1&language=en_US - [salesforce-c31becc332] - | Salesforce retirement: Audience Builder (Order End Date) | deprecation | published n/a | Salesforce lists "Audience Builder" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=001496487&type=1&language=en_US - [salesforce-21b3a78332] - | Salesforce retirement: Tableau Perpetual License (Order End Date) | deprecation | published n/a | Salesforce lists "Tableau Perpetual License" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=002834204&type=1&language=en_US - [salesforce-647f13f1c6] - | Salesforce retirement: Identity Connect (Order End Date) | deprecation | published n/a | Salesforce lists "Identity Connect" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000366167&type=1&language=en_US - [salesforce-b8d0b1e6fa] - | Salesforce retirement: Intelligent Form Reader (Order End Date) | deprecation | published n/a | Salesforce lists "Intelligent Form Reader" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000396814&type=1&language=en_US - [salesforce-288e52077b] - | Salesforce retirement: Chatter Answers (Order End Date) | deprecation | published n/a | Salesforce lists "Chatter Answers" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000381733&type=1&language=en_US - [salesforce-3bc97967bf] - | Salesforce retirement: Click Field Service Edge (Order End Date) | deprecation | published n/a | Salesforce lists "Click Field Service Edge" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=004518833&type=1&language=en_US - [salesforce-3e1cfda9b2] - | Salesforce retirement: Tableau Site License (Order End Date) | deprecation | published n/a | Salesforce lists "Tableau Site License" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=002188063&type=1&language=en_US - [salesforce-3b6d3ad9f2] - | Salesforce retirement: Maps Live Mobile (Order End Date) | deprecation | published n/a | Salesforce lists "Maps Live Mobile" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=005103356&type=1&language=en_US - [salesforce-ed2ba7aaf1] - | Salesforce retirement: Sustainability Cloud (Order End Date) | deprecation | published n/a | Salesforce lists "Sustainability Cloud" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000396181&type=1&language=en_US - [salesforce-8539a99b42] - | Salesforce retirement: foundationConnect (Order End Date) | deprecation | published n/a | Salesforce lists "foundationConnect" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=004464152&type=1&language=en_US - [salesforce-f31363e9db] - | Salesforce retirement: Signature Success (original purchase date before 2020) and Mission Critical Support Plans (Order End Date) | deprecation | published n/a | Salesforce lists "Signature Success (original purchase date before 2020) and Mission Critical Support Plans" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=Salesforce-Feature-Retirements&language=en_US&type=1 - [salesforce-bdf292271e] - | Salesforce retirement: LiveMessage Classic (Order End Date) | deprecation | published n/a | Salesforce lists "LiveMessage Classic" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000351084&language=en_US&mode=1&type=1 - [salesforce-5bb460f89b] - | Salesforce retirement: Work.com Workplace Command Center (Order End Date) | deprecation | published n/a | Salesforce lists "Work.com Workplace Command Center" on its Active Product & Feature Retirements page with timing: Order End Date. | https://help.salesforce.com/s/articleView?id=000391089&type=1&language=en_US