The much-awaited Application Programming Interface (API) for movie site Netflix will launch tomorrow, according to an email from the company. As HackingNetflix found out last week, the launch event will occur at the AJAX Experience conference. Details are listed below. It looks pretty good, but there are some major limitations, too.
Millions of people love movies via Netflix, making this API an opportunity for all kinds of developers to add well-known value to any other application.
The company says the API will allow access to data for 100,000 movie and TV episode titles on DVD as well as Netflix account access on a user's behalf.
Presumably this does not mean that 3rd party applications will be able to pull in the streaming content available on the Netflix site, but rather that they'll be able to make user data portable for offering personalized content on their applications based on a user's Netflix activities. Users will still have to visit the Netflix site itself or to one of the big integration partners like LG or Xbox in order to watch streams. Last week Netflix cut deals with the Disney Channel and CBS to put nearly 100 of their shows on the Netflix site. You vibrating hamster Facebook app will not be able to show your users their favorite Netflix video inside the hamster, though, you just get to interact with their list of favorites content as data.
Update: Now that the API is live, we see that our assumption here was wrong. As reader Dave Jeyes points out in comments, the documentation includes code for a play button and a media player. Cool!
It also appears that this is a read-only API, meaning that movies cannot be requested or other account information changed, from inside of 3rd party applications. We presume there will be affiliate links made available so that users can click through and developers can make some profit.
Update: It turns out our hunch was wrong about read-only. In an email response to the question, the company says: "Write capabilities: yes. We wanted to enable full movie queue management, so there are write capabilities in that a user can add movies to their queue, reorder their queue, and remove movies. Ratings can also be written, i.e. a user can rate a movie using the API."
Speaking of developer profit, commercial use of the API will be accepted. Netflix says, for example, that developers can sell an app in the iPhone app store that uses the Netflix API. That's great, there are far too many commercially desirable APIs around the web for which commercial use is prohibited.
The API includes access to data via REST API, a Javascript API, and ATOM feeds. No JSON, which we suspect will disappoint some developers.
User authentication will occur using OAuth, the open standard we and others have been cheering for and the protocol now used for all the Google Data APIs.
So the good news is that Netflix is using standards based authentication, making it very easy to develop against, is allowing commercial use and is finally launching the interface. The bad news appears to be that it's user-data only and appears to be read only. We'll update this post if we get any more details from the company before launch tomorrow. Update:Now that we've seen more information about the API, it appears that there is no bad news. This is great stuff.
The API will be available at http://developer.netflix.com by self sign-up tomorrow. That site is currently password protected.
TrackBack URL for this entry: http://www.readwriteweb.com/cgi-bin/mt/mt-tb.cgi/8479
Comments
Subscribe to comments for this post OR Subscribe to comments for all Read/WriteWeb posts
Smart move from Netflix. It is great to see the web slowly evolve beyond simple widgets to more seamless integration. Next: Linked Data.
Posted by: Edwin Khodabakchian | September 30, 2008 5:28 PM
Thanks
Posted by: Shanika Perara | September 30, 2008 6:08 PM
Wow - really cool! But no embeds of streaming movies? :(
Still, it will be interesting to see and we do plan on integrating with a users "My Queue" at Mefeedia.com, so users can be updated on their Netflix Queue too... TV, Web Video, Movies, News Video. :)
Posted by: Frank Sinton
|
September 30, 2008 6:24 PM
Wow, this is great news. We hope to make full use of this on FeedFlix!
Posted by: Raghu Srinivasan | September 30, 2008 6:31 PM
this will enable us to offer some of our users' Netflix-related feature requests! Awesome news!
Posted by: Flickchart
|
September 30, 2008 7:47 PM
The Netflix API documentation shows both a Play button and a way to invoke a media player.
Here's the function:
"openPlayer(titleID, xPos, yPos, appID)"
http://developer.netflix.com/docs/JavaScript_APIs
Posted by: Dave Jeyes | October 1, 2008 8:15 AM
One more clarification. Based on the documentation the API supports both ATOM and JSON. see:
"The REST API resources return the output data formatted by default as vanilla XML data, or what is referred to as "plain old XML" (POX). You can instead specify that the output be in either Atom or JSON format. To do so, include the output parameter in your API request and set its value to either Atom or JSON ."
Posted by: Edwin Khodabakchian | October 1, 2008 9:46 AM