NEWS · NOVEMBER 5, 2026 · ADVERTISING

Meta ships Graph and Marketing API v27.0: AI disclosure editing and device targeting broadened by default

In a developer blog post dated November 4, 2026, Meta released Graph API v27.0 and Marketing API v27.0. Apps can now add or remove the AI-generated disclosure while editing a post, and eligible new Sales ad sets aimed at particular mobile devices or operating systems get broader reach switched on by default.

01 · WHAT HAPPENED?

One release: AI disclosure edits, restricted legacy features and new ad defaults

The Meta for Developers post dated November 4, 2026 says Graph API v27.0 and Marketing API v27.0 are available, and Social Media Today covered the changes on November 5. The notes split into two areas. On the Graph API side they cover post editing, older request formats and one Page Insights metric. On the Marketing API side they cover a device targeting default, Product showcase, the catalog endpoint and Lookalike audiences.

The post also covers Meta Business SDK v27, which it says will be published shortly after Graph API v27.0. The SDK will add phone OTP verification to lead forms. A phone_otp_verification_type setting will make verification required, optional or disabled, with the optional choice available only to eligible ad accounts.

02 · DETAILS

What changed in Graph API and Marketing API, item by item

In the Graph API, the post edit endpoints take a new optional is_ai_generated parameter. Passing true adds the AI-generated disclosure and false removes it, and older versions are unaffected. As of November 4, 2026, new apps are barred from multi-ID requests, date and time formatting, HTTP method override, field aliases, JSONP callbacks or async batch requests, and existing apps cannot start new uses. Multi-ID requests and date formatting were already deprecated in v26.0, while the other features are deprecated in v28.0. The Page Insights metric total_video_consumption_rate is no longer returned on any Graph API version from early November 2026, with no direct replacement. Graph API v21.0 is removed on January 21, 2027 and v22.0 on May 20, 2027.

In the Marketing API, eligible new Sales ad sets aimed at particular mobile devices or operating systems get "Reach more people across other mobile devices" switched on when the device field is omitted (the Mobile App conversion location and Special Ad Categories are excluded). A device value of 0 restricts delivery to the devices that were targeted, and existing ad sets do not change. For other versions the default arrives about 90 days later, around February 2027, with the date still to be confirmed. When Meta has high confidence that a catalog product set matches the ad, it can turn on Product showcase for ads built from creatives with no Product showcase settings, and setting enroll_status to OPT_OUT disables it. The catalog /batch endpoint stops working on v27.0 and above in favor of items_batch. On v27.0, creating a Lookalike audience with country or location_spec is rejected, and the remaining versions follow about 90 days later; such audiences now use the locations set in the ad sets that target them, and existing audiences keep running.

03 · WHY IT MATTERS

Defaults can quietly shift delivery and cost

A broader device default and automatic Product showcase are two settings that can change delivery and cost behavior for teams that manage ads through the API. Both can take effect on newly created ad sets and ads without anyone pressing a button in the interface. Social Media Today also notes that businesses running campaigns through third-party tools should review their settings.

The legacy Graph API restrictions are a developer matter. The restriction holds on every Graph API version: new apps cannot use these features at all, and existing apps cannot add new uses. Integrations built on field aliases or async batch calls, which are deprecated in v28.0, need a migration plan. Any catalog connection that still calls /batch has to move to items_batch when it is upgraded to v27.0. We covered the changes in the previous release in our Graph API v26 article, which is a separate event.

04 · TÜRKİYE

The sources say nothing about Türkiye, so this section is commentary

Neither the Meta announcement nor the Social Media Today report mentions Türkiye. They give no information about ad accounts or agencies in the country, or about any local regulator. This section is therefore not a fact drawn from the sources but explicitly UNALSOFT commentary.

Our reading is that API versions are global, so the same release notes should apply to an account that runs ads or content from Türkiye. The practical work is simple. List which tools run on which API version, review Sales ad sets that target devices and ads created through the API, and check whether any catalog connection still calls /batch.

The UNALSOFT view

We read this release as a checklist rather than a software announcement. If your ads are built through a third-party tool or your own integration, confirm before moving to v27.0 that the device value and the Product showcase setting arrive the way you want them. Catalog and Lookalike requests also need testing against the new format. On the ad management side we treat that review as its own step in campaign setup. Because the sources carry no data about Türkiye, this article proposes no local conclusion.

Is someone checking the defaults on the ads you run through the API?

A short conversation is enough to review your tool connections and ad sets together before the move to v27.0.

Message on WhatsApp