Today, we are releasing Facebook Graph API v12.0 and Marketing API v12.0. Below are changes that will affect certain parts of our developer community. These include product updates and reminders, as well as notifications about large-scale deprecations.
To see a complete list and details of all changes, visit our changelog.
General Announcements and Updates
Conversions API: Expanding minimum callable version
Graph API Backwards Compatibility for Apps Created with One-Click Access Tokens Beginning with v12.0, newly created access tokens generated under the Conversions API settings tab in Events Manager are now supported by all available Graph API versions (see the supported versions here).
Note that these tokens will resolve to the most recent version of the Graph API. This behavior applies only to Graph API endpoints. Conversions API and Marketing API endpoints do not support autoupgrade behavior. An exception will be thrown.
User Profile API for Instagram Messaging: New fields
We are making enhancements to the User Profile API for Instagram messaging. The User Profile API for Instagram previously supported two fields: Name and URL of profile picture. We have updated the API to include the following information:
1. This will allow businesses to personalize and prioritize messages based upon publicly available user data. Follower count
2. Verified Badge
3. Business follows User account [Yes/No]
4. For more information, please refer to the developer documentation.
Detailed Targeting New Opportunities
To help advertisers find additional opportunities that weren’t originally available to them, when advertisers leverage Detailed Targeting and optimize for conversions, value or app events using the conversions objective they will be automatically included into Targeting Expansion. Please refer to the Detailed Targeting Expansion Help center article for more details.
Video API: New fields
We have added two new fields, views and post_views, to the [Video] node. To learn more, please refer to the Video API developer documentation.
Deprecations & Breaking Changes
The Graph API and Marketing API default behavior is to throw an error when an app requests a field or edge on a node that returns an associated node or nodes, but lacks the appropriate permissions required by the associated nodes. Some of these fields and edges didn’t follow the protocol. They were instead omitted from API responses if they did not have the appropriate permissions.
Starting with v12.0 these fields and edges will conform to the default behavior. This change will apply to all versions on December 13, 2021.
- Affected Graph API endpoints
- Affected Marketing API endpoints
System users and app roles
We are deprecating the ability for system users to be granted roles on apps unless the users and the apps both belong to the same businesses. We recommend that system users are removed from your app. Instead, use the Business On Behalf Of API. This breaking change will go into effect on December 13, 2021.
We are deprecating the planned_start_time parameter within the Scheduling capability in the Live API and the breaking change will go into effect on December 13, 2021. An announcement will follow regarding a new parameter.
Messenger Platform: Conversation API
We are deprecating the user_id field from the thread metadata in Conversation API. Developers will need to migrate all references to user_id to the Conversation API and fully rely upon IGSID to identify a thread between user and business.
This breaking change will go into effect on prior Graph API versions on December 13, 2021. To learn more, please refer to the Conversation API developer documentation.
Messenger Platform: Instagram Webhooks
We are making an update to our Messenger API for IG reaction webhook in order to better support emoji reactions. The current version returns an emoji field in a string. With this update, reaction Webhooks will return a unicode format. The default emojis will not be supported by the “reaction” field. The reaction field will return the default emojis and the MSGR equivalent.
This breaking change will go into effect on prior Graph API versions beginning December 13, 2021. In order to continue to support emoji reactions, all developers need to migrate to the new unicode we are returning by December 13, 2021. For more information, please refer to the Webhook Developer documentation.
API Version Deprecations:
As part of Facebook’s versioning schedule for Graph API and Marketing API, please note the upcoming deprecations:
- November 2, 2021: Graph API v4.0 will be deprecated and removed from the platform
- February 3, 2022: Graph API v5.0 will be deprecated and removed from the platform
- May 22, 2022: Graph API v6.0 will be deprecated and removed from the platform
To avoid disruption to your business, we recommend migrating all calls to the latest API version that launched today.
- Marketing API v10.0 will deprecate on 10/04/2021
- Marketing API v11.0 will deprecate on 02/23/2022
To avoid disruption to your business, we recommend migrating all calls to the latest Marketing API version that launched today. For more information, please visit the changelog.
Facebook Platform SDK
- On January 19, 2021, we announced the 2-year deprecation schedule for Facebook Platform SDK v8.x and below. These versions will sunset in January of 2023.
- On June 8, 2021, we released Facebook Platform SDK v11.0, which began the 2-year deprecation of Facebook Platform SDK v9.0. SDK v9.0 will sunset in June of 2023.
Native Offers Endpoint Deprecation
On June 8, 2021, we announced the deprecation of Offers Ads API. This will go into effect immediately with the release of Graph API v12.0.
Messenger Platform – Airline Templates
On June 8, 2021, we announced the deprecation of airline templates. This will go into effect on December 6, 2021.
More dWeb.News Social Media News https://dweb.news/news-sections/social-media-news/