Meta yesterday blocked calls to 47 Commerce Order Management endpoints under Graph API version 26.0, ending third-party access to order listing, shipment tracking, refund processing and tax settings for the discontinued Facebook and Instagram Shops checkout experience. The change arrived alongside Marketing API v26.0, according to Meta for Developers, and forms part of a release that also removes the Instagram Explore Feed ad placement, strips Messenger Stories from targeting options, and blocks the creation of new poll ad creatives.

The releases took effect on July 29, 2026, and were detailed in a post authored by Ayyad Farah and Manjari Jain on the Meta for Developers blog. Nine distinct changes carry the same effective date, spanning both the read-side Graph API and the campaign-management Marketing API, with several tied to a second milestone set for October 27, 2026, when the same restrictions extend across every remaining supported API version.

Because the underlying commerce orders infrastructure is being retired, the Commerce Order Management endpoints have no successor. Developers who still call them will see requests fail immediately on v26.0, and the same calls will return outright errors across all other Graph API versions once the October deadline passes. No comparable functionality replaces the deprecated surface, according to Meta's documentation.

The commerce endpoint removal, in detail

The blocked endpoints cover the operational plumbing that once let third-party platforms manage orders placed through Facebook and Instagram Shops without leaving their own systems. Representative examples include calls that retrieve order details, list line items, pull payment and payment-transaction records, process refunds, track shipments, and list orders and returns tied to a Page or a Commerce Merchant Settings object. Tax settings retrieval is included in the removal as well.

This is not a new policy direction so much as the closing chapter of one that began over a year earlier. Meta phased out Facebook and Instagram shops checkout by August 2025, moving merchants toward website-based checkout instead of completing purchases directly within the two apps. That transition, which the company said would grant business owners greater control over payment processing and post-purchase customer relationships, left the Commerce Order Management API serving an increasingly hollow purpose: an interface for managing orders through a checkout flow that fewer and fewer shops were still using. The v26.0 removal formalizes what the 2025 product change had already made largely moot in practice, though any merchant or platform still relying on the older API for legacy order records loses that access with no replacement path offered.

Delivery Estimate fields disappear without a substitute

A second no-replacement removal affects forecasting rather than commerce. The daily_outcomes_curve, budget_guardrail, and estimate_dau fields are being stripped from the Delivery Estimate endpoint response because the service powering these values has been deprecated, according to Meta. Representative affected calls include ad-account-level and ad-set-level delivery estimate requests. As with the commerce endpoints, no replacement API is available, and the same removal applies across all remaining supported Graph API and Marketing API versions on October 27, 2026.

For agencies and in-house teams that built pacing dashboards or automated budget-guardrail alerts against these fields, the practical result is a forecasting gap that must be closed through other means, whether that is a different Meta reporting surface or an internally built estimation model. Meta's announcement does not describe a migration path.

Placement changes: Explore Feed, Messenger Stories, and poll creatives

Three separate changes reshape where and how ads can run.

The Instagram Explore Feed placement is no longer available as of today. Any ad set that specifies Explore will return an error on creation or update, and Meta's guidance is unambiguous: remove Explore from placement configurations. Campaign spending previously flowing to that surface shifts automatically to other eligible placements, though the announcement gives no figure for how much delivery volume that affects industry-wide.

Messenger Stories placement follows a more layered path. Beginning with versioned v26.0 calls, the story value is silently removed from messenger_positions when creating or updating ad sets, with no dedicated error returned. Historical targeting data may still show story when queried through existing ad-set fields, but new and updated ad sets will not carry it forward. Meta advises developers using manual placements to remove story from their targeting specifications, and if it is the only value present, to consider removing Messenger entirely from publisher_platforms unless another Messenger placement, such as marketing messages, remains in use. This particular change is API-only: Ads Manager, the graphical interface most advertisers use directly, is unaffected. Unversioned calls and versions earlier than v26.0 are untouched initially, but the deprecation extends to every Marketing API version, including unversioned calls, on October 27, 2026.

Poll ad creation is blocked outright for new work. Requests that create a poll creative, or that attempt to convert an existing ad to use one, are rejected starting today. Meta draws a clear line around what still works: updates to an existing ad that leave its creative untouched, such as status, budget, or schedule changes, continue to function normally. The poll_spec field and the "poll" value under interactive_components_spec become unavailable for new creative work, with the same full-version cutoff arriving on October 27, 2026.

Housing, Employment, and Financial Products campaigns gain a new requirement

Marketing API v26.0 introduces a compliance-adjacent change for advertisers running campaigns in Meta's Special Ad Categories - Housing, Employment, and Financial Products and Services. Starting today, the advantage_audience parameter within targeting_automation continues to default to 1 automatically for fully default or relaxed audience setups, matching existing behavior. But for constrained audience setups within these three regulated categories, developers must now explicitly set advantage_audience to either 1 or 0 when creating a new ad set.

