Meta released Graph API v27.0 and Marketing API v27.0 on November 4. On the new version, ads can pick up Product showcase automatically, and new eligible Sales ad sets with device targeting can deliver beyond the devices you chose unless your integration opts out. The device default and a new lookalike rule reach every API version around February 2027.
Two defaults that change what runs
Product showcase, called product_extensions in the API, may now be switched on when you create ads whose creatives carry no Product showcase settings. Meta says it does this only when it has high confidence that a product set in your catalog matches the ad, so an ad built without catalog products can end up showing them. Versions before v27.0 do not change.
The second default affects delivery. New eligible Sales ad sets that target specific mobile devices or operating systems now have "Reach more people across other mobile devices" on whenever the device field is omitted. Meta can then serve other devices and operating systems when it expects better performance. Existing ad sets are untouched, and the setting is unavailable for the Mobile App conversion location and Special Ad Categories. About 90 days after launch, the default applies on all versions, whether or not your tool has upgraded.
What stops working
Several calls now fail or return nothing. The dates differ, so check each one against your stack.
- /{catalog-id}/batch no longer works on v27.0. Move to /{catalog-id}/items_batch. The old endpoint survives on v26.0 and earlier until v26.0 support ends.
- New lookalikes are rejected if lookalike_spec contains country or location_spec, on v27.0 now and on all versions about 90 days later. Meta says these fields had no effect, and existing lookalikes keep running.
- The total_video_consumption_rate metric stops returning data on all versions in early November, with no direct replacement.
- New apps can no longer use six legacy Graph API features, including field aliases and asynchronous batch requests. The remaining ones end with v28.0.
- Graph API v21.0 is removed on January 21, 2027, and v22.0 on May 20, 2027.
Who this reaches, and what Meta left open
Anything that talks to Meta through code is in scope: agency buying tools, catalog sync platforms, reporting dashboards and in-house scripts. If you only work in the Ads Manager interface, the post does not tell you whether the same defaults apply there, as PPC Land points out.
Meta also does not define "high confidence" or give figures for how much delivery shifts to other devices. PPC Land notes that the post describes no breakdown showing where expanded impressions went. That makes the opt-out decision a judgment call rather than something you can read from a report.
What to do this week
Ask whoever maintains your tools which API version they run and when they plan to move. Most of the risk sits at the upgrade: a catalog tool that moves to v27.0 loses /batch in the same step, and an integration written before the device setting existed never sends that field, so its silence now means expansion.
If your device targeting is deliberate, for example iOS-only offers or app-store-specific landing pages, set device to 0 explicitly. To keep creatives as built, set degrees_of_freedom_spec.creative_features_spec.product_extensions.enroll_status to OPT_OUT. Fix both before February rather than after a Q1 launch goes out with different delivery.
What it means for you
- Set device to 0 on new Sales ad sets where device targeting matters.
- Opt out of Product showcase if ads must show only the creative you built.
- Migrate catalog syncs to /items_batch before upgrading to v27.0.
- Remove location fields from lookalike calls and the retired video metric from dashboards.
Sources
- Meta for Developers: Introducing Graph API v27.0 and Marketing API v27.0
- PPC Land: Meta's API v27 may add catalog products to new ads by default
