+1 for this. I just started using the API today, and immediately started looking for this feature. For social and media discovery apps, I daresay this is the most important API of all, especially given the recent disappearance of the built-in community features. Not that anyone noticed. ;-)
One other feature suggestion related to the ratings would be the ability to specify a level of response detail. A good example is the Amazon API, they let you specify ResponseGroup=Small or ResponseGroup=Large, which determines how much extra data you get about each item.
Obviously the default parameter could be the current format, but I've seen a number of people on the forum mention downloading the full title index, and if they're keeping that in a cache for 24 hours they really only need the item id (e.g. http://api.netflix.com/catalog/titles/movies/60027695) and user_rating (and possibly the parent item id, if the item is a disc/episode/season). All the other data is relatively static and could easily be cross-referenced from a recent copy of the title index.
This option would probably reduce the bandwidth usage of the ratings API a lot, once the ability to retrieve all of a user's ratings is implemented.
We've implemented this feature in the next release of the API. We're testing it out with some internal applications under development to make sure we've got it right before releasing it publicly.
Michael- Just to clarify, this thread started with a request to retrieve all of a user's ratings. Is this the feature you're now saying has been implemented? Do you have a release date for the API?
We're working with our legal team to make sure that various concerns are addressed before we release this. The final form of this feature has not been determined, and unfortunately, due to the nature of the issue, we can't give a date for when it will be available.
Please understand that it's as frustrating to us as it is to you, but there are a lot of issues and considerations that must be addressed before we can turn this feature on.
It looks like I'm waiting for this as well. I just started writing my application, and it turns out I need this feature. Good timing on my part, I suppose.
scurrilous – 2 years ago
+1 for this. I just started using the API today, and immediately started looking for this feature. For social and media discovery apps, I daresay this is the most important API of all, especially given the recent disappearance of the built-in community features. Not that anyone noticed. ;-)
Dan Hinsley – 2 years ago
Might as well add a +2 for this. It would be very handy to have.
Chloe – 2 years ago
I think I'd like to +3 for this. That would be very helpful.
unfair – 2 years ago
One other feature suggestion related to the ratings would be the ability to specify a level of response detail. A good example is the Amazon API, they let you specify ResponseGroup=Small or ResponseGroup=Large, which determines how much extra data you get about each item.
Obviously the default parameter could be the current format, but I've seen a number of people on the forum mention downloading the full title index, and if they're keeping that in a cache for 24 hours they really only need the item id (e.g. http://api.netflix.com/catalog/titles/movies/60027695) and user_rating (and possibly the parent item id, if the item is a disc/episode/season). All the other data is relatively static and could easily be cross-referenced from a recent copy of the title index.
This option would probably reduce the bandwidth usage of the ratings API a lot, once the ability to retrieve all of a user's ratings is implemented.
Michael Hart – 2 years ago
We've implemented this feature in the next release of the API. We're testing it out with some internal applications under development to make sure we've got it right before releasing it publicly.
cmiller19 – 2 years ago
Michael- Just to clarify, this thread started with a request to retrieve all of a user's ratings. Is this the feature you're now saying has been implemented? Do you have a release date for the API?
JR Conlin – 2 years ago
We're working with our legal team to make sure that various concerns are addressed before we release this. The final form of this feature has not been determined, and unfortunately, due to the nature of the issue, we can't give a date for when it will be available.
Please understand that it's as frustrating to us as it is to you, but there are a lot of issues and considerations that must be addressed before we can turn this feature on.
Devin – 2 years ago
It looks like I'm waiting for this as well. I just started writing my application, and it turns out I need this feature. Good timing on my part, I suppose.
davidratings – 2 years ago
What's the progress?
blckholehorizon – 1 year ago
bump. any new news?
Hupermagno – 1 year ago
very interesting article ... I hope this will continue
radomir – 1 year ago
Michael - any update on this feature? ETA? Thanks!
davidsalazar – 11 months ago
so is this not possible yet lol?
BuddyTV – 8 months ago
We need this feature!
LizD – 3 months ago
+1 for this feature!