This mirrors a requirement Meta introduced for campaigns outside Special Ad Categories back in Marketing API v23.0, extending the same explicit-declaration logic to the more heavily regulated advertising categories. Critically, the behavior applies only to new ad set creation; updating an existing ad set does not trigger the requirement on any API version, according to the documentation. The affected endpoints are the ad-set creation, update, and copy calls within the Marketing API.

Rights Manager fields migrate to a dedicated ownership type

Away from advertising delivery, Meta is restructuring how copyright ownership data is represented in the Graph API. The reference_owner and matched_reference_owner fields on AudioVisualReferenceMatch and ImageReferenceMatch objects, along with the sending_rights_holder and receiving_rights_holder fields on CopyrightOwnershipTransfer, are being deprecated in favor of replacement fields that return a dedicated RightsHolderOwner type.

According to Meta, the new type better represents the ownership model that Rights Manager, the company's copyright-detection tool for video content, actually uses. Starting with v26.0, the deprecated fields are no longer returned, replaced by reference_owner_rh_owner, matched_reference_owner_rh_owner, sending_rights_holder_owner, and receiving_rights_holder_owner. This change carries a longer runway than most others in the release: the deprecated fields continue functioning on v25.0 and earlier for two full years after the v26.0 launch, well beyond the standard 90-day cycle applied elsewhere.

Legacy protocol behaviors retired

Five request-handling behaviors that have existed in the Graph API for years disappear from v26.0 calls today: the prettyparameter 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 handling that previously enabled 304 Not Modified responses.

Meta frames the retirement as a simplification measure intended to make request handling more consistent. Practically, JSON responses on v26.0 now always arrive in compact form, requiring client-side formatting; requests including date_format return a parameter error rather than a formatted date; and requests to the root /?ids=... pattern likewise return a parameter error, pushing developers toward per-object requests or Graph API's supported batching mechanism instead. The separate debug_token endpoint, commonly used for inspecting access token validity, is explicitly unaffected. All five retirements extend to every remaining supported Graph API version on October 27, 2026.

Legacy Page fields deprecated for the New Pages Experience

A narrower deprecation targets five legacy Page-node fields - current_location, genre, network, parking, and start_info - along with the auto_publish_page_info_updates Page setting, but only for pages using Meta's New Pages Experience. On v26.0 and later, requesting any of these fields on a New Pages Experience page returns a version error, and the setting no longer appears in the Page settings response. Pages that have not migrated to the New Pages Experience are unaffected for now. Meta places the date for the change reaching all remaining API versions at approximately 90 days after launch, in late October 2026, with the precise date still to be confirmed.

Ads in WhatsApp Status expand identity, targeting, and creative options

Not every v26.0 change is a removal. Marketing API v26.0 expands Ads in WhatsApp Status with several additions that broaden how advertisers can build and target these placements.

Third-party Marketing API callers must now explicitly include a wamo_whatsapp_identity_spec field in ad creatives intended for WhatsApp Status delivery, since it is not automatically defaulted for these callers. On targeting, when WhatsApp Status placement is selected and user_age_unknown is left unset, it now defaults to true, letting campaigns reach WhatsApp users whose age is unknown to Meta's systems. On optimization, Conversion Optimization for offsite conversions now extends across the Sales, Leads, and Engagement objectives, and Landing Page Views optimization is likewise supported. On creative, carousel formats now support up to 10 cards within WhatsApp Status placements.

These additions build on ground Meta established before this release. WhatsApp Status advertising launched globally in June 2025, using signals from connected Instagram and Facebook accounts to target the messaging platform's roughly 1.5 billion daily active users, according to Meta's original announcement. The European rollout followed a longer regulatory review; Meta's own 2026 Digital Markets Act compliance filing confirmed the company was preparing to extend WhatsApp Channels and Status advertising into the European Union, citing consent flows designed to satisfy the bloc's cross-service data combination requirements.

Web-only destinations blocked for combined Website and App campaigns

A further Marketing API v26.0 change affects how ad creatives can be paired with campaign conversion locations. Beginning today, an ad cannot use a creative with applink_treatment set to web_only when the campaign in question uses both Website and App conversion locations simultaneously. The Ad Creative endpoint itself is not changing structurally, but the applink_treatment value configured through it becomes incompatible with that specific combined-destination setup. Meta's guidance directs developers toward automatic destination selection or an alternative compatible manual destination for campaigns spanning both Website and App outcomes. The restriction, like most others in this release, extends to all Marketing API versions on October 27, 2026.

Two Graph API versions scheduled for retirement

Separately from the version 26.0 changes taking effect today, Meta confirmed two upcoming full-version retirements on its standard versioning schedule. Graph API v20.0 will be deprecated and removed from the platform on September 24, 2026. Graph API v21.0 follows on January 21, 2027. Meta's guidance to developers remains consistent with prior version-retirement cycles: migrate calls to the latest available API version to avoid disruption when a deprecated version stops accepting requests.

Graph API v21.0 is the version Meta released on October 2, 2024, introducing further limits on original campaign objectives. Its scheduled January 2027 retirement gives developers still running on that version roughly eighteen months of continued access from today's v26.0 release.

Meta Business SDK v26 and the wider developer sequence

