Meta today released Graph API v27.0 and Marketing API v27.0. On the new version, two features switch on by default for new ads, lookalike audience requests that carry location fields are rejected, and the catalog batch endpoint stops working. Six legacy Graph API features are also blocked for new apps on every version. The post on the Meta for Developers blog, written by Ayyad Farah and Manjari Jain, confirms that Graph API v21.0 will be removed from the platform on January 21, 2027 and v22.0 on May 20, 2027.

The changes affect anything that talks to Meta's advertising and Pages systems through code: agency buying tools, catalog management platforms, social media dashboards and in-house scripts. Two of the Marketing API changes start on v27.0 today and reach every remaining version in about 90 days. The post describes only the API, and it does not say whether the same defaults apply in Ads Manager.

In Short

Meta has updated the systems that software uses to buy ads and manage Facebook Pages, and some new settings now switch themselves on unless someone switches them off. Businesses that run ads through their own tools or an agency's software could see catalog products added to their ads, or ads shown on phones they did not choose. Several older ways of sending requests to Meta also stop working, so tools that have not been updated may start returning errors.

What changes, and when

The release mixes immediate breaks with staged ones. According to Meta, the timing for each change is as follows:

Change Where it applies Timing
Product showcase may switch on for new ads Marketing API v27.0 Today; older versions unchanged
Reach more people across other mobile devices on by default New eligible Sales ad sets v27.0 today; all versions about 90 days later, date to be confirmed
Location fields rejected in lookalike_spec New lookalike audiences v27.0 today; all versions about 90 days later, date to be confirmed
/{catalog-id}/batch stops working Catalog API v27.0 today; works on v26.0 and earlier until v26.0 support ends
Six legacy features closed to new apps All Graph API versions Today; unsupported for all apps on v28.0
total_video_consumption_rate stops returning data All Graph API versions Early November 2026
is_ai_generated on post edits Graph API v27.0 Today
Graph API v21.0 and v22.0 removed Platform January 21, 2027 and May 20, 2027

Ninety days from today is February 2, 2027, by PPC Land's calculation. Meta's summary gives "February 2027" for the device setting and leaves the exact day unconfirmed.

Product showcase becomes a default

According to Meta, from v27.0 the company may turn on Product showcase - called product_extensions in the API - when an advertiser creates ads whose creatives carry no Product showcase settings. Meta does not apply it everywhere. It acts "only when it has high confidence that a specific product set" in the advertiser's catalog matches the ad. In practice, an ad built without catalog products can show closely matched products from the advertiser's catalog, which Meta says requires no extra integration work.

The opt-out sits deep in the creative specification. Integrations that want the old behaviour set degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status to OPT_OUT. Meta's example:

"degrees_of_freedom_spec": {"creative_features_spec":
{"product_extensions": {"enroll_status": "OPT_OUT", "action_metadata":
{"type": "MANUAL"}}}}

The post names two representative affected endpoints: POST /{ad-account-id}/ads, which creates ads, and POST /{ad-account-id}/adcreatives, which creates ad creatives. It links to a page for previewing the product set Meta may use, and it states that "Versions before v27.0 do not change." Unlike the device and lookalike changes, Product showcase has no date for reaching older versions.

The summary at the top of the post calls the feature optional: "This is an optional feature." That is true in the narrow sense that an opt-out exists. On v27.0, though, the default for a creative without settings is that Meta may enable it.

The post leaves several things undefined. It does not say what "high confidence" means or how the match is measured. It does not list the placements where Product showcase appears, and it gives no performance figures. Nor does it say how an advertiser reading a creative back through the API would learn that Meta had switched the feature on.

The mechanism is familiar. In August 2025, Meta made dynamic media the default for new Advantage+ catalog ads created through the Marketing API from September 1, 2025, with full enforcement by October 20, 2025. Developers who wanted the earlier behaviour had to set enroll_status to OPT_OUT, the same field pattern used now. Last month PPC Land reported that Meta would turn on product browsing in existing ads on October 28 unless advertisers opted out, a separate feature that sends some people who tap an ad to an in-app product experience.

