Meta ships Graph API and Marketing API v27: what changes

On 4 November 2026, Meta for Developers announced Graph API v27.0 and Marketing API v27.0 with new capabilities, deprecations and breaking changes. It affects ad targeting, creatives, catalog integrations, lookalike audience creation and Page Insights metrics. There are also Graph API version retirement dates.

Key takeaways

• Announced on 4 November 2026: Graph API v27.0 and Marketing API v27.0 bring new capabilities, deprecations and breaking changes.
• Marketing API v27 defaults: cross‑device reach may turn on for eligible new Sales ad sets unless device = 0; Product showcase can auto‑enable (opt‑out available).
• Catalog: /{catalog-id}/batch is deprecated and does not work on v27+; use /{catalog-id}/items_batch instead.
• Lookalike audiences: location fields in lookalike_spec are rejected on v27+, with delivery locations inherited from the ad set.
• Graph API: new is_ai_generated on post edit; total_video_consumption_rate removed; legacy features restricted; v21 retires 21 January 2027, v22 retires 20 May 2027.

What Meta announced and who is affected

On 4 November 2026, Meta for Developers launched Graph API v27.0 and Marketing API v27.0. The release introduces new capabilities alongside deprecations and breaking changes that can affect integrations and live campaigns across Facebook and Instagram. Teams building or maintaining B2B advertising stacks—catalogues, lookalike audiences, performance dashboards and Page tooling—should review changes promptly.

Highlights include default behaviour shifts in mobile device targeting for Sales ad sets, optional automatic activation of Product showcase in ads, a deprecated Catalog endpoint, and stricter rules for creating Lookalike audiences. On the Graph side, developers can now manage an AI‑generated self‑disclosure flag when editing Page posts, while a long‑standing video metric is being removed.

Meta also shared retirement dates: Graph API v21.0 is removed on 21 January 2027 and v22.0 on 20 May 2027. If your stack depends on older versions, plan upgrades and verification. ARTIC tracks these windows to reduce risk for B2B advertisers and marketing teams.

Marketing API v27: campaign‑impacting changes

• Cross‑device reach default: Starting in v27.0, new eligible Sales ad sets that target specific mobile devices or operating systems will have “Reach more people across other mobile devices” turned on when you omit the individual device setting. To keep delivery restricted to your specified devices/OS, set device to 0. Existing ad sets are not changed, and the setting is unavailable for the Mobile App conversion location and Special Ad Categories. Meta plans to extend this default to all versions approximately 90 days later (February 2027), date to be confirmed.

• Product showcase: From v27.0, Meta may automatically enable Product showcase (product_extensions) on ads whose creatives lack explicit Product showcase settings, when there is a high‑confidence match to a product set in your catalogue. You can opt out by setting product_extensions.enroll_status to OPT_OUT in your creative features spec.

• Catalog batch endpoint: The /{catalog-id}/batch endpoint is deprecated; use /{catalog-id}/items_batch instead. Applications may break on v27+ if not updated. Support continues on v26.0 and earlier until those versions are dropped.

• Lookalike audiences: On v27.0+, POST /act_{ad-account-id}/customaudiences rejects lookalike_spec that includes country or location_spec. Lookalike audiences inherit delivery locations from the targeting in your ad sets.

Graph API v27: AI disclosure, video metric removal and legacy limits

• AI‑generated disclosure on post edit: With v27.0, POST /{post-id} and POST /{page-post-id} accept an optional Boolean is_ai_generated when editing a Page post. Set true to add the disclosure, false to clear it, or omit to preserve the current value. Older Graph API versions do not change.

• Page Insights change: The total_video_consumption_rate metric will no longer return data starting in early November 2026 on any Graph API version. There is no direct replacement. Remove it from requests and verify dashboards continue to work.

• Legacy features restricted: From 4 November 2026, new apps cannot use, and existing apps cannot introduce new use cases for, legacy features including multi‑ID requests, date/time formatting, HTTP method override, field aliases, JSONP callbacks and asynchronous batch requests, across all Graph API versions. The remaining features will be deprecated in Graph API v28.0.

