Web Niraj
  • Facebook
  • Flickr
  • Github
  • Linkedin
  • Twitter
  • YouTube
Online portfolio, code examples and developer blog
  • About
  • Contact
  • Portfolio
  • WordPress
Search the site...
  • Home
  • Blog
  • Facebook Announces Graph API v2.3, More Deprecations

Facebook Announces Graph API v2.3, More Deprecations

3

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_posts Permission – 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 the read_stream permission. The user_posts permission is automatically granted to anyone who previously had read_stream permission.
  • publish_pages Permission – This new permission is required to publish as a Page. Previously publish_actions was required. People who granted manage_pages and publish_actions before v2.3 have automatically been granted publish_pages. If anyone logs in via v2.3, you’ll need to request publish_pages explicitly in addition to manage_pages.
  • read_custom_friendlists Permission – Is the new name for read_friendlists Login 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}/interests and/v2.3/{user_id}/activities edges as well as user_interests and user_activities permissions 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/permissions endpoint.
  • Page RSS Feed endpoint – at https://www.facebook.com/feeds/page.php is now deprecated and will stop returning data from June 23, 2015. Developers should call the Graph API’s /v2.3/{page_id}/feed endpoint 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.

Facebook, Facebook Graph API, Facebook Graph API 2.3

3 comments on “Facebook Announces Graph API v2.3, More Deprecations”

  1. Facebook to Depreciate Like Box Social Plugin on June 23rd 2015 | NUETA VENTURES says:
    May 20, 2015 at 4:19 PM

    […] the release of Graph API v2.3 back in March 2015, Facebook also announced the depreciation of a few of social plugins, […]

    Reply
  2. Dee says:
    August 7, 2015 at 5:34 PM

    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

    Reply
    • Niraj Shah says:
      August 14, 2015 at 8:17 PM

      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:

      Reply

Leave a ReplyCancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

StackExchange / StackOverflow

profile for Niraj Shah on Stack Exchange, a network of free, community-driven Q&A sites

Support Me

Buy Me a Coffee

PSN Profile

Tags

ACL Amazon Web Services Android Android 4.4 KitKat Android 5.0 Lollipop Apache Backup Bash Bug Command Line Cordova cPanel / WHM Facebook Facebook Graph API Facebook PHP SDK 4.0 Facebook Social Plugins Fan Page Flash Geolocation Google Nexus 5 Hacking HTML5 Input Sanitization iOS JavaScript jQuery Laravel 5 Laravel 5.2 Linux Mac OS NodeJS Parse PDF PHP Plugin Portfolio Review Security Server SSH SSL Sysadmin Tutorial WordPress WordPress Plugins
© 2011-2025 Niraj Shah
  • Blog
  • Portfolio
  • WordPress
  • About Me
  • Contact Me
  • Privacy Policy
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Privacy Policy