Device targeting widens unless set to 0

The second default concerns delivery rather than creative. According to Meta, from v27.0 new eligible Sales ad sets that target specific mobile devices or operating systems have Reach more people across other mobile devices switched on when the field targeting.targeting_automation.individual_setting.device is omitted. Meta can then deliver ads to people on other devices and operating systems "when that is likely to improve performance."

Keeping delivery to the devices and operating systems in the targeting requires setting device to 0. Existing ad sets are not changed. Meta says the setting is unavailable for the Mobile App conversion location and for Special Ad Categories, so ads in the housing, employment and financial products groups fall outside it, as do ad sets optimising for app conversions.

The practical effect is that an omission becomes a choice. An integration written before the setting existed never sends the device field. On v27.0, that silence now means expansion. About 90 days after today's launch, according to Meta, the same default applies to new eligible ad sets on every version, whether or not the integration has upgraded.

Meta does not define "eligible" beyond the two exclusions. The post gives no figures for how much delivery moves to other devices, and it does not describe any reporting breakdown that would show where expanded impressions went.

The setting lives in the targeting_automation object, which Meta has been filling with automation switches. With v26.0 in July, PPC Land reported that for new ad sets in housing, employment and financial products campaigns, the advantage_audience field had to be set explicitly to 1 or 0 when constrained. In August, some advertisers lost manual placement controls, with value rules capped at 90% bid cuts. Device targeting is another control over where ads run. For new Sales ad sets aimed at specific devices, it now defaults to Meta's judgement unless the integration sets it to 0.

Lookalike audiences lose location fields

From v27.0, POST /act_{ad-account-id}/customaudiences rejects any lookalike_spec that contains country or location_spec. According to Meta, no replacement field is needed. Lookalike audiences deliver to the locations selected in the audiences of the ad sets that use them, and Meta states that "These fields have no effect." On all remaining versions the rejection follows about 90 days after launch, with the date still to be confirmed.

The impact on running campaigns is limited by design: "Only new audience creation is affected; existing Lookalike audiences and the ads targeting them keep running unchanged."

The two descriptions in the post differ slightly. The summary says lookalike audiences "now inherit delivery locations from the ad sets that target them," which reads as a new behaviour. The detailed section says the fields already have no effect. The post does not say when location in the lookalike specification stopped shaping delivery. For integrations, the change is mechanical either way: a request that still sends either field fails on v27.0 today and on every version from early 2027.

The catalog batch endpoint stops on v27.0

The catalog change is the one most likely to produce errors without warning. According to Meta, /{catalog-id}/batch is deprecated, and applications should use /{catalog-id}/items_batch instead. The post says the change "affects advertiser businesses and agencies integrating with the Catalog API" - the software that keeps a retailer's catalog in sync with Meta, alongside or in place of a scheduled product feed upload. Meta states the risk directly: "Applications may break if they don't update their code to use /items_batch instead of /batch."

The timing works differently from a calendar deadline. On v27.0 the old endpoint no longer works from today. On v26.0 and earlier it continues "until support for v26.0 is dropped," and the post gives no date for that. The break therefore arrives at the moment an integration upgrades. A catalog tool that moves to v27.0 to pick up new features loses /batch in the same step, and Meta links a migration guide for the move to /items_batch.

Six legacy Graph API features closed to new apps

The broadest change applies to all versions at once. According to Meta, starting today new apps cannot use six legacy features, and existing apps cannot introduce new use cases for them. "This applies across all Graph API versions." The six are:

  • Multi-ID requests (ids), which retrieve several objects in one call, for example ?ids=[id1,id2]
  • Date/time formatting (date_format), which changes how dates appear in responses, for example date_format="U"
  • HTTP method override (method), which changes the method of a non-batch request, for example ?method=delete
  • Field aliases (.as(...)), which rename fields in a response, for example picture.width(100).height(100).as(picture_small)
  • JSONP callbacks (callback), which wrap a response in a named JavaScript function, for example ?callback=MyJSFunction
  • Asynchronous batch requests (asyncbatch), which submit requests for background processing and return results later