• Version retirements and SDK: Graph API v21.0 is removed on 21 January 2027; v22.0 on 20 May 2027. The Meta Business SDK v27 release will follow shortly after the v27 API release, aligning interfaces with the new versions.

B2B impact: targeting, creatives, catalogues and reporting

• Targeting and reach: If you create new Sales ad sets that segment by device/OS and you omit the device setting, Meta may expand delivery to other devices by default to improve performance. Where your B2B funnel requires strict device control (e.g., compatibility tests), explicitly set device = 0.

• Creatives and catalogue use: With Product showcase potentially turning on automatically, creatives may display closely matched products from a specific product set. If you prefer full manual control, opt out via product_extensions.enroll_status. For complex B2B catalogues, validate mappings and previews thoroughly. Learn more about B2B paid media strategy in our overview of Paid Media for B2B.

• Catalog API reliability: Calls to /{catalog-id}/batch will fail on v27+, so migrate to /{catalog-id}/items_batch and end‑to‑end test create/update/error flows. If you manage Meta Ads across markets, see our page on Meta Ads for B2B.

• Audiences and reporting: Remove location fields when creating Lookalike audiences; rely on ad set locations. Drop total_video_consumption_rate from ETLs and BI. For AI editorial workflows, align processes with the new is_ai_generated flag and revisit our guide to using AI in digital marketing.

What to do now: urgent checklist and validation plan

• Mobile targeting: For new Sales ad sets with device/OS segmentation, decide whether to allow the new default expansion or set device = 0 to keep restrictions. Document the policy in your playbooks.
• Product showcase: Audit creatives lacking Product showcase settings. If you prefer manual control, set product_extensions.enroll_status = OPT_OUT and validate previews.
• Catalog migration: Locate any calls to /{catalog-id}/batch and switch to /{catalog-id}/items_batch. Run load/error tests and update internal docs.
• Lookalike creation: Remove country and location_spec from lookalike_spec in all creation flows. Update forms, validation and libraries accordingly.
• Reporting and dashboards: Remove total_video_consumption_rate from queries, ETLs and visualisations. Regression‑test dependencies.
• Page post tooling: If you edit Page posts via API, incorporate is_ai_generated where relevant and align editorial policies with AI‑disclosure rules. See our perspective on AI for digital marketing.
• Broader integration QA: Re‑validate Conversions API (CAPI) event mappings, objectives, permissions and webhooks when upgrading SDKs or API versions, even if not explicitly changed in v27. Schedule a focused Paid Media audit to retest audiences, catalogues and reporting across environments. ARTIC can help teams structure this verification.

Frequently asked questions

When did Meta release Graph API v27.0 and Marketing API v27.0?

Meta for Developers announced both on 4 November 2026. From that release, new capabilities, deprecations and default changes apply that can impact integrations and campaigns.

What happens to /{catalog-id}/batch on v27+?

The /{catalog-id}/batch endpoint is deprecated and does not work on v27.0 and later. Migrate to /{catalog-id}/items_batch. It continues to work on v26.0 and earlier until those versions are dropped.

Can I still set a location when creating Lookalike audiences?

Not on v27.0+. The country and location_spec fields in lookalike_spec are rejected. Lookalike audiences deliver to the locations selected in your ad sets. Existing Lookalikes and ads targeting them continue unchanged.

Which Page Insights video metric is being removed?

The total_video_consumption_rate metric stops returning data starting in early November 2026 on all Graph API versions. There is no direct replacement, so remove it from requests and ensure dashboards function without it.

Are your campaigns up to date?

ARTIC is a Google Premier Partner and Meta Business Partner. We review your accounts with a paid media audit and run Google Ads and Meta Ads campaigns focused on B2B leads.

Sources

• https://developers.facebook.com/blog/post/2026/11/04/introducing-graph-api-v27-and-marketing-api-v27/

Informative article with the sources linked, up to date on the publication date.