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.
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.
token_for_businessfield on the User object makes it easier to identify the same person across multiple apps owned by the same business.
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.
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
/v2.2/ in URL path.
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:
<fb:recommendations-bar/>XFBML tag your pages at the earliest opportunity.
likedfield within the
pageproperty of the
signed_requestobject will return
truefor all apps created before August 7, 2014 when those apps are rendered inside a page tab.