Today, we are releasing Facebook Graph API v11.0 and Marketing API v11.0. As a part of this release, we have created this blog post to highlight broad-reaching changes that will impact parts of our developer community. These changes include announcements and product updates, reminders from prior launches, and notifications on large-scale deprecations that may affect your application(s)’ integration with our platform.
For a complete list of all changes and their details, please visit our changelog.
On May 6, 2021, Facebook began expanding the data access level functionality introduced in Graph API v8.0 to Consumer apps. This rollout will complete in late June / early July. This model makes testing new permissions and features easier, since anyone with a role on the app can grant it any unapproved permission or feature without having to switch to Development mode or having to use a test app.
This functionality will launch for all newly created Consumer apps in the coming weeks. Note that as part of this change, new Consumer apps must be set to Live Mode and the public_profile permission set to Advanced Access before users who do not have a role on the apps can authenticate using Facebook Login. The public_profile and email permissions are automatically approved for Advanced Access but are set to Standard Access by default.
Please refer to our access levels developer documentation to learn more about how access levels affect Consumer apps.
Starting June 8, 2021, the Instagram Basic Display API will now support versioning. You may now perform versioned calls on all 'graph.instagram.com' endpoints using the same versioned request protocol as the Facebook Graph API.
Also, as part of this release, Instagram introduces app-scoped IDs (ASIDs), which are user IDs unique to each app and user pair.
Starting June 8, 2021, the oEmbed product has been replaced with a new oEmbed Read feature. Developers who have implemented Facebook oEmbed or Instagram oEmbed must be approved by App Review for the new oEmbed Read feature by September 7, 2021 or their oEmbed integrations will be revoked. New apps that require access may submit for review during app creation or any time after.
Changes to the Audience Deletion API
As part of Facebook’s ongoing effort to improve how advertisers create and manage their audiences, Custom Audiences (except Customer List Custom Audiences), Lookalike Audiences, or saved audiences that have not been used in active ad sets for over two years will be automatically deleted.
For Customer List Custom Audiences, Facebook will continue to store and delete these in accordance with advertisers’ instructions. If an advertiser chooses not to use an audience tagged as an “Expiring Audience” within the allotted time frame, Facebook will treat this as an instruction to delete the audience.
Additionally, moving forward, any Custom Audience (except Customer List Custom Audiences), Lookalike Audience, or saved audience which has not been used in an active ad set for over two years will automatically be tagged as an “Expiring Audience” and will be auto-deleted 90 days after being identified as an expiring audience.
This change will be rolled out:
Deleted Facebook Page Based Audience Deletion
As part of our ongoing effort to improve how advertisers create and manage their audiences, we are making an update that affects Engagement Custom Audiences, associated Lookalike Audiences and saved audiences created from a deleted Facebook page. We expect impact for most advertisers to be minimal.
Starting September 08, 2021, for advertisers using the Marketing API: Engagement Custom Audiences (page, video, lead form, event, instant experience, shopping), associated Lookalike Audiences, and saved audiences that were created using a deleted Facebook page will be marked with a “warning status” with a 30 day grace period before being automatically deleted. New campaigns can continue to be created and scheduled up until this cut-off date.
Additionally, moving forward, after September 8, 2021 advertisers will not be able to create these Engagement Custom Audiences types or Lookalike Audiences from deleted Facebook pages.
Starting June 08, 2021, Facebook is releasing Platform SDKs v11.0. With this release, we are deprecating v9.0 and introducing several feature updates. Please visit the iOS SDK Changelog, Android SDK Changelog and Unity SDK Changelog to learn about important upcoming changes to these SDKs. Additionally, Facebook has posted a separate blog highlighting these updates.
Starting June 8, 2021, in an effort to reduce risk on our platform, we are further specifying the permissible use cases for both user_likes and user_posts. If your app currently has access to user_likes and/or user_posts, and your use case is not aligned with the updated permissible use case(s), you will have until September 6, 2021 to make any necessary changes on your app, to account for it no longer being eligible to access one or more of these permissions. Beginning September 6, 2021, apps with access to these permissions that don’t fall under the new permissible use cases will be subject to enforcement action.
If you're unsure whether your use case aligns with these updates, please proactively submit for App Review before September 6, 2021. Apps' whose use case does align with the updated permissible use case(s) will not be impacted by this change.
Starting June 8, 2021, for API v11.0+, Facebook is implementing several changes to how you engage with product group and catalog:
Starting on June 8, 2021, for API v11.0+, to eliminate inconsistencies between surfaces and remove confusion around availability and inventory, Facebook will add the quantity_to_sell_on_facebook field as a replacement for the inventory field.
The quantity displayed by this new field will not be reduced by reserved inventory, defined as inventory temporarily reserved when buyers add an item to their cart. We will continue to support the ‘inventory’ field for the near term. However, we recommend that you use the new ‘quantity_to_sell_on_facebook’ field instead.
On October 2, 2020, Facebook announced the new Page experience as a way for public figures, businesses and others who want to build and connect with an audience to manage their professional presence on Facebook. All classic Pages are currently being transitioned over to the new Pages experience in a gradual rollout. We are planning to complete the rollout within the next few months, and classic Pages will eventually be deprecated.
Please see the developer documents to learn how to determine whether a Page has been transitioned yet and visit the Help Center for questions.
On June 1, 2021, Facebook launched a new Platform Live Status page to increase transparency and proactive communication with external developers using Facebook platform products. This new Facebook for Business Status page will serve as the single location for checking server health for platform and business products offered by Facebook, including Ads, WhatsApp Business API, Facebook Developer Platform, and more.
Originally announced March 30, 2021, Facebook is in the process of deprecating Facebook Analytics (FBA). After June 30, 2021, the Facebook Analytics tool will no longer be available. Additionally, we are deprecating the Dashboard Plugin for Marketing API.
While the individual Facebook Analytics tool is going away, these alternatives are still available:
Starting June 8, 2021, Graph API v11.0+ will no longer support businesses' abilities to send Airline Templates. Deprecation for the prior Graph API versions (v10.0 and below) will occur 6 months after the announcement of this change on December 6th, 2021.
We recommend businesses send boarding passes and check-in templates as images, consistent with how companies typically send these notifications in other channels.
Starting June 8, 2021, if you are using Offer Ads API, you are encouraged to use Facebook Ads instead, for building your promotions and discounts. Offer Ads API endpoints will be deprecated upon the release of Graph and Marketing API v12.0 in the fall. Though we are not officially deprecating the endpoint on the launch of v11.0, we will begin transitioning support that may cause a sub-optimal experience if you continue to use this endpoint.
Starting June 8, 2021, for Graph API v11.0+, the “id” field for all comments returned in requests using the Page Public Content Access feature will be removed. Note: nested requests will still be supported for these objects.
This change will apply to all other active API versions (v10.0 and below) on September 6, 2021.
Starting June 8, 2021, access to the following endpoints is temporarily limited to apps that have queried them within the last 30 days:
As part of Facebook’s Graph API and Marketing API, please note the upcoming deprecations:
To avoid disruption to your business, we recommend migrating all calls to the latest API version that launched today.
As part of our Marketing API versioning schedule, please note the upcoming Marketing API version deprecations:
To avoid disruption to your business, we recommend migrating all calls to the latest Marketing API version that launched today. (Visit the changelog for more details).
As part of our Graph API versioning schedule , please note the upcoming Graph API version deprecations listed below: