Netflix API Developer Blog
Changes to the Public API Program
The changes, outlined below, are designed to allow us to focus our API efforts on supporting the products and features used most by our members. They are also designed to allow us to continue to offer the public API program in a way that aligns with our goals.
The following are the changes we are making to the program, all of which are effective immediately (except where otherwise noted):
Daniel Jacobson
Director of Engineering – Netflix API
----
Source: http://developer.netflix.com/blog/read/Changes_to_the_Public_API_Program
Now that doesn't help getting a MP plugin for Netflix...
Changes to the Public API Program
- Daniel Jacobson
- 2 weeks ago
The changes, outlined below, are designed to allow us to focus our API efforts on supporting the products and features used most by our members. They are also designed to allow us to continue to offer the public API program in a way that aligns with our goals.
The following are the changes we are making to the program, all of which are effective immediately (except where otherwise noted):
- We will no longer issue new public API developer keys. All existing keys that are actively calling the API will remain active.
- We will no longer accept new API affiliates. There will be no impact to existing and active affiliates.
- We will no longer offer test environments. The test tools have been unavailable for a while and we won’t bring them back.
- We will set the forums in the developer portal to read-only. We encourage developers to continue their conversations at StackOverflow with the tag “netflixapi”. The existing forum posts will remain on the site for now in the form of an archive.
- We will retire the OData catalog, effective on April 8, 2013.
Daniel Jacobson
Director of Engineering – Netflix API
----
Source: http://developer.netflix.com/blog/read/Changes_to_the_Public_API_Program
Now that doesn't help getting a MP plugin for Netflix...