WebProNews

Tag: REST

  • Facebook Retires The REST API For New Apps

    In late 2011, Facebook said that it would retiring the REST API to focus all of its efforts on the Graph API. Developers had over a year to make the jump, and now Facebook is finally pulling the plug.

    Facebook announced today that the REST API no longer available for new apps. Going forward, all new apps on Facebook must use the Graph API. Apps created after April 10 will receive an error code 3 upon trying to call the REST endpoints.

    So what does this mean for all the currently existing apps using the REST API? Facebook says those apps won’t be affected, and can continue to use the API. Of course, Facebook would really like it if developers made the jump to the Graph API. If enough developers make the jump, Facebook may even be able to fully retire the REST API so that all apps are on the same page.

    If you have yet to make the switch to the Graph API, you might want to check out the stellar improvements and features Facebook has been introducing to it lately. In fact, Facebook just launched a few more Open Graph tools to help make users’ timelines more interesting.

    As per tradition, Facebook also released its latest bug report. Since last week, 70 bugs were fixed, and 72 were accepted for further review. You can check out the full bug fix list at the blog post.

  • Google Announces New Ad Exchange Developer Resources

    If you use Ad Exchange, you’re going to want to listen up. Google is making some new resources available to developers that should make your lives a lot easier.

    The first and most important change is that the Ad Exchange Web site is now integrated with Google’s developers resource site. This allows Google to provide better support for those working with the various APIs involved with Ad Exchange. Some of the features you’re going to find on the new Web site are details on the SOAP API, REST API and the Real-Time Bidding Protocol.

    Google is now giving Ad Exchange developers access to the REST API. It will give you the ability to “manage your RTB account configuration, submit creatives and list direct deals. Google suggests that you try out the API with their API explorer tool before you dive into making applications with it.

    To help developers get used to working with these new APIs and software, they have created a client library with code examples. The code examples will be the most useful as it allows you to see how various programming languages work within the SOAP and REST APIs. The programming language examples currently available for the SOAP API are Java, PHP, Python, Dotnet and Ruby. The REST API has a lot more examples available, but they are all in beta or alpha so exercise caution when trying them out. The language examples available are .NET, Go, Google Web Toolkit, Java, JavaScript, Objective C, PHP, Python and Ruby.

    If you still have questions, and you probably will, Google directs developers to the Ad Exchange API forum. If you don’t need any help, you can give help to other developers that do need it. Remember, sharing is caring and sharing your developer knowledge is the best way to show that you care.