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 API: Graph API v2.4 Released, Removes Groups, Notifications and Stream Permissions

Facebook API: Graph API v2.4 Released, Removes Groups, Notifications and Stream Permissions

4

Facebook has released the latest update to the Graph API, resulting in more drastic changes and deprecations to the platform. Released on July 8th 2015, the latest version of the API removes access to the user’s Notifications, Inbox and Stream and Groups. As a result, you have until October 8th 2015 to remove these features from your App before they are completely disabled.

As a result, the following permissions have been removed:

  • read_stream
  • read_mailbox
  • manage_notifications
  • user_groups

This means that application using any of the above will cease to work after October 8th 2015. With Groups, the API will still support API calls to groups the user is an admin of, but you will no longer be able to get information on which other groups the user is a member of.

In other deprecations, the following endpoints will also stop working in v2.4:

  • GET /v2.4/{id}/links
  • GET /v2.4/{id}/statuses
  • GET /v2.4/{event_id}/invited
  • GET /v2.4/{event_id}/likes
  • GET /v2.4/{event_id}/sharedposts

For all the details on the changes in Graph API v2.4 and instructions on how to upgrade to the latest version, please see the official changelog.

API, Deprecation, Facebook, Facebook Graph API

4 comments on “Facebook API: Graph API v2.4 Released, Removes Groups, Notifications and Stream Permissions”

  1. BasavaraJ says:
    February 18, 2016 at 6:41 AM

    How we can use notification API if we want to use it in future? can we change the API version..?

    Reply
    • Niraj Shah says:
      February 19, 2016 at 12:53 PM

      You can still send notifications to the user, you just can’t read or edit them in anyway. You can switch to a different API version using the SDK, but older versions will be come unusable as new versions are released, forcing you to upgrade. There is no point in using deprecated APIs as they will stop working eventually.

      Reply
      • BasavaraJ says:
        February 22, 2016 at 4:09 AM

        Thanks for replay Niraj,

        My requirement is to read the notification, not to post notification. So is there alternate way to achieve this..?

      • Niraj Shah says:
        February 23, 2016 at 7:43 PM

        The Read Notification API has been depreciated. There is no way around it. You can no longer read notifications.

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