Meta yesterday blocked calls to 47 Commerce Order Administration endpoints beneath Graph API model 26.0, ending third-party entry to order itemizing, cargo monitoring, refund processing and tax settings for the discontinued Fb and Instagram Outlets checkout expertise. The change arrived alongside Advertising API v26.0, in response to Meta for Builders, and varieties a part of a launch that additionally removes the Instagram Discover Feed advert placement, strips Messenger Tales from concentrating on choices, and blocks the creation of latest ballot advert creatives.

The releases took impact on July 29, 2026, and have been detailed in a submit authored by Ayyad Farah and Manjari Jain on the Meta for Builders weblog. 9 distinct modifications carry the identical efficient date, spanning each the read-side Graph API and the campaign-management Advertising API, with a number of tied to a second milestone set for October 27, 2026, when the identical restrictions prolong throughout each remaining supported API model.

As a result of the underlying commerce orders infrastructure is being retired, the Commerce Order Administration endpoints haven’t any successor. Builders who nonetheless name them will see requests fail instantly on v26.0, and the identical calls will return outright errors throughout all different Graph API variations as soon as the October deadline passes. No comparable performance replaces the deprecated floor, in response to Meta’s documentation.

The commerce endpoint removing, intimately

The blocked endpoints cowl the operational plumbing that when let third-party platforms handle orders positioned via Fb and Instagram Outlets with out leaving their very own techniques. Consultant examples embody calls that retrieve order particulars, checklist line objects, pull cost and payment-transaction data, course of refunds, monitor shipments, and checklist orders and returns tied to a Web page or a Commerce Service provider Settings object. Tax settings retrieval is included within the removing as properly.

This isn’t a brand new coverage path a lot because the closing chapter of 1 that started over a 12 months earlier. Meta phased out Facebook and Instagram shops checkout by August 2025, transferring retailers towards website-based checkout as an alternative of finishing purchases immediately inside the two apps. That transition, which the corporate mentioned would grant enterprise homeowners higher management over cost processing and post-purchase buyer relationships, left the Commerce Order Administration API serving an more and more hole goal: an interface for managing orders via a checkout stream that fewer and fewer retailers have been nonetheless utilizing. The v26.0 removing formalizes what the 2025 product change had already made largely moot in follow, although any service provider or platform nonetheless counting on the older API for legacy order data loses that entry with no alternative path supplied.

Supply Estimate fields disappear with no substitute

A second no-replacement removing impacts forecasting somewhat than commerce. The daily_outcomes_curvebudget_guardrail, and estimate_dau fields are being stripped from the Supply Estimate endpoint response as a result of the service powering these values has been deprecated, in response to Meta. Consultant affected calls embody ad-account-level and ad-set-level supply estimate requests. As with the commerce endpoints, no alternative API is on the market, and the identical removing applies throughout all remaining supported Graph API and Advertising API variations on October 27, 2026.

For companies and in-house groups that constructed pacing dashboards or automated budget-guardrail alerts towards these fields, the sensible result’s a forecasting hole that have to be closed via different means, whether or not that could be a completely different Meta reporting floor or an internally constructed estimation mannequin. Meta’s announcement doesn’t describe a migration path.

Placement modifications: Discover Feed, Messenger Tales, and ballot creatives

Three separate modifications reshape the place and the way advertisements can run.

The Instagram Discover Feed placement is not out there as of as we speak. Any advert set that specifies Discover will return an error on creation or replace, and Meta’s steerage is unambiguous: take away Discover from placement configurations. Marketing campaign spending beforehand flowing to that floor shifts routinely to different eligible placements, although the announcement provides no determine for the way a lot supply quantity that impacts industry-wide.

Messenger Tales placement follows a extra layered path. Starting with versioned v26.0 calls, the story worth is silently faraway from messenger_positions when creating or updating advert units, with no devoted error returned. Historic concentrating on knowledge should present story when queried via present ad-set fields, however new and up to date advert units won’t carry it ahead. Meta advises builders utilizing guide placements to take away story from their concentrating on specs, and if it’s the solely worth current, to contemplate eradicating Messenger fully from publisher_platforms except one other Messenger placement, equivalent to advertising messages, stays in use. This explicit change is API-only: Advertisements Supervisor, the graphical interface most advertisers use immediately, is unaffected. Unversioned calls and variations sooner than v26.0 are untouched initially, however the deprecation extends to each Advertising API model, together with unversioned calls, on October 27, 2026.

