Facebook platform APIs
Get flash to fully experience Pearltrees
Facebook today announced it would be migrating the now publicly available Ads API from the legacy REST API to the Graph API by January 2012, and that programmatic access to new features will only be available via the Graph API. Developers of Ads API tools and services that allow for efficient management of massive Facebook ad campaigns should look to migrate as soon as possible to retain access to forthcoming improvements. Facebook has also released the source code for the Ads Power Editor , its internally developed Ads API tool, to provide a development example.. The Ads API was officially launched to the public at the beginning of August after nearly two years of private beta testing with a limited set of partners. It joined the Pages and Insights APIs to form the Facebook Marketing APIs. The Ads API permits developers to devise apps that manage Facebook ads programmatically, permitting simultaneous creation of thousands of ad variants, dynamic bid optimization, and deep analytics.
Facebook to Migrate the Ads API to the Graph API, Releases Ads Power Editor Source Code
Photo aggregation service Trove revealed results of a survey of Hacker News readers about API horrors and headaches. Programmable Web (a site owned by ReadWriteWeb sponsor Alcatel-Lucent ) counted up the mentions of specific APIs to try to determine which one drew the most ire from developers. The verdict? Facebook is the worst. But actually, Facebook tied with "Other."
Does Facebook Really Have the Worst API?
Facebook Introduces Batched Requests to Assist Heavy Graph API Usage
Facebook now allows application developers to batch requests so they can more efficiently access the Graph API. Developers can batch up to 20 requests, batch multiple HTTP methods and FQL queries, and can order operations to specify dependencies between them. The capability should help developers build faster, more efficient apps that can access large amounts of data without putting as much server strain on Facebook. The Graph API was designed for accessing a single object so previously, developers had to send each Graph API request separately. However, it’s more efficient to batch these requests into a single HTTP request, so Facebook has released the capability to everyone’s benefit.
Facebook Insights API
Facebook Groups API
Facebook Places API
Open graph
f8
Facebook Connect
As part of its game-focused product updates, Facebook changed a wide range of policies around what developers can and can’t do on the platform. The company has broadly grouped its dozens of changes into three main areas, with the overall move being to make many more options available to developers. The changes include new or heavily revised policies, policies that are being turned into best practices (and so are no longer required), those that are getting removed due to now-redundant language or larger product changes. At its announcement event yesterday, Facebook executives explained that the more lenient policies are partly the result of the product changes. Because it will not show news feed stories from games to non-players, for example, it is greatly increasing the variety of news feed stories that it can show to gamers.
A Line-by-Line Look at Facebook’s Updated Platform Developer Policies
We’re rolling out an update to the Live Stream plugin for all new and existing applications to be more consistent with users’ expectations and other social plugins. In this new version, all posts can be seen in real-time by other people viewing the Live Stream, and we’re adding the option for users to not share their comments on Facebook. We also now support multiple Live Streams on one website by specifying a via URL, which will link status updates to their respective pages.
Platform Updates: Live Stream, Like Button and Real-time
*UPDATE* : Carl Sjogreen, the lead of the platform PM team, commented below that positive changes are coming. All of us should hope he and his team succeeds! Original Post: Using the Facebook API is the one of the worst experiences as a developer I have ever had. This past week has been a real trial, and a true challenge to keep my energy and spirits up so that I remain efficient. Whew, that’s off my chest.
The Facebook API: A Case Study in Not Caring About Developers | Seth Call: Programmer
