Graph API v26.0 and Marketing API v26.0 include new capabilities, deprecations, and breaking changes. Review the highlights below and visit the V26.0 changelog for the complete list of changes and details.

• Graph API - Commerce Order Management: Calls to affected endpoints on v26.0 and later are blocked beginning July 29, 2026. The endpoints are removed from all remaining Graph API versions on October 27, 2026, after which calls return errors. No replacement API is available.
• Graph API - Rights Manager owner fields: Starting with v26.0 on July 29, 2026, replacement fields returning the RightsHolderOwner type are available and the deprecated owner fields are no longer returned. The deprecated fields remain available on v25.0 and earlier for two years after the v26.0 launch.
• Graph API - Legacy protocol features: Five legacy behaviors are removed from v26.0 calls beginning July 29, 2026. The same behavior applies to all remaining supported Graph API versions beginning October 27, 2026.
• Marketing API - Ads in WhatsApp Status: v26.0 adds expanded identity, targeting, optimization, and creative capabilities beginning July 29, 2026.
• Marketing API - Advantage+ Audience for Housing, Employment, and Financial Products and Services campaigns: Beginning with v26.0 on July 29, 2026, new or copied ad sets with constrained targeting must explicitly set advantage_audience to 1 or 0. Default or relaxed setups continue to default it to 1, and existing ad-set updates are unaffected.
• Marketing API - Instagram Explore Feed: The placement is no longer available beginning with v26.0 on July 29, 2026. Developers should remove Explore from their placement configurations.
• Marketing API - Web-only destination for Web+App campaigns: Beginning with v26.0 on July 29, 2026, an ad cannot use a creative with applink_treatment set to web_only when the campaign uses Website and App conversion locations. The restriction applies to all Marketing API versions on October 27, 2026.
• Marketing API - Messenger Stories: Beginning with versioned v26.0 calls on July 29, 2026, the story value is silently removed from messenger_positions when creating or updating ad sets. The deprecation applies to all Marketing API versions, including unversioned calls, on October 27, 2026.
• Marketing API - Poll ad creation: Beginning with v26.0 on July 29, 2026, requests that create a poll creative or change an ad to use one are rejected. Existing-ad updates that do not change the creative remain supported. The deprecation applies to all Marketing API versions on October 27, 2026.
• Graph API and Marketing API - Delivery Estimate fields: The daily_outcomes_curve, budget_guardrail, and estimate_dau response fields are removed from v26.0 calls beginning July 29, 2026, and from all remaining supported versions on October 27, 2026. No replacement API is available.
• Graph API version retirements: Graph API v20.0 is deprecated and removed on September 24, 2026. Graph API v21.0 is deprecated and removed on January 21, 2027.

Beginning with Marketing API v26.0 on July 29, 2026, Ads in WhatsApp Status support additional identity, targeting, optimization, and creative capabilities.

• WhatsApp identity: Third-party Marketing API callers must explicitly include wamo_whatsapp_identity_spec in ad creatives intended for WhatsApp Status delivery. WhatsApp identity is not automatically defaulted for these callers.
• Unknown-age targeting: When WhatsApp Status placement is selected and user_age_unknown is not set, the field defaults to true, meaning the campaign can reach people on WhatsApp whose age is unknown.
• Optimization: Conversion Optimization for offsite conversions is supported across the Sales, Leads, and Engagement objectives. Landing Page Views optimization is also supported.
• Creative format: Carousel ads support up to 10 cards.

See the placement targeting and basic targeting documentation for details.

The daily_outcomes_curve, budget_guardrail, and estimate_dau fields are being removed from the Delivery Estimate endpoint response because the service powering these values has been deprecated. Starting with Graph API v26.0 and Marketing API v26.0 on July 29, 2026, these fields will no longer be returned. The change will apply to all remaining supported Graph API and Marketing API versions on October 27, 2026. No replacement API is available.

Developers should remove any usage of or references to these fields before the applicable removal date.

Representative affected endpoints include:

• GET /{ad-account-id}/delivery_estimate - Ad account delivery estimates
• GET /{adset-id}/delivery_estimate - Ad set delivery estimates

The complete field and endpoint list will be available in the V26.0 changelog.

Apps calling these endpoints on Graph API v26.0 and later will be blocked beginning July 29, 2026. The endpoints will be removed for all remaining Graph API versions on October 27, 2026, after which calls will return errors.

The checkout directly on Facebook and Instagram experience for Shops has been fully sunset. The Commerce Order Management API allowed third-party platforms to list orders, view order details, manage shipments, process cancellations, handle refunds, and track returns for that checkout experience. Because the underlying commerce orders infrastructure is being retired, these endpoints are being deprecated.

Developers should stop calling these endpoints and remove the dependency. No replacement API is available.

Representative affected endpoints include:

