Netflix API Developer Blog

Upcoming Changes to the Open API Program

As of Oct. 14th, 2011, the Netflix API will be focused exclusively on offering content and functionality from the streaming catalog. As a result, we will be discontinuing the support of DVD-related features in the Open API. These changes are in an effort to better position the Netflix API towards the company’s long-term goal of internationalizing our streaming experience. Focusing the API towards streaming will better enable the company to create rich experiences in these new markets. Additionally, over time, we plan to open up the API to become international as well.

The rest of this post includes the list of changes that will take effect in October. Our goal is to make the transition as smooth as possible by gracefully degrading as many of these deprecated features as possible.

The following resources will have DVD-related content removed from them, but they will still work correctly with streaming content only:

  • users/user_ID/title_states
  • users/user_ID/feeds
  • catalog/titles
  • catalog/titles/autocomplete
  • catalog/titles/title/similar
  • catalog/people/person_ID/filmography

The following disc endpoints (on the left of the table) will continue to be valid endpoints but will return a comparable, streaming-oriented result set (the results provided by the right side of the table) until June 1st, 2012, at which time these endpoints will be removed:

Current Endpoint New Endpoint Results
/users/user_ID/queues/disc /users/user_ID/queues/instant
/users/user_ID/queues/disc/available /users/user_ID/queues/instant/available
/users/user_ID/queues/disc/available/entry_ID /users/user_ID/queues/instant/available/entry_ID
/users/user_ID/queues/disc/saved /users/user_ID/queues/instant/saved
/users/user_ID/queues/disc/saved/entry_ID /users/user_ID/queues/instant/saved/entry_ID

The following resources will be deprecated and will return 404 responses:

  • users/user_ID/at_home
  • users/user_ID/rental_history/shipped
  • users/user_ID/rental_history/returned
  • catalog/titles/discs/disc_ID

All category resources will be deprecated. The category scheme attribute will remain, but will no longer resolve. The affected resources include:

  • /categories/title_formats
  • /categories/award_types
  • /categories/screen_formats
  • /categories/rental_states
  • /categories/title_video_formats
  • /categories/languages
  • /categories/subtitle_languages
  • /categories/audio
  • /categories/genres
  • /categories/title_formats
  • /categories/queue_availability
  • /categories/title_states
  • /categories/mpaa_ratings
  • /categories/tv_ratings
  • /categories/ca_movie_ratings
  • /categories/container_formats
  • /categories/video_formats
  • /categories/audio_formats

All resources that return DVD-specific elements will continue to work, although the DVD-specific elements will no longer be returned. This will primarily affect the elements in the catalog/titles/title resource, which will no longer return DVD-related values in the title_formats category.

Currently, there are several endpoints for the catalog index across the versions of the API. Over time, we plan to collapse them into a single index. For this announcement, we plan to leave the current versions the same, although the number of titles will dramatically decrease. The title count will decrease because the index today has both streaming and DVD titles. From this change, it will only contain titles that are available in streaming. We will have future announcements the catalog index in the future as we attempt to globalize it and clean up the endpoints.

The JavaScript Widgets will continue to work, although the will be modified to only work for streaming titles. Titles will no longer be able to be added to the DVD queue through these widgets.

The documentation in the portal is currently being revised to reflect all of these changes. We hope to have it published to the site sometime next week.

During this transition, we will continue to work with our developer community to make the change as smooth as possible.

Daniel Jacobson, Director of Engineering – Netflix API

