Graph API v27.0, released November 4, lets apps add or remove the AI-generated self-disclosure on an existing Page post. Social Media Today read this as advertisers being able to hide disclosures, but Meta's developer post describes only Page post edits and never mentions ads. Here is what the change covers and where the gaps are.
What changed
Two post-edit endpoints, POST /{post-id} and POST /{page-post-id}, now accept an optional Boolean called is_ai_generated. Meta's rules for it are simple, and older API versions do not change.
- true adds the disclosure.
- false clears it.
- Leaving the field out keeps the existing value.
What Meta did not say
The developer post does not connect this field to ads, ad creatives, the Marketing API or Instagram. It does not name the permissions or roles needed to change a disclosure. It also leaves open what happens when a post promoted as an ad has its disclosure edited.
There is a second gap. Meta's labelling policy says "AI info" labels can come from industry-standard image indicators as well as from people disclosing AI use. The v27.0 post covers only the self-disclosure, so it does not tell you whether clearing that flag has any effect on a label Meta applied through detection. The v27.0 Page post reference also lists a second parameter, is_self_disclosed_as_ai_generated, with no explanation in the text we read.
Who it affects
The audience is anyone who edits Page posts through code: social scheduling tools, agency publishing dashboards and in-house scripts. Since this launched as a field on v27.0, nothing changes until an integration upgrades and starts sending it. The practical risk sits in the tool, because an integration that always sends a value can overwrite a disclosure, while one that omits the field leaves it alone.
Disclosure rules still apply separately. Meta has said advertisers must disclose in certain cases when they digitally create or alter a political or social issue ad. A field that clears a flag on a Page post does not change that obligation, and nothing in this release suggests it does.
What to do
Ask your tool vendors or developers whether they plan to expose is_ai_generated, and what the default will be. Make sure a move to v27.0 does not start sending false on every edit. Then set an internal rule on who may clear a disclosure and why, such as correcting a post that was wrongly flagged. Keep a log, since a cleared flag on content that really was AI-made is hard to explain to a client or to Meta later.
Do not plan around hiding AI labels on ads. Nothing Meta has published here supports that use.
What it means for you
- The field covers editing Page posts; Meta's post does not mention ads.
- Omit the field to keep a disclosure as it is; false clears it.
- Check that tools upgrading to v27.0 don't send false by default.
- Political and social issue ads keep their own disclosure duties.
Sources
- Meta for Developers: Introducing Graph API v27.0 and Marketing API v27.0
- Meta for Developers: Page Post reference, v27.0
- Meta: Our approach to labeling AI-generated content and manipulated media
- Social Media Today: Meta adds new capabilities to Graph and Marketing API
