Graph API v2.2 and updated iOS and Android SDKs

As part of our continued commitment to release changes to our Platform through versioning, we're delighted to announce today the next version of the Graph API: v2.2 — and that going forward, the Ads API also supports versioning as described below.

In addition, we're releasing updated iOS and Android SDKs designed to work with API v2.2.

v2.2 builds on v2.1 with a number of improvements — particularly for apps that manage Pages — and includes one of the most-requested features by these apps: the ability to programmatically hide and unhide comments on Page posts.

Apps created from today onwards may only call v2.2 or greater, and v2.1 will be deprecated two years from today, on October 30, 2016. As announced at f8 this year, v1.0 will be deprecated on April 30, 2015.

API v2.2 feature highlights

• Apps can now programmatically hide and unhide comments on Page posts.
• A new token_for_business field on the User object makes it easier to identify the same person across multiple apps owned by the same business.
• There's a new way to manage Page subscriptions for realtime updates via a dedicated subscribed_apps edge.
• More of a Page's attributes are now editable via the API through the Page node or the settings edge.

For the full list of additions, changes and deprecations in this version please see the Graph API changelog and the v2.1 to v2.2 upgrade guide as well as our iOS and Android SDK changelogs.

Ads API Versioning

We recently announced new access levels for the Ads API. In addition, from v2.2 onwards, the Ads API now supports versioning.

For developers using the Ads API, versioning means increased control over how you opt into new Ads API features. Rather than changing a migration setting in your app dashboard, you can now control the behavior by specifying the version number in your client codebase.

Our advertising products continue to evolve at a fast pace. To ensure developers take advantage of this progress, the Ads API will follow a 90-day breaking change policy. To make this behavior clear, Ads API methods will be removed from a version 90 days after the next version is released.

As v2.2 is the first release for the Ads API, Ads API methods will be removed from v1.0, v2.0 and v2.1 in 90 days' time. Developers using the Ads API should update their apps to call v2.2 before January 28, 2015. After that date, all calls to Ads API methods which do not specify v2.2 (including calls which do not specify any version) will result in an error.

For full details on the changes to the Ads API in v2.2, see the Ads API Blog and the dedicated Ads API changelog and upgrade guide.

How to Upgrade to v2.2

To upgrade to v2.2, mobile developers should download our latest iOS and Android SDKs. Web developers should declare v2.2 in the version property when calling the init() method of the JavaScript SDK. Developers calling the Graph API directly should specify /v2.2/ in URL path.

Reminder of forthcoming deprecations

With the release of API v2.1 on August 7, 2014, we announced a number of policy changes and 90-day deprecations. These come into effect on November 5th:

• The Recommendation Bar plugin is deprecated and will stop appearing on your pages after November 5th. Please remove the <fb:recommendations-bar/> XFBML tag your pages at the earliest opportunity.
• You must not incentivize people to use Social Plugins or to like a Page. This includes offering rewards, or gating apps or app content based on whether or not a person has liked a Page. From November 5th, the liked field within the page property of the signed_request object will return true for all apps created before August 7, 2014 when those apps are rendered inside a page tab.
• The insights edge will be removed from the Application object in v1.0 and v2.0. You should update your apps to call /v2.1/{app_id}/app_insights or /v2.2/{app_id}/app_insights to take advantage of the new App Insights API.