• GET /{commerce-order-id} - Order details
• GET /{commerce-order-id}/items - Order line items
• GET /{commerce-order-id}/payments - Order payments
• GET /{commerce-order-id}/payment_transaction_details - Payment transaction details
• GET /{commerce-order-id}/refunds - Order refunds
• GET /{commerce-order-id}/shipments - Order shipments
• GET /{commerce-order-shipment-id}/items - Shipment line items
• GET /{commerce-return-id} - Return details
• GET /{commerce-order-cancellation-id}/items - Cancellation line items
• GET /{page-id}/commerce_orders - List orders by Page
• GET /{commerce-merchant-settings-id}/commerce_orders - List orders by Commerce Merchant Settings
• GET /{commerce-merchant-settings-id}/commerce_returns - List returns by Commerce Merchant Settings
• GET /{commerce-merchant-settings-id}/tax_settings - Tax settings

The complete list of 47 affected endpoints will be available in the Graph API v26.0 changelog.

The reference_owner and matched_reference_owner fields on AudioVisualReferenceMatch and ImageReferenceMatch, along with the sending_rights_holder and receiving_rights_holder fields on CopyrightOwnershipTransfer, are being deprecated. Starting with Graph API v26.0, replacement fields returning the dedicated RightsHolderOwner type are available to better represent the ownership model used by Rights Manager, and the deprecated fields are no longer returned in v26.0 and later responses.

The deprecated fields will continue to work on v25.0 and earlier for two years after the v26.0 launch, after which they will be removed. Developers should migrate to the replacement fields during this two-year window.

Use the following replacement fields:

• Use reference_owner_rh_owner instead of reference_owner.
• Use matched_reference_owner_rh_owner instead of matched_reference_owner.
• Use sending_rights_holder_owner instead of sending_rights_holder.
• Use receiving_rights_holder_owner instead of receiving_rights_holder.

Representative affected endpoints include:

• GET /{audio-visual-reference-match-id} - Reference match details
• GET /{image-reference-match-id} - Image reference match details
• GET /{copyright-ownership-transfer-id} - Ownership transfer details

The complete field list will be available in the Graph API v26.0 changelog.

Beginning July 29, 2026, Graph API v26.0 and later no longer support five legacy protocol behaviors: pretty, debug, date_format, root GET /?ids=... requests, and legacy If-None-Match / ETag handling.

These behaviors are being retired to simplify Graph API responses and make request handling more consistent.

For Graph API v26.0 and later:

• pretty is ignored, and JSON responses use compact formatting. Format JSON in client tools or code.
• debug is ignored, and no debug response envelope is added. Use standard debugging tools. The debug_token endpoint is unaffected.
• Requests that include date_format return a parameter error. Use the default date format and convert values locally if needed.
• Root requests using GET /?ids=... return a parameter error. Use per-object requests or supported batching.
• If-None-Match is ignored. Legacy ETag response headers and 304 Not Modified behavior are removed, and requests return full responses.

Beginning October 27, 2026, these changes apply to all remaining supported Graph API versions. Review runtime request logs and the Graph API v26.0 changelog for migration details.

Developer blog post draft. Target release: Graph API v26.0. Change type: Deprecation (90-day).

Summary

For New Pages Experience pages, five legacy Page-node fields (current_location, genre, network, parking, start_info) and the auto_publish_page_info_updates Page setting are being deprecated starting with Graph API v26.0. These fields are no longer maintained and should not be accessed for New Pages Experience pages.

Timeline

• July 29, 2026: The fields are blocked and the setting is removed on v26.0 and later for New Pages Experience pages.
• Approximately 90 days after launch: The same change applies to all remaining versions. The exact date in late October 2026 is to be confirmed.

What is changing

On v26.0 and later, requesting any of these five fields on a New Pages Experience page returns a version error, and the auto_publish_page_info_updates setting no longer appears in the Page settings response. On earlier versions, behavior is unchanged until the 90-day migration window closes, after which the same applies to all versions.

Affected endpoints:

• GET /{page-id}?fields=current_location
• GET /{page-id}?fields=genre
• GET /{page-id}?fields=network
• GET /{page-id}?fields=parking
• GET /{page-id}?fields=start_info
• GET /{page-id}?fields=settings - the auto_publish_page_info_updates setting is removed from the returned settings list

What developers should do

• Remove these fields and the auto_publish_page_info_updates setting from your Page requests.
• Check your request logs, client integrations, and dashboards for use of these fields on New Pages Experience pages.
• See the Graph API v26.0 changelog for the complete, up-to-date list.

Reference

• Page node reference

Starting July 29, 2026, with Marketing API v26.0, the advantage_audience parameter within targeting_automation will automatically default to 1 for fully default or relaxed audience setups. For constrained audience setups, developers must explicitly set advantage_audience to either 1 or 0 for campaigns in the Housing, Employment, or Financial Products and Services special ad categories.