Ballot advert creation is blocked outright for brand spanking new work. Requests that create a ballot artistic, or that try to convert an present advert to make use of one, are rejected beginning as we speak. Meta attracts a transparent line round what nonetheless works: updates to an present advert that go away its artistic untouched, equivalent to standing, funds, or schedule modifications, proceed to perform usually. The poll_spec subject and the “ballot” worth beneath interactive_components_spec grow to be unavailable for brand spanking new artistic work, with the identical full-version cutoff arriving on October 27, 2026.

Housing, Employment, and Monetary Merchandise campaigns acquire a brand new requirement

Advertising API v26.0 introduces a compliance-adjacent change for advertisers operating campaigns in Meta’s Particular Advert Classes – Housing, Employment, and Monetary Merchandise and Companies. Beginning as we speak, the advantage_audience parameter inside targeting_automation continues to default to 1 routinely for totally default or relaxed viewers setups, matching present habits. However for constrained viewers setups inside these three regulated classes, builders should now explicitly set advantage_audience to both 1 or 0 when creating a brand new advert set.

This mirrors a requirement Meta launched for campaigns outdoors Particular Advert Classes again in Advertising API v23.0, extending the identical explicit-declaration logic to the extra closely regulated promoting classes. Critically, the habits applies solely to new advert set creation; updating an present advert set doesn’t set off the requirement on any API model, in response to the documentation. The affected endpoints are the ad-set creation, replace, and replica calls inside the Advertising API.

Rights Supervisor fields migrate to a devoted possession sort

Away from promoting supply, Meta is restructuring how copyright possession knowledge is represented within the Graph API. The reference_owner and matched_reference_owner fields on AudioVisualReferenceMatch and ImageReferenceMatch objects, together with the sending_rights_holder and receiving_rights_holder fields on CopyrightOwnershipTransfer, are being deprecated in favor of alternative fields that return a devoted RightsHolderOwner sort.

In keeping with Meta, the brand new sort higher represents the possession mannequin that Rights Supervisor, the corporate’s copyright-detection software for video content material, really makes use of. Beginning with v26.0, the deprecated fields are not returned, changed by reference_owner_rh_ownermatched_reference_owner_rh_ownersending_rights_holder_owner, and receiving_rights_holder_owner. This modification carries an extended runway than most others within the launch: the deprecated fields proceed performing on v25.0 and earlier for 2 full years after the v26.0 launch, properly past the usual 90-day cycle utilized elsewhere.

Legacy protocol behaviors retired

5 request-handling behaviors which have existed within the Graph API for years disappear from v26.0 calls as we speak: the fairlyparameter for formatted JSON output, the debug parameter and its accompanying debug response envelope, the date_formatparameter, root-level GET /?ids=... batch-style requests, and legacy If-None-Match and ETag dealing with that beforehand enabled 304 Not Modified responses.

Meta frames the retirement as a simplification measure supposed to make request dealing with extra constant. Virtually, JSON responses on v26.0 now at all times arrive in compact type, requiring client-side formatting; requests together with date_format return a parameter error somewhat than a formatted date; and requests to the basis /?ids=... sample likewise return a parameter error, pushing builders towards per-object requests or Graph API’s supported batching mechanism as an alternative. The separate debug_token endpoint, generally used for inspecting entry token validity, is explicitly unaffected. All 5 retirements prolong to each remaining supported Graph API model on October 27, 2026.

Legacy Web page fields deprecated for the New Pages Expertise

A narrower deprecation targets 5 legacy Web page-node fields – current_locationstylecommunityparking, and start_info – together with the auto_publish_page_info_updates Web page setting, however just for pages utilizing Meta’s New Pages Expertise. On v26.0 and later, requesting any of those fields on a New Pages Expertise web page returns a model error, and the setting not seems within the Web page settings response. Pages that haven’t migrated to the New Pages Expertise are unaffected for now. Meta locations the date for the change reaching all remaining API variations at roughly 90 days after launch, in late October 2026, with the exact date nonetheless to be confirmed.

