Netflix will be shutting down public API support for third-party developers

Posted Jun 14, 2014

Netflix is getting tougher with the way that third-party developers can use its content because it is supporting its public API by the end of the year.

Netflix VP of Edge Engineering Daniel Jacobson said that it would retire the public API program effective November 14th. Netflix launched its API six years ago as a way for third-party developers to access and point to content that users could get from Netflix.

Subscribers were able to use these services to check the availability to reserve DVDs and check for titles. It was also used to link directly to streaming content on the web.

Since Netflix now has over 35 million subscribers in the U.S. and 12.5 million internationally, Netflix does not seem to need third-party support to grow.

Over the last few years, Netflix cut back on what developers could do with the API. Last year, Netflix announced it would stop issuing new API keys to third-party developers, but it grandfathered in apps that were already using the API.

Here is an e-mail that Netflix sent to TechCrunch:

Netflix API Developers,

As Netflix continues to grow internationally, the emphasis of our engineering efforts is to satisfy a growing member base and a growing number of devices. To better focus our efforts and to align them with the needs of our global member base, we will be retiring the public API program. Effective on November 14, 2014, public API developers will no longer be able to access Netflix content. All requests to the public API will return 404 errors.

Thank you to for participating in the ecosystem throughout the years.

Daniel Jacobson

VP of Edge Engineering

Netflix will continue to work with a small number of partners, including: Instant Watcher, Fanhattan, Yidio, NextGuide, Flixster, Can I Stream It?, FeedFliks, Instant Watch Browser for Netflix

I am relieved about Instant Watch Browser for Netflix because I use that website all the time.