Facebook launches Requests 2.0 for developers

Facebook has launched Requests 2.0: the bookmark counters that alert users of outstanding requests has been simplified, and there are two types of requests: user-generated and app-generated.

Facebook has launched Requests 2.0, simplifying the process of managing the bookmark counters that alert users of outstanding requests. The update also splits requests into two types for developers:

  • User-generated requests: These requests are confirmed by a user's explicit action on a request dialog. These requests update the bookmark count for the recipient. Developers can send these requests by using the recently launched Request Dialog.
  • App-generated requests: These requests can be initiated and sent only to users who have authorized your app. Developers can send these requests using the Graph API. Use these requests to update the bookmark count to encourage a user to reengage in the app.

Facebook has also stopped manually managing the bookmark count using the incrementCount and decrementCount APIs, and has unified its APIs so the count represents the number of all outstanding requests. As a result, the developer only needs to worry about sending requests to update users about outstanding items in their app, and the count is synced automatically.

Developers will still need to process requests. When a user with pending requests visit your app, you should first read the outstanding app requests for that user, highlight the request the user wants to act upon, and delete it when the user acts upon it. To prevent bookmark counts from accumulating indefinitely, requests will auto-expire after 14 days.

To use both request types and automatically sync the bookmark count to them, you'll need to enable the feature (Developer App settings => Advanced => Upgrade to Requests 2.0). This switch controls the bookmark counts seen by your users and synchronizes the count with sent requests. New apps will automatically use Requests 2.0.