Advertisements in WhatsApp Standing develop identification, concentrating on, and inventive choices

Not each v26.0 change is a removing. Advertising API v26.0 expands Advertisements in WhatsApp Standing with a number of additions that broaden how advertisers can construct and goal these placements.

Third-party Advertising API callers should now explicitly embody a wamo_whatsapp_identity_spec subject in advert creatives supposed for WhatsApp Standing supply, since it isn’t routinely defaulted for these callers. On concentrating on, when WhatsApp Standing placement is chosen and user_age_unknown is left unset, it now defaults to true, letting campaigns attain WhatsApp customers whose age is unknown to Meta’s techniques. On optimization, Conversion Optimization for offsite conversions now extends throughout the Gross sales, Leads, and Engagement goals, and Touchdown Web page Views optimization is likewise supported. On artistic, carousel codecs now assist as much as 10 playing cards inside WhatsApp Standing placements.

These additions construct on floor Meta established earlier than this launch. WhatsApp Standing promoting launched globally in June 2025, utilizing indicators from linked Instagram and Fb accounts to focus on the messaging platform’s roughly 1.5 billion every day lively customers, in response to Meta’s authentic announcement. The European rollout adopted an extended regulatory evaluate; Meta’s personal 2026 Digital Markets Act compliance submitting confirmed the corporate was making ready to increase WhatsApp Channels and Standing promoting into the European Union, citing consent flows designed to fulfill the bloc’s cross-service knowledge mixture necessities.

Net-only locations blocked for mixed Web site and App campaigns

An additional Advertising API v26.0 change impacts how advert creatives might be paired with marketing campaign conversion areas. Starting as we speak, an advert can not use a artistic with applink_treatment set to web_only when the marketing campaign in query makes use of each Web site and App conversion areas concurrently. The Advert Artistic endpoint itself just isn’t altering structurally, however the applink_treatment worth configured via it turns into incompatible with that particular combined-destination setup. Meta’s steerage directs builders towards computerized vacation spot choice or another appropriate guide vacation spot for campaigns spanning each Web site and App outcomes. The restriction, like most others on this launch, extends to all Advertising API variations on October 27, 2026.

Two Graph API variations scheduled for retirement

Individually from the model 26.0 modifications taking impact as we speak, Meta confirmed two upcoming full-version retirements on its customary versioning schedule. Graph API v20.0 will probably be deprecated and faraway from the platform on September 24, 2026. Graph API v21.0 follows on January 21, 2027. Meta’s steerage to builders stays per prior version-retirement cycles: migrate calls to the newest out there API model to keep away from disruption when a deprecated model stops accepting requests.

Graph API v21.0 is the model Meta released on October 2, 2024, introducing additional limits on authentic marketing campaign goals. Its scheduled January 2027 retirement provides builders nonetheless operating on that model roughly eighteen months of continued entry from as we speak’s v26.0 launch.

Meta Enterprise SDK v26 and the broader developer sequence

Meta mentioned the Enterprise SDK v26 launch will observe shortly after Graph API v26 itself, carrying dependency upgrades, integration with the open-sourced Conversions API Parameter Builder, and the identical deprecations described above, together with the Commerce Order Administration API’s removing and the 5 legacy protocol options. The Parameter Builder integration is meant to auto-generate and improve parameters together with fbcfbpevent_source_urlreferrer_url, and client_ip_address, alongside computerized private knowledge normalization and hashing for supported languages, gated by advertiser-level choice settings, in response to Meta’s documentation. Two additional Platform SDK deprecations run on their very own two-year schedule: Fb Platform SDK v20.0 in September 2026, and v21.0 in January 2027, aligning with the Graph API retirement dates above.

At present’s launch lands roughly 5 months after Meta released Graph API v25.0 and Marketing API v25.0 on February 18, 2026, the model that required advertisers to undertake the unified Advantage+ marketing campaign construction throughout all advert set creation. That launch adopted Meta’s October 8, 2025 deprecation of the legacy Advantage Shopping and Advantage App Campaign APIs, which first prohibited new legacy-structure campaigns whereas allowing present ones to maintain operating. Model 25.0 has since served because the reference model throughout subsequent Meta developer bulletins, together with webhook subscription capabilities documented on July 22, 2026, which added an advertisements subscription endpoint carrying greater than 88 notification sorts. Whether or not that documentation and its code examples get up to date to reference v26.0 just isn’t addressed in as we speak’s announcement.