Meta said the Business SDK v26 release will follow shortly after Graph API v26 itself, carrying dependency upgrades, integration with the open-sourced Conversions API Parameter Builder, and the same deprecations described above, including the Commerce Order Management API's removal and the five legacy protocol features. The Parameter Builder integration is intended to auto-generate and enhance parameters including fbc, fbp, event_source_url, referrer_url, and client_ip_address, alongside automatic personal data normalization and hashing for supported languages, gated by advertiser-level preference settings, according to Meta's documentation. Two further Platform SDK deprecations run on their own two-year schedule: Facebook Platform SDK v20.0 in September 2026, and v21.0 in January 2027, aligning with the Graph API retirement dates above.

Today's release lands roughly five months after Meta released Graph API v25.0 and Marketing API v25.0 on February 18, 2026, the version that required advertisers to adopt the unified Advantage+ campaign structure across all ad set creation. That release followed Meta's October 8, 2025 deprecation of the legacy Advantage Shopping and Advantage App Campaign APIs, which first prohibited new legacy-structure campaigns while permitting existing ones to keep running. Version 25.0 has since served as the reference version across subsequent Meta developer announcements, including webhook subscription capabilities documented on July 22, 2026, which added an ads subscription endpoint carrying more than 88 notification types. Whether that documentation and its code examples get updated to reference v26.0 is not addressed in today's announcement.

Why this matters for the marketing community

Version releases of this kind rarely make headlines outside developer channels, yet the cumulative effect on marketing operations is substantial. PPC Land has tracked Meta's Marketing API through a dense sequence of version releases and deprecations stretching back to Graph API v19.0 in January 2024 and continuing through v20.0 in May 2024, v21.0 in October 2024, and the Instagram and Marketing API simplification announced in January 2025. Each cycle has narrowed the surface area developers must maintain while consolidating campaign creation around Meta's automated Advantage+ systems.

What distinguishes today's release is the number of changes offering no stated replacement. The Commerce Order Management API's 47 endpoints and the Delivery Estimate forecasting fields both disappear without a documented successor, which places the burden of finding alternative solutions squarely on the developers and agencies who had built tooling against them. For pacing and forecasting teams specifically, losing budget_guardrail and daily_outcomes_curve removes signals that some automated alert systems may have depended on for early warning of budget or delivery problems, absent a Meta-provided substitute.

The Special Ad Categories change carries a different kind of significance. Housing, Employment, and Financial Products and Services campaigns already operate under heightened regulatory and platform scrutiny, following years of legal and civil rights attention to discriminatory ad targeting in these categories. Requiring explicit declaration of advantage_audiencesettings for constrained audience setups in these categories, rather than allowing silent defaults, adds a small but meaningful layer of deliberate configuration to campaigns that regulators and advocacy groups continue to watch closely.

For advertisers running WhatsApp Status campaigns, the identity, targeting, and creative expansions announced today extend a format Meta has been building out since mid-2025, and the mandatory wamo_whatsapp_identity_spec requirement for third-party callers signals that Meta continues tightening identity verification requirements around cross-platform ad delivery, even as it expands the format's targeting and creative flexibility elsewhere in the same release.

None of these changes individually amounts to a dramatic shift in how advertising works on Meta's platforms. Collectively, they represent the routine but consequential maintenance that keeps a sprawling advertising API current, and they arrive on a schedule that gives most affected developers a defined window - typically the standard 90 days to October 27, 2026 - before the same restrictions apply irreversibly across every remaining supported API version.

Timeline

Summary

Who: Meta, through its Meta for Developers division, in a blog post authored by Ayyad Farah and Manjari Jain. The changes affect developers, advertising agencies, and in-house marketing technology teams that integrate with Meta's Graph API and Marketing API.

What: Meta released Graph API v26.0 and Marketing API v26.0, blocking calls to 47 Commerce Order Management endpoints with no replacement API, removing Delivery Estimate forecasting fields with no replacement, eliminating the Instagram Explore Feed ad placement, silently dropping Messenger Stories from ad set targeting, blocking new poll ad creative creation, requiring explicit audience-automation settings for constrained Housing, Employment, and Financial Products campaigns, migrating Rights Manager ownership fields to a new type, retiring five legacy Graph API protocol behaviors, deprecating select legacy Page fields for the New Pages Experience, and expanding Ads in WhatsApp Status with new identity, targeting, and creative capabilities.

When: Today, July 29, 2026. Most of the changes extend to all remaining supported API versions on October 27, 2026, ninety days later. Separately, Graph API v20.0 is deprecated on September 24, 2026, and Graph API v21.0 is deprecated on January 21, 2027.

Where: Across Meta's Graph API and Marketing API, affecting Facebook, Instagram, Messenger, and WhatsApp advertising and platform integrations globally.

Why: Meta is retiring infrastructure tied to discontinued products, such as on-platform Shops checkout and a deprecated delivery-forecasting service, while simplifying request handling, tightening compliance requirements for regulated ad categories, and expanding monetization capacity on WhatsApp Status, a placement the company has been building out since June 2025.