32 Comments

  1. Gregg Reno – 8 months ago

    Daniel - I really appreciate the long lead time and the detailed description of these changes. It's much better than having to scramble to make code changes after it's already in production.

    Maybe this has been brought up in the past, but I'd like to request a developer sandbox server so we can test the changes before they hit production. Maybe a few weeks early? Something like api_sandbox.netflix.com and odata_sandbox.netflix.com?

    Also, will OData be impacted by the changes other than the changes to DVD at categories? Or will the OData search functionality be migrated into the new API? I understand it may be too early to announce anything.

    Thanks,
    -Gregg Reno

  2. jonbcamposYahoo – 8 months ago

    I too would like to say thank you for the heads up.

  3. Daniel Jacobson – 8 months ago

    Gregg, Thanks for the reminder. I actually meant to include an update about OData as well.

    The biggest impact on the OData implementation will be in the amount of content that is available (similar to the content changes for the rest of the API). Come October, the OData library will contain streaming titles only.

  4. mosdl – 8 months ago

    So I assume this means that any current bugs with discs and the api won't be resolved (such as tv series not working at all with the api for discs)?

  5. cornyd00d – 8 months ago

    So the only way to add/move discs in our queue after this will be the official Netflix site? One of the driving reasons I was making my app in the first place was because I wanted to be able to add/re-arrange movies to my disc queue and the official Netflix app does not support this.

  6. Gregg Reno – 8 months ago

    OK, thanks for the update on OData. Glad to know it will still be around for a while.

  7. Matthew Foster – 8 months ago

    Please reconsider this change, or at least provide a way for users to still access these endpoints, even if they have specify additional options or use a different server address. Making this change, as you know, will kill a lot of third-party applications. I would be disappointed if this were to happen, and would strongly reconsider whether I want to continue paying for Netflix.

  8. Kurt – 8 months ago

    I agree with cornyd00d and Matthew Foster. I wrote an app specifically to manage my DVD queue, because the options for arranging the queue using the official Netflix site are so poor. Please consider keeping at least the endpoints used to access and sort the DVD queue.

  9. John Clayton – 8 months ago

    Let me get this straight - even though DVD is the only way to get most newer content you're going to obsolete the best way to manage it?!

    This change would be more than welcome once ALL content was available through streaming - and believe me, as a consumer that's what I want - but that is a long, long ways off. In the mean time customers still need to get DVDs if they want to see newer movies and TV shows, and other content not available through streaming. I built an app to add movies to my DVD queue whenever, and from wherever, because sometimes it's just easier than navigating the non-mobile-friendly site. I'm sure a large portion of your customers use apps to manage their queue for the same reason.

    Just pulling the plug on what users see as a core function of Netflix seems like a pretty harsh move. Not cool.

  10. elaydin – 8 months ago

    I know posting on here is a complete waste of time, but here it goes...

    I understand DVDs are annoying. You have to acquire them. You have to store them somewhere. You have to mail them out, and get them back in the mail. Sometimes you have to replace them. However, it's still the only way to get most new movies. It's also difficult for the studios to take them away from you. They'll be around for a while.

    What possible good is there in doing something your customers are NOT going to like? The resources required have to be small compared to the full streaming infrastructure.

    One question:
    Where do I forward the annoyed emails from my customers?

  11. sbv002 – 8 months ago

    Even after thinking about this for a few days, aside from the obvious implications, I'm still not making the connection between Internationalization and shutting down developers' access to the DVD API - unless of course DVDs are going away altogether.

  12. Hello – 8 months ago

    I have to ask the question. Why keep an API at all if you kill off the DVD features? Just use the Official Netflix app on your phone (I know some driod's are still missing this) and the web site for anything else. Seriously there's no reason for an API.

  13. Dave – 8 months ago

    I wish I could say that I'm not disappointed in this decision. It doesn't make sense why would you work so hard to develop a neat API to just throw it away. Unfortunately I see the outcome of this decision, alienating developers and losing the support of the developer community you worked so hard to build. I hope you guys will reconsider but I doubt this comment will reach anyone important.

    In the meantime I'll still finish my mobile application and when the end of disc management comes I'll abandon it. Another terrible choice of a great American company. No wonder we have no innovation here anymore.

  14. Wile E Coyote – 8 months ago

    Daniel,
    I too am concerned about the future of the API, but have a few questions.

    1. Lag time in service - What will be the lag time between the API changes (October 14th) and Netflix going excusively to Instant Streaming? The sites we build or maintain will obviously have a disadvantage due to the inability to deliver all of the Netflix services (disc queue management.)

    2. The catalog index - I understand that the queries of the API and OData will only contain streaming titles, but what about the full catalog index? Will it still contain all movies in the Netflix database? I can live with the API and OData service only returning streamed titles, but I will be relying on the catalog index to return all titles.

    As others have stated, thanks for the heads up. We appreciate it!

  15. Billy Mabray – 8 months ago

    I was working on a full-featured iPad app for managing DVD and streaming queues. I started the project because the Netflix website doesn't meet my needs, and I've heard from many other people that they'd like a native app with more features. As it stands now, this project is on hold. The API will no longer be able to scratch this particular itch, so I have to move on to other projects.

    Now, I understand why you're making this change: For your growing international user base, it would be confusing for them to find a bunch of third party apps that have DVD features they don't, and may never, have access to. But I have to think there must be another solution that doesn't cut everybody off from using the DVD APIs.

    Have you considered changing the API license? Perhaps require that any app with DVD content be restricted to the US only. Or require that DVD data cannot appear in the same app as streaming data. Just seems like there must be a less drastic solution.

  16. Sam Matthews – 8 months ago

    I agree that, due to this new direction, the API and most 3rd party apps developed with it, will become irrelevant.

    In the case of Android, NF has developed an instant player, but has made no mention of allowing that player to be utilized via other apps. NF is basically jettisoning the whole API crowd.

    I can't think of why they would do this, other than... I guess ultimately NF will discontinue all DVD rentals, thus eliminating thousands of messy employees, for a handful of button pushers.

    And the fact that they are 'going international'?.. perhaps its off to Mexico.

    I too will discontinue my android app when this change goes into effect. I mean.. whats the point of adding Instant Movies to your queue that you cannot instantly watch? .. unless you leave my app and go find the same movie on NF's Player.

    I hope Redbox eats your lunch ..

  17. Sam Matthews – 8 months ago

    Ok I think I figured it out... what NF is doing is preserving the API for the big companies that have built set-top boxes.. like Roku, MS Media, Tivo, etc. These devices only stream instant, and so have nothing to do with DVDs or their queues.

    What they are also doing is rendering every 3rd party app that does queue management - useless - because who's going to use a 3rd party app to manage half their queues? No, they will now go back to the NF site, which is where NF want's them I guess.

    Yes...thanks again for the early heads up.. but I had a sneaking suspicion going months back.. when I realized that all the substantial work on the API was over 2 years old, with almost no changes and/or activity since.

    PS.. the NF site looks like crap... what with all the missing box art... and no member reviews...

  18. nitramssirc – 8 months ago

    I take it from the deafening silence that the last line about working with the developer community means they will continue to work with the community in the same fashion they have been, practically not at all!

    Personally, I love Netflix, and I use it almost everyday, but until Netflix can consistently offer new titles and make them easy to find, I just cannot get fully behind Instant only. I can only hope that Netflix plans on either improving their mobile app, or they are going to drop DVD's altogether.

  19. Matthew Foster – 7 months ago

    @nitramssirc: It wasn't a deafening silence, they were just too busy working on making the rate increases for DVD subscribers take effect. http://www.santacruzsentinel.com/localnews/ci_18462453

  20. ShadowAssassin – 7 months ago

    What a disappointing business decision. I've had my account suspended for months and months after the first rate hike and it looks like I'm just going to cancel it all together. The streaming section is so boring and now you're going to make the API worse. You'll be able to find me on Vudu and Hulu, see you later Netflix!

  21. Brandon Radcliffe – 7 months ago

    Absolutely not cool, my family and I feel that this unjust and disappointing, we will now be going to Blockbuster for there service........................ Horrible move Netflix, next time be smarter!!!

  22. lwertz – 7 months ago

    While I see how this is a good move for Netflix, I can't help but feel royally screwed over as a developer. Will you be adding anything (some stability? more features? ability to play instantly outside of Netflix? anything???) to help keep the API useful? What are you leaving us? We can search and add things to instant queues now... super. You're making it very difficult to build services on top of Netflix that increase YOUR customer's experience.

    Throw us a bone here, Netflix. We're trying to make you money!

  23. David Chappelle – 7 months ago

    I must join the voices who question the linking of international streaming to the DVD API. It seems clear that based on this move, along with the recent pricing change, Netflix intends to abandon disc mailing in the future. Obviously I'm in the minority here, but I feel that streaming is so inherently inferior to discs that given the choice between streaming or nothing, I'd pick nothing, and go back to renting and buying discs. Most complaints about streaming are about the lack of selection. Even if 100% of all content were available on streaming, the quality would not be as good as blu-ray, and I don't have to worry about ISP data caps, lost connections, and browser plugins. I know young people are all about consuming video content on a tiny laptop screen, but I have a dedicated home theater that works best with optical media, not streaming.

  24. checkman – 6 months ago

    Removing the DVD queue features from the API prevents developers from helping Netflix to maximize profitability of the DVD services as those services are being phased out.

    Seriously, it cannot be cost-prohibitive to leave this part of the API in place. Move it to a different location if you have to. Deprecate it, and tell developers you won't be fixing bugs. But removing it altogether is shooting yourself and your community of developers in the foot.

  25. Jon Eisenstein – 6 months ago

    The one function I've been looking for has been to be able to sort my DVD queue by predicted rating, which appears to be on its way out if it isn't already. Is there any possibility that this will be possible in the future? (i.e., allow reading of the DVD queue, and be able to view those titles with their associated predicted rating for the user?)

  26. Matthew Foster – 5 months ago

    David- Now that the separation of the Streaming and DVD businesses has been announced, can you officially comment whether Qwikster will have a similar API so that we can once again manager our DVD queues? Thanks,

  27. Manish – 5 months ago

    Can't it be done in a way that these end points are still there, and they go to either Qwikster or Netflix, depending on whether we are adding movies to DVD queue or Instant Watch queue?

  28. Manish – 5 months ago

    Will Qwikster have these APIs? Will it be possible for apps developers to connect to Qwikster in a similar way that Netflix does?

  29. Mike – 5 months ago

    Yes, the question about a Qwikster API is a big one. We're in a holding pattern until Qwikster lights up and .... help us all, please have an API that does at minimum what the Netflix API did.

  30. Edward Petersen – 5 months ago

    I'm afraid I haven't read all of the comments here, but I was wondering if anyone has touched on the categories issue? It seems to me that several of those categories that are being depreciated are not necessarily DVD-only related. Why are they going away if they are useful for all titles, regardless of delivery method? Like genre, MPAA ratings, etc.?

  31. slvr32 – 4 months ago

    And the next question, following the Qwikster reversal announcements in the last couple of days...

    Any plans to reverse the removal of DVD functions in the API, i.e. hold still for a minute so a developer can write an app with known/stable API functionality?

  32. Matthew Foster – 4 months ago

    I would like to echo slvr32's comment. Now that the Qwikster decision has been reversed, please also reverse the DVD removal from the API. You earned back some credibility from your paying customers today. Thanks!

Please sign in to post a comment.