Model releases of this type not often make headlines outdoors developer channels, but the cumulative impact on advertising operations is substantial. PPC Land has tracked Meta’s Advertising API via a dense sequence of model releases and deprecations stretching again to Graph API v19.0 in January 2024 and persevering with via v20.0 in May 2024v21.0 in October 2024, and the Instagram and Marketing API simplification announced in January 2025. Every cycle has narrowed the floor space builders should keep whereas consolidating marketing campaign creation round Meta’s automated Benefit+ techniques.

What distinguishes as we speak’s launch is the variety of modifications providing no acknowledged alternative. The Commerce Order Administration API’s 47 endpoints and the Supply Estimate forecasting fields each disappear with no documented successor, which locations the burden of discovering different options squarely on the builders and companies who had constructed tooling towards them. For pacing and forecasting groups particularly, shedding budget_guardrail and daily_outcomes_curve removes indicators that some automated alert techniques could have trusted for early warning of funds or supply issues, absent a Meta-provided substitute.

The Particular Advert Classes change carries a special sort of significance. Housing, Employment, and Monetary Merchandise and Companies campaigns already function beneath heightened regulatory and platform scrutiny, following years of authorized and civil rights consideration to discriminatory advert concentrating on in these classes. Requiring specific declaration of advantage_audiencesettings for constrained viewers setups in these classes, somewhat than permitting silent defaults, provides a small however significant layer of deliberate configuration to campaigns that regulators and advocacy teams proceed to look at intently.

For advertisers operating WhatsApp Standing campaigns, the identification, concentrating on, and inventive expansions introduced as we speak prolong a format Meta has been constructing out since mid-2025, and the obligatory wamo_whatsapp_identity_spec requirement for third-party callers indicators that Meta continues tightening identification verification necessities round cross-platform advert supply, even because it expands the format’s concentrating on and inventive flexibility elsewhere in the identical launch.

None of those modifications individually quantities to a dramatic shift in how promoting works on Meta’s platforms. Collectively, they characterize the routine however consequential upkeep that retains a sprawling promoting API present, and so they arrive on a schedule that offers most affected builders an outlined window – sometimes the usual 90 days to October 27, 2026 – earlier than the identical restrictions apply irreversibly throughout each remaining supported API model.


Timeline

Abstract

Who: Meta, via its Meta for Builders division, in a weblog submit authored by Ayyad Farah and Manjari Jain. The modifications have an effect on builders, promoting companies, and in-house advertising expertise groups that combine with Meta’s Graph API and Advertising API.

What: Meta launched Graph API v26.0 and Advertising API v26.0, blocking calls to 47 Commerce Order Administration endpoints with no alternative API, eradicating Supply Estimate forecasting fields with no alternative, eliminating the Instagram Discover Feed advert placement, silently dropping Messenger Tales from advert set concentrating on, blocking new ballot advert artistic creation, requiring specific audience-automation settings for constrained Housing, Employment, and Monetary Merchandise campaigns, migrating Rights Supervisor possession fields to a brand new sort, retiring 5 legacy Graph API protocol behaviors, deprecating choose legacy Web page fields for the New Pages Expertise, and increasing Advertisements in WhatsApp Standing with new identification, concentrating on, and inventive capabilities.

When: At present, July 29, 2026. Many of the modifications prolong to all remaining supported API variations on October 27, 2026, ninety days later. Individually, Graph API v20.0 is deprecated on September 24, 2026, and Graph API v21.0 is deprecated on January 21, 2027.

The place: Throughout Meta’s Graph API and Advertising API, affecting Fb, Instagram, Messenger, and WhatsApp promoting and platform integrations globally.

Why: Meta is retiring infrastructure tied to discontinued merchandise, equivalent to on-platform Outlets checkout and a deprecated delivery-forecasting service, whereas simplifying request dealing with, tightening compliance necessities for regulated advert classes, and increasing monetization capability on WhatsApp Standing, a placement the corporate has been constructing out since June 2025.


Source link