Facebook's API Can Now Add or Remove the AI Label on Page Posts. What Graph API v27.0 Means for Automated Pages in 2026
Publisher in a Box editorial teamUpdated
Key takeaways
Graph API v27.0, released November 4, 2026, lets apps add or clear the AI label while editing an existing Facebook Page post, through the optional `is_ai_generated` field.
The rule did not change: Meta requires the label on photorealistic video and realistic-sounding audio that was digitally generated or altered, before you share it, and not on images.
Clearing a required label is a risk, because Meta says there may be penalties for content that should have been labeled and was not.
Label at publish whenever you can, use the edit route to fix missed posts right away, and keep any label removal to one post at a time with a person checking.
Check your other tools too, because legacy request features, the `total_video_consumption_rate` metric and Graph API v21.0 and v22.0 are all on their way out.
Table of Contents
On November 4, 2026, Meta released Graph API v27.0, and one line in it matters to anyone who runs Facebook Pages through software. Apps on the new version "can add or remove a post's AI-generated self-disclosure while editing the post," which means a scheduler, an automation workflow or an in-house tool can now set the AI label on a Page post without a person opening Facebook.
Some coverage framed this as a way to hide the AI label. Meta's own announcement is narrower than that, and the rule about when the label is required did not move at all. This guide covers what changed, what Meta still requires, and what an automated Page should check. Where we give our own reading or our team's experience, we say so.
What exactly changed in Graph API v27.0?
The change is one optional field on the endpoints an app uses to edit a Page post. Meta's developer blog says the `POST /{post-id}` and `POST /{page-post-id}` endpoints "now accept the optional Boolean `is_ai_generated` parameter." Setting it to true adds the disclosure, setting it to false clears it, and leaving it out keeps whatever the post already had.
Two details in Meta's wording matter. The field arrives "while editing an existing Page post," so the announcement describes posts that already exist. And it launches with v27.0 only, because Meta says "older API versions remain unchanged," so a tool on an older version gets nothing new.
We also read the v27.0 Page Post reference, which lists `is_ai_generated` among the parameters for updating a Page post. The changelog link in Meta's announcement returned a page not found error when we checked it on November 7, so the blog post and the reference page are the primary sources we relied on.
November 4, 2026
The release date of Graph API v27.0, the first version that lets an app add or clear the AI label while editing a Facebook Page post. Older versions did not change.
Source: Meta for Developers, Introducing Graph API v27.0 and Marketing API v27.0
Why does this matter if your Page runs on automation?
Until now, the AI label on Facebook was mostly a manual step. Meta's help page describes it inside the Facebook composer, where you click "AI label off" and then turn on "Add AI label," with matching steps for reels and stories. That works for a person posting by hand, but a Page that publishes through a scheduler or an automated workflow never passes through that screen.
Our own guidance to customers has said the same thing since October. In our team's experience, most scheduling tools still do not offer the AI label, so we have told publishers to post realistic AI video directly in Facebook, where they can turn the label on. The v27.0 change gives tool makers a documented route to set the label on an existing post, which is the first step toward closing that gap.
A Page that runs AI voiceover reels through an automated pipeline has been choosing between publishing by hand and publishing without the label, and the second choice carries risk. Our guide to Facebook Page automation without shipping slop covers automated production in more depth.
When does Facebook require the AI label?
Facebook requires the label for realistic video and realistic audio, and not for images. The Facebook help page, read on November 7, 2026, says "Meta requires you to label content you share that has photorealistic video or realistic-sounding audio that has been digitally generated or altered, including with AI." It adds that "you must label the content before you share it."
Meta's examples of content that needs the label include "A reel narrated with a realistic AI-generated voiceover" and "A song created using AI-generated vocals." Its examples of content that does not include "Video of an outdoor landscape, created in a style resembling a cartoon" and an image, because "Meta does not require you to label images that have been created or modified with AI." Images can still be labeled automatically when Meta's systems detect AI signals in the file.
The help page also warns that "There may be penalties if you do not label content as required." Meta's Transparency Center states the same rule, saying Meta requires disclosure "using our AI-disclosure tool" for photorealistic video or realistic-sounding audio, and that "we may apply penalties if they fail to do so."
The API changed how the label can be set. It did not change when the label is required, and that second question is the one that carries penalties.
Does the new field let you remove a required label?
Technically, yes, and that is exactly why the field needs a rule around it inside your operation. Setting `is_ai_generated` to false clears the disclosure, and Meta's announcement does not limit when an app may do that. The requirement on the help page still applies to the content, whatever the API allows.
In our reading, the false setting exists to correct mistakes, such as a label added to a post that never contained realistic AI video or audio. Clearing the label from a reel with a realistic AI voiceover would leave content that Meta says must be labeled without its label, which is the situation the help page says may bring penalties. We would treat any tool that clears labels in bulk as a risk, not a feature.
It also helps to be clear about what the label does not do. Our guidance to customers says the label is a disclosure only and does not make content original. In our team's experience, images and reels with the AI label can still be monetized, and the label by itself does not affect reach or engagement. Originality is judged separately, which our guide to the limited originality flag covers in detail.
Should you label posts at publish or fix them later?
Label at publish whenever you can, because that is what Meta's rule asks for. The help page says the label goes on "before you share it," while the v27.0 field is described for editing a post that already exists. An edit after publishing is a correction, and a correction still leaves the post live without its label for some period of time.
So the order for an automated Page is simple. If your tool can label at publish, use that. If it cannot, publish realistic AI video directly in Facebook with the label on. Use the v27.0 edit route to fix missed posts and to clear labels added by mistake.
When a missed label is found, fix it right away rather than scheduling the fix for later. That follows the same principle we give for violations in general, which is to act quickly instead of waiting on a window. If Meta has already flagged a post, our limited originality guide sets out the order we recommend.
What else in v27.0 touches a publisher's tools?
Several other changes reach the tools publishers use every day. If you pay for a scheduler, a dashboard or an automation workflow, ask whoever maintains it about these.
Legacy request features. Starting November 4, 2026, new apps cannot use multi-ID requests, date and time formatting, HTTP method override, field aliases, JSONP callbacks or asynchronous batch requests, and existing apps "cannot introduce new use cases for them." Meta says the remaining features will be deprecated in Graph API v28.0.
A video metric is going away. Meta says that "Starting in early November 2026, the `total_video_consumption_rate` video insights metric will no longer return data on any Graph API version," and that "There is no direct replacement." A dashboard that shows it will go blank or break.
Old versions are being removed. Graph API v21.0 is removed on January 21, 2027, and v22.0 on May 20, 2027. A tool still on those versions has to move, and it only gains the AI label field once it reaches v27.0.
None of these changes affect how Facebook pays you. They affect whether your tools keep working, and for a Page that earns through Facebook Content Monetization, a posting tool that silently fails costs output.
What should an automated Page do this week?
We would do this now rather than wait for each tool to announce an update, because the requirement already applies to every reel you publish.
1. List every tool that publishes or edits posts on your Page. Include schedulers, workflows, agencies and admins, and note each tool's Graph API version if the vendor will say. 2. Find your realistic AI video and audio. Look for reels with AI voiceovers, AI presenters, AI vocals or realistic AI scenes. Those are the posts Meta's rule covers, and images are not. 3. Check the label on those posts. Open them and confirm the AI label is on. Where it is missing, add it now, by hand or through a tool on v27.0. 4. Set a rule for clearing labels. Decide who may set `is_ai_generated` to false and when. In our view, that should be a person checking one post at a time, never a bulk action. 5. Ask each vendor about labeling at publish. The edit route fixes posts after they go live. A tool that can label at publish is the better answer, and until yours can, post realistic AI video directly in Facebook. 6. Check your reporting. If a dashboard uses `total_video_consumption_rate`, expect it to stop returning data and plan which metric you will watch instead.
Meta's labeling rule is a platform policy, not a statement about any law, and some places have their own rules on disclosing AI content. Nothing here is legal advice, and if your business publishes a lot of AI video or audio, talk to a lawyer in your own country.
Where to go from here
If you want your Page's daily content produced without a team, the Facebook Automation Machine rewrites captions in your voice and frames branded posts, ready for you to schedule, on your own stack for a one-time $397. Facebook keeps changing its rules, and we keep updating the Automation Machine as it does. For the automation and the strategy together, the Facebook Monetization Suite adds the full PIB playbook for $499.
Frequently asked questions
Can a scheduling tool add the AI label to a Facebook post now?
Graph API v27.0, released November 4, 2026, lets an app "add or remove a post's AI-generated self-disclosure while editing the post" on a Facebook Page. Whether your tool offers it depends on whether its maker has moved to v27.0 and built the feature, so ask your vendor.
Does the AI label hurt reach or earnings on Facebook?
Meta does not say the label reduces reach. In our team's experience, images and reels with the AI label can still be monetized, and the label by itself does not affect reach or engagement. The label is a disclosure, and originality is judged separately.
Do I have to label AI images on Facebook?
No. Meta says it "does not require you to label images that have been created or modified with AI." Images can still be labeled automatically when Meta detects AI signals, and labeling an AI image yourself is allowed.
Which Facebook posts need the AI label?
Posts with photorealistic video or realistic-sounding audio that was digitally generated or altered, including with AI. Meta's examples include a reel narrated with a realistic AI voiceover and a song with AI-generated vocals.
Can I use the API to remove an AI label?
The field can clear the label by setting it to false, but Meta's requirement still applies to the content. Clearing the label from a reel that needs it leaves content Meta says must be labeled without one, and Meta says there may be penalties.
Sources
Meta for Developers, Introducing Graph API v27.0 and Marketing API v27.0, November 4, 2026, read November 7, 2026, developers.facebook.com
Meta for Developers, Page Post reference, v27.0, read November 7, 2026, developers.facebook.com
Facebook Help Center, Label AI content on Facebook, read November 7, 2026, facebook.com
Meta Help Center, How to identify AI content on Meta products, read November 7, 2026, meta.com
Meta Transparency Center, Misinformation, read November 7, 2026, transparency.meta.com
Social Media Today, Meta adds new capabilities to Graph and Marketing API, November 5, 2026, socialmediatoday.com
See more from Publisher in a Box in your Google results
The team behind 300M+ managed followers. We help publishers scale traffic, revenue, and audience across Facebook, Google Discover, and syndication networks.