This behavior applies only when creating a new ad set. Updating an existing ad set will not exhibit this behavior on any API version.

This is the same behavior introduced for campaigns outside Special Ad Categories in Marketing API v23.0. See the Advantage+ Audience troubleshooting documentation for details.

The following API endpoints are affected:

• POST /{ad-account-id}/adsets
• POST /{adset-id}
• POST /{adset-id}/copies

Beginning with Marketing API v26.0 on July 29, 2026, the Instagram Explore Feed placement will no longer be available. Delivery to Explore will stop, and campaign spending will shift automatically to other eligible placements.

Attempting to create or update an ad set that specifies the Explore placement will return an error. Developers should remove Explore from placement configurations and use other eligible placements.

The following endpoints are affected:

• POST /act_{ad-account-id}/adsets
• POST /{ad-set-id}

Starting on July 29, 2026, with Marketing API v26.0, developers will no longer be able to attach an ad creative with applink_treatment set to web_only to an ad in a campaign that uses Website and App conversion locations. This affects ad creation and updates through POST /act_{ad-account-id}/ads and POST /{ad-id}.

The Ad Creative endpoint is not changing, but POST /act_{ad-account-id}/adcreatives is where the applink_treatment value is configured. Developers should review their integrations for applink_treatment=web_only and use automatic destination selection or another compatible manual destination for Website and App campaigns.

On October 27, 2026, 90 days after the release of v26.0, this restriction will apply to all Marketing API versions. See the Ad and Ad Creative documentation for more information.

Beginning with Marketing API v26.0 on July 29, 2026, the story value in messenger_positions will no longer be available when creating or updating ad sets through versioned v26.0 or later calls.

For these calls, story will be silently removed from the targeting specification and will no longer appear in effective placements for new or existing ad sets. Historical targeting data may continue to include story when requested through GET /{ad_set-id}?fields=targeting. No dedicated error will be returned, but standard placement validation errors may apply if removing story leaves an invalid placement configuration.

The following endpoints are affected:

• POST /act_{ad-account-id}/adsets
• POST /{ad_set-id}

Developers using manual placements should remove story from messenger_positions. If it is the only value, remove the entire messenger_positions field and consider removing messenger from publisher_platforms when no other Messenger placement, such as marketing_messages, is used. No action is required for Advantage+ Placements.

This API-only change does not affect Ads Manager. Unversioned calls and calls to versions earlier than v26.0 are initially unaffected. On October 27, 2026, 90 days after the v26.0 release, the deprecation will apply to all Marketing API versions, including unversioned calls.

Beginning with Marketing API v26.0 on July 29, 2026, poll components will no longer be supported when creating or updating ads and ad creatives. The poll_spec field and the "poll" value for the type field will no longer be available under interactive_components_spec.

Requests that create a poll creative or change an ad to use one will be rejected. Updates to an existing ad that do not change its creative, such as status, budget, or schedule changes, can continue.

The following endpoints are affected:

• POST /{ad_account_id}/adcreatives
• POST /{ad_account_id}/ads
• POST /{ad_id}
• GET /{ad_account_id}/generatepreviews

Developers should remove poll-related fields from their creative specifications and use a creative without a poll component. Calls to versions earlier than v26.0 and unversioned calls are initially unaffected.

On October 27, 2026, 90 days after the v26.0 release, this deprecation will apply to all Marketing API versions.

The Meta Business SDK v26 release will be published shortly after the release of Graph API v26. This release will include dependency upgrades, Conversions API Parameter Builder integration, new API features, and deprecation of the Commerce Order Management API and several legacy protocol features.

The Business SDK is now integrated with open sourced Conversions API Parameter Builder. You can leverage this new integration to improve the quality of your Conversions API integration. Key features: Auto-generates (gated by preference set by advertisers) and enhances parameters fbc, fbp, event_source_url, referrer_url, client_ip_address and automatic PII normalization/hashing for supported languages, see more here. The Commerce Order Management API (47 endpoints) is fully deprecated with no replacement. The Instagram Explore Feed ad placement is removed and returns errors if specified. Messenger Stories placement is silently removed from messenger_positions. Ads in WhatsApp Status gain new capabilities including identity spec, carousel up to 10 cards, and offsite-conversion optimization.

As part of our 2-year deprecation schedule for Platform SDKs, please note the upcoming deprecations and sunsets:

• Sept, 2026: Facebook Platform SDK v20.0 will be deprecated
• Jan, 2027: Facebook Platform SDK v21.0 will be deprecated

As part of Facebook's versioning schedule for Graph API, please note the upcoming deprecations:

• September 24, 2026: Graph API v20.0 will be deprecated and removed from the platform.
• January 21, 2027: Graph API v21.0 will be deprecated and removed from the platform.

To avoid disruption, migrate all calls to the latest API version.