At f8 2014, we announced a new version of the Graph API v2.0. We also announced that moving forward, the primary way we'd release changes to our Platform would be through new API versions. Versioning provides a 2-year stability guarantee for Core APIs and gives you control over when you upgrade different instances of your app to use the latest platform features.
Version 2.1 incorporates several commonly requested features that build on the changes in v2.0 with the goal of increasing consistency and simplicity for developers. It's available today to all apps — and is now the default version for all new apps.
/oauth/access_token, which will return a string in case of success.
likedfield will no longer be returned in the
pageproperty of the
signed_requestobject for Page Tab apps created from today onwards. For apps created before today, from November 5, 2014 (90 days from today), the
likedproperty will always return
trueregardless of whether or not the person has liked the page.
In addition to the launch of API v2.1, today, we are announcing two changes to our Platform Policies. Developers should update their apps to comply with these policy changes by November 5, 2014 (90 days from today).
To upgrade to v2.1, mobile developers should download our latest iOS and Android SDKs. Web developers should declare
v2.1 in the
version property when calling the
v2.1 in your URLs when calling the Graph API.
In line with our 2-year stability guarantee, v2.0 will be deprecated on August 7, 2016. After that date, all apps will automatically be upgraded to v2.1. As announced at f8 2014, v1.0 will be deprecated on April 30, 2015.
With each API version living for at least two years, we're excited to enhance stability, simplicity and consistency across the Graph API. We'll continue to focus on this in future versions.