Meta's example for the asynchronous batch feature is a DELETE call on a marketplace business's managed partner businesses.

Apps already using these features keep them for now. "Existing apps may continue their current use of those features on supported older versions," according to Meta. The remaining features will be deprecated in Graph API v28.0 and will not be supported for v28.0 requests, including from apps already using them. The post gives no date for v28.0.

Two of the six are not new deprecations. Meta notes that multi-ID requests and date/time formatting "were already deprecated in Graph API v26.0." When v26.0 launched on July 29, PPC Land reported that requests using date_format or root-level /?ids= batching returned a parameter error on v26.0, and that the retirement would extend to all versions on October 27, 2026. Today's post lists both features again and does not mention the October 27 date.

A video metric disappears with no replacement

Page Insights loses another metric. According to Meta, the total_video_consumption_rate video insights metric is being deprecated because its inputs - 3-second video viewers and video Reach - were deprecated with Graph API v26.0 after being announced with v25.0. Starting in early November 2026, the metric will not be returned on any Graph API version. The affected endpoint is GET /{video-id}/video_insights. Meta's guidance is short: "There is no direct replacement."

The post is dated November 4 and gives only "early November" for the cut-off, so the metric may already be gone from some responses or may disappear within days. Dashboards and reports that chart it will show gaps with no like-for-like series to carry the trend.

The pattern is long-running. In December 2023, Facebook deprecated 89 Page Insights metrics effective March 14, 2024. In August 2025, Meta removed impressions and page fans from all API versions from November 15, 2025, with views replacing impressions. This time Meta names no successor.

AI-generated disclosure can be edited

One addition runs the other way. According to Meta, from Graph API v27.0 developers can add or remove a post's AI-generated self-disclosure while editing an existing Page post. The POST /{post-id} and POST /{page-post-id} endpoints accept an optional Boolean, is_ai_generated: true adds the disclosure, false clears it, and omitting it keeps the existing value. Meta calls it "This additive capability"; it launches with v27.0 today, and older versions remain unchanged.

The parameter works in both directions, so a disclosure set by mistake can be corrected, and a correct one can be removed. The post does not say whether clearing a self-disclosure has any effect on labels Meta applies through its own detection. It also covers Page posts, not ads.

Meta has applied AI labels to content on its platforms since 2024, when it set out its approach to labelling AI-generated images, video and audio. Disclosure in ads has been rare by at least one count. On October 22, Resemble AI reported that only 2 of 3,379 AI-flagged Meta ad files disclosed AI use in their ad copy, a separate surface from the organic posts the new parameter addresses.

SDK release: lead form verification and Burst inventory

Meta's Business SDKs - the client libraries that many developers use instead of writing raw API calls - will get a v27 release "shortly after the release of Graph API v27," according to the post. The SDK notes add changes that do not appear in the key dates list.

Lead forms gain phone one-time password verification through phone_otp_verification_type, which supports required, optional or disabled verification. "Optional verification is available only to eligible ad accounts," according to Meta. For advertisers running lead ads, the field adds a verification step that applies to the phone number a person submits. The post does not define which accounts are eligible for the optional mode or which markets the feature covers.

The meta_moment_maker_spec is deprecated for third-party apps. In the same paragraph, Meta says developers requesting Ads Burst or Ads Super Burst inventory should use product_type on reach and frequency predictions instead. Read together, the two sentences suggest the deprecated spec had been one route to that inventory, although the post does not say so directly. Meta announced Ads Super Burst on October 15, selling brands reserved windows of 3 to 24 hours with optional category exclusivity, so the API change arrives three weeks after the product.

The SDK notes repeat the device and Product showcase defaults, the catalog migration and the lookalike change. Under what Meta calls its "2-year deprecation schedule for Platform SDKs," Facebook Platform SDK v21.0 will be deprecated in January 2027 and v22.0 in May 2027.

