Facebook Graph API v2.3 is now available to use, adding new login permissions, a new debug mode for developers and updates to Real-time Updates. Along with it, more APIs are being depreciated towards the end of June 2015.
For starters, Facebook is introducing new permissions and changing old ones:
user_postsPermission – This permission allows an app to access the posts on a person’s Timeline. This includes the someone’s own posts, posts they are tagged in and posts other people make on their Timeline. Previously, this content was accessible with theread_streampermission. Theuser_postspermission is automatically granted to anyone who previously hadread_streampermission.publish_pagesPermission – This new permission is required to publish as a Page. Previouslypublish_actionswas required. People who grantedmanage_pagesandpublish_actionsbefore v2.3 have automatically been grantedpublish_pages. If anyone logs in via v2.3, you’ll need to requestpublish_pagesexplicitly in addition tomanage_pages.read_custom_friendlistsPermission – Is the new name forread_friendlistsLogin permission. This is to clarify that the permission grants access to a person’s custom friendlists, not the full list of that person’s friends.
On June 28th 2015, the following APIs will be removed:
- Edges and Permissions –
/v2.3/{user_id}/interestsand/v2.3/{user_id}/activitiesedges as well asuser_interestsanduser_activitiespermissions are deprecated in v2.3. From June 23, 2015 onwards, in all previous API versions, these endpoints will return empty arrays, the permissions will be ignored if requested in the Login Dialog, and will not be returned in calls to the/v2.3/me/permissionsendpoint. - Page RSS Feed endpoint – at
https://www.facebook.com/feeds/page.phpis now deprecated and will stop returning data from June 23, 2015. Developers should call the Graph API’s/v2.3/{page_id}/feedendpoint instead. This returns JSON rather than RSS/XML. - Social Plugins – The following are now deprecated and will no longer render after June 23, 2015:
- Facepile Plugin
- Recommendations Feed Plugin
- Activity Feed Plugin
In addition to the above, the changelog also indicates a number of changes to video uploads, Page APIs and the API responses. You should check the complete changelog to see what other changes could affect you.
[…] the release of Graph API v2.3 back in March 2015, Facebook also announced the depreciation of a few of social plugins, […]
Hi Niraj,
thanks for a wonderful information. I have one question though, we have a application which used to use v1.0 api, since these api are deprecated our application got automatically upgraded to v2.0. Since this happened our app stopped working, reason is obvious we need to make some changes in our code base to accommodate necessary api change.
First I started making change on my local for that I created a new app on developers.facebook.com and I submitted couple of time for approval for publish_action.
(but it got rejected.. reasons I can explain if you want), but this blog post above states that for existing application it will automatically granted for publish_action.
does that mean if I use my existing app (created on 2009) would be automatically upgraded for these permissions and not need for login review..
Please let me know.
This is what my app does, it is a content management system, we create new sites for our customer, in that site customer can add document and choose which document they want to appear on their facebook page. and we fetch the comments posted on that post in our application. we initially requesting the oath token with these permissions..
https://graph.facebook.com/oauth/authorize?client_id=%1$s&display=popup&redirect_uri=%2$s&scope=read_stream,publish_stream,email,status_update,offline_access,manage_pages&response_type=token&enable_profile_selector=1“;
I really appreciate your help in this.
Thanks
You should check your [App Settings] > [Status & Review] page to see what permission have already been granted. There, it should tell you whether the publish_actions permission has already been added. Look for something like: