Facebook has released version 9 of the Graph API and the Marketing API. The release brings innovations that require action on the part of the developer. The company is also updating some API guidelines with the aim of better protecting users and their private data.

Since 10. November 2020, consumer and gaming apps that are submitted for reviewing the application or that switch from development to live mode must have a data deletion callback or a Provide a URL with explicit instructions for users on how to request deletion of their data. Apps that have not gone through this process by the specified date will receive reminder notifications with additional instructions.

Action required by developer Facebook’s goal is to better protect user data. As a result, the company has ordered an annual data usage review for app administrators. This procedure is intended to ensure that API access and data usage comply with the guidelines of the Facebook platform. This requirement apparently ensures that applications that connect advertisers’ CRM systems (Customer Relationship Management) to the Facebook API lose the ability to retrieve and pass on data from Lead Ads campaigns.

Developers who use the current version of the Graph API and want to continue to retrieve Lead Ads form data must complete the app review. This means that business apps must request extended access for permission to get leads before upgrading. Non-business applications must go live and request leads_retrieval permission before upgrading. Developers who do not want to upgrade to Graph API 9 yet have until February 9th 2021 to submit an app review request for leads_retrieval permission.

Change of some API-Policies Facebook had on 22. October changed its Facebook Live policy to protect users from fraudulent and deliberately harmful content posted on Facebook Live. Accordingly, live videos may no longer be prerecorded or looped – both are forbidden by both the Live API and Core Live. Broadcasts via the Live API or Core Live must not contain looping content (videos, static images or video-only for surveys) and all pre-recorded content must be clearly labeled.

The company uses crawlers to ensure that URLs are live and accessible to users using third-party applications. These crawlers are intended to protect privacy. Facebook is also changing its guidelines here: Developers should grant the Facebook crawler access to URLs that are specified in the app’s settings. This includes all developer-controlled URLs, including the Policy URL, Connect URL and other product-specific URLs.

The Instant Games guidelines also receive a Update. According to this, instant Games is prohibited from independently requesting personal or sensitive data from people in an instant game. In addition, by updating the bot policy, developers are instructed to inform users of an automated chat experience, for example with a chat bot, about communication with an automated system. According to the announcement, this change is particularly relevant for the German market.

For information – no action required Facebook informed Instagram users via adjustments to the metrics of the Instagram Insights API, which can lead to a decrease in the number of followers displayed via the API. In addition, the Insights data for the Follower_count metric should only be displayed for the last 30 days. The company also announces that it has also worked on the Instagram Ads API. Accordingly, it is possible for users to take over existing organic Instagram posts and advertise them as advertisements. Facebook also plans to return the Instagram Graph API user ID on the Instagram Ads API and some other endpoints to provide a more consistent developer experience between the Ads and Graph API platforms.

See more Information on the current version of Facebook’s Graph API and Marketing API can be found in the announcement post on the Facebook for Developers blog.

(mdo)