Currently to remove from the queue requires using the DELETE headers. Problem is that when working with flash player you only have access to post and get. Please provide a secondary method so I can finally complete the actionscript API.
You can attach an argument called "method" to override the HTTP transfer method. (e.g. you'd add "method=DELETE" to delete a title). "method" works on all calls and is of particular use for both you and folks using JSONp.
Hmm... That works for me. Be sure to call it with the right form.
Let's say that I have a movie in my available queue
http://api.netflix.com/users/T123xxx.Insert.UserID.Here--/queues/disc/available/3/70117672 (The top notch flick "Giant Shark vs. Mega Octopus")
Hours pass, I wake up from my stupor and realize my mistake. The way to delete it is to call that movie's ID passing it two values:
The "etag" was returned as part of the queue list call and we use that to know what "version" of the queue you're talking about.
That should return a status of "success" indicating that the movie is now removed from your queue.
I'll note that passing "method=DELETE" to http://api.netflix.com/users/T123xxx.Insert.UserID.Here--/queues/disc/available doesn't work because you can't delete the user's queue. (Remember, REST says that the URL part is what you're acting on and the "method" is what you want to do. So you "POST" a movie to the queue, but "DELETE" the individual movie from the queue.)
Currently to remove from the queue requires using the DELETE headers. Problem is that when working with flash player you only have access to post and get. Please provide a secondary method so I can finally complete the actionscript API.
Message edited by jonbcampos 2 years ago
Tags
JR Conlin – 2 years ago
*poof* There already is one.
You can attach an argument called "method" to override the HTTP transfer method. (e.g. you'd add "method=DELETE" to delete a title). "method" works on all calls and is of particular use for both you and folks using JSONp.
jonbcampos – 2 years ago
Thank you, I didn't know about that!
jonbcampos – 2 years ago
I've tested it with a delete call and it failed. For the call would you be wanting it in POST format or just GET?
JR Conlin – 2 years ago
Hmm... That works for me. Be sure to call it with the right form.
Let's say that I have a movie in my available queue
http://api.netflix.com/users/T123xxx.Insert.UserID.Here--/queues/disc/available/3/70117672 (The top notch flick "Giant Shark vs. Mega Octopus")
Hours pass, I wake up from my stupor and realize my mistake. The way to delete it is to call that movie's ID passing it two values:
http://api.netflix.com/users/T123xxx.Insert.UserID.Here--/queues/disc/available/3/70117672?method=DELETE&etag=1234
The "etag" was returned as part of the queue list call and we use that to know what "version" of the queue you're talking about.
That should return a status of "success" indicating that the movie is now removed from your queue.
I'll note that passing "method=DELETE" to http://api.netflix.com/users/T123xxx.Insert.UserID.Here--/queues/disc/available doesn't work because you can't delete the user's queue. (Remember, REST says that the URL part is what you're acting on and the "method" is what you want to do. So you "POST" a movie to the queue, but "DELETE" the individual movie from the queue.)
Does that help?
jonbcampos – 2 years ago
JR,
I know that we went back and forth with this and there seems to be a bug in the system. Is a fix worked out?
Jonathan