Introducing Fb Graph API v12.Zero and Advertising API v12.0
Today we’re releasing Facebook Graph API v12.0 and Marketing API v12.0. Below we’ve highlighted changes that will affect parts of our developer community. These changes include announcements and product updates, reminders of previous launches, and notifications of wide-ranging settings that may affect the integration of your application (s) with our platform.
A full list of all changes and their details can be found in our changelog.
General announcements and updates
Conversions API: Minimum expandable version
Graph API Backward Compatibility for Apps Created with One-Click Access Tokens Starting with version 12.0, newly created access tokens generated on the Conversions API Settings tab in Events Manager are now supported by all available Graph API versions (those supported Versions can be found here).
Please note that calls with these tokens to an outdated Graph API version are automatically resolved into the oldest available version. This behavior only applies to Graph API endpoints. Marketing API endpoints, including the Conversions API, do not support automatic upgrade behavior and will throw an exception.
User Profile API for Instagram Messaging: New Fields
We’re making improvements to the Instagram Message User Profile API. Previously, the User Profile API for Instagram supported two fields: 1) Name and 2) URL of the profile picture. To help businesses better personalize and prioritize messages based on publicly available user information, we’ve updated the API to also include the following information:
1. Number of followers
2. Verified badge
3. Business follows user account [Yes/No]
4. User account follows business account [Yes/No]
See the developer documentation for more information.
Detailed targeting of new opportunities
To help advertisers find additional advertising opportunities that were not originally available to them, they are automatically included in the targeting extension when they use detailed targeting and optimize for conversions, value or app events using the conversion goal. For more information, see the help article on the detailed alignment extension.
Video API: New fields
We have two new fields, views and post_views, for the [Video] Node. For more information, see the Video API developer documentation.
Settings and breakthrough changes
The default behavior of the Graph API and Marketing API is to throw an error when an app requests a field or edge on a node that returns one or more associated nodes but does not have the appropriate permissions required for the associated nodes are required. However, some of these fields and edges did not follow this protocol and instead were simply omitted from API responses if the calling app did not have the appropriate permissions.
As of v12.0, these fields and edges correspond to the standard behavior. This change will apply to all versions as of December 13, 2021.
System users and app roles
We’re discontinuing the ability to assign roles for apps to system users unless the users and apps both belong to the same company. To avoid disruptions to your app and your company, we recommend removing these system users from your app and using the Business On Behalf Of API instead. This breaking change comes into effect on December 13, 2021.
The “planed_start_time” parameter within the “Scheduling” function in the Live API will be discontinued and the breaking change will take effect on December 13, 2021. A new parameter will be announced at a later date.
Messenger platform: Conversation API
We say goodbye to the user_id field from the thread metadata in the Conversation API. All developers must migrate all references to user_id (IGID) and rely entirely on IGSID as the primary identifier of a thread between the user and the company.
This fundamental change will take effect on December 13, 2021 for earlier Graph API versions. For more information, see the Conversation API developer documentation.
Messenger platform: Instagram webhooks
We’re updating our Messenger API for the IG Response webhook to better support emoji responses. The current version returns the emoji field as a string – with this update, response webhooks return a new Unicode format. Note that the Reaction field only supports the standard emojis. For all other emojis, the reaction field returns “other”, just like MSGR.
This fundamental change will take effect December 13, 2021 for earlier Graph API versions. In order to continue to support emoji responses, all developers will need to migrate to the new Unicode, which we will be returning by December 13, 2021. Please see the webhook developer documentation for details.
Setting the API version:
As part of Facebook’s version plan for the Graph API and Marketing API, please note the upcoming settings:
- November 2, 2021: Graph API v4.0 will be discontinued and removed from the platform
- February 3, 2022: Graph API v5.0 is retired and removed from the platform
- May 22, 2022: Graph API v6.0 will be discontinued and removed from the platform
To avoid disruption to your business, we recommend migrating all calls to the latest API version launched today.
- Marketing API v10.0 will be discontinued on October 4th, 2021
- Marketing API v11.0 will be discontinued on 02/23/2022
To avoid disruption to your business, we recommend migrating all calls to the latest Marketing API version launched today. (Visit the changelog for more details).
Facebook platform SDK
Native offers endpoint setting
On June 8, 2021, we announced the discontinuation of the Offers Ads API. This takes effect immediately with the release of Graph API v12.0.
Messenger platform – airline templates
On June 8, 2021, we announced the discontinuation of airline templates. This comes into force on December 6, 2021.