Retirement dates and the release pace

The version deprecations match what Meta published in July. Graph API v21.0 "will be deprecated and removed from the platform" on January 21, 2027 - 78 days from today, by PPC Land's calculation - and v22.0 on May 20, 2027. With v26.0, PPC Land reported that v20.0 would be removed on September 24, 2026, with v21.0 following in January. The post lists retirement dates only for Graph API versions; it gives no separate schedule for Marketing API versions.

The gap between releases has narrowed. Meta introduced v23.0 on May 29, 2025, according to the post's related links. v24.0 followed on October 8, 2025, when it blocked creation of legacy Advantage+ shopping and app campaigns through the old APIs. v25.0 arrived on February 18, 2026, v26.0 on July 29, 2026 and v27.0 today. By PPC Land's count, that is 132, 133, 161 and 98 days between releases, so v27.0 came sooner after its predecessor than any of the previous three.

Google has moved further. In October it moved the Google Ads API to two releases a month starting with v26. Meta still ships versions a few months apart, but each one carries its own list of defaults and breaks, some of which reach older versions on their own timetable.

Why the defaults matter for marketers

For advertisers who buy through software, much of today's release changes behaviour by default rather than by request. If an integration sends nothing about Product showcase, Meta may enable it. If a device-targeted Sales ad set sends nothing about expansion, the expansion is on. In both cases Meta frames the change as a performance gain, and in both cases the post offers no data to support that claim.

More campaign building now happens in code, which raises the stakes of API defaults. Meta published an Ads CLI for developers and AI agents on April 29, 2026, opened its ads MCP server to any developer with a Meta app on July 16, and on October 26 added tools that let AI agents create apps through its developer MCP server. Today's post does not say whether those tools adopt v27.0 behaviour, or when.

The contract around automated changes is also shifting. On October 22, PPC Land reported that a new AI Features section in Meta's terms makes advertisers solely responsible for Meta's AI ad edits. A day later Meta pushed the revised terms back to November 20. Today's post does not say whether Product showcase counts as an AI feature under those terms. In June, REI said Meta had enrolled it in an AI personalization tool without its knowledge after an altered bicycle image ran in its ads. The episode showed how a default can go unnoticed until an ad has already run.

Developers face a stack of Meta deadlines. On October 21, Meta set October 13, 2027 as the date the WhatsApp Cloud API stops delivering marketing messages. Graph API v21.0 goes in January, the device and lookalike changes reach all versions around February, v22.0 goes in May, and v28.0, whenever it lands, ends the remaining legacy features for every app.

Timeline

Summary

Who: Meta, through a Meta for Developers blog post by Ayyad Farah and Manjari Jain. The changes affect developers, agencies, ad-tech vendors, catalog integrators and advertisers who create campaigns or manage Pages through Meta's Graph API, Marketing API and Business SDKs.

What: Graph API v27.0 and Marketing API v27.0. Meta may turn on Product showcase for new ads with no showcase settings. Reach more people across other mobile devices is on by default for new eligible Sales ad sets. Lookalike requests with country or location_spec are rejected, /{catalog-id}/batch stops on v27.0, and six legacy Graph API features are closed to new apps on all versions. total_video_consumption_rate stops returning data, and is_ai_generated can be set when editing Page posts. Graph API v21.0 and v22.0 are removed in January and May 2027.

When: Today, November 4, 2026, for v27.0. The metric removal is in early November 2026. The device and lookalike changes reach all versions about 90 days later, in February 2027, with the date to be confirmed.

Where: Meta's developer platform, covering ads on Facebook and Instagram, product catalogs, lead forms and Facebook Page posts, for every integration that calls the affected endpoints.

Why: Meta says the device expansion runs when it is likely to improve performance and that Product showcase needs no extra integration work. It retires the catalog and legacy features in favour of newer methods, and it drops the video metric because its inputs were deprecated. The post gives no performance data for either default, and the defaults apply to any integration that does not explicitly opt out.