Assistance de TMDB
Assistance → Assistance de l'API
Query for multiple movies ids with a comma separated list?
posté par rustybaileySTAFFMOD le 11 août 2013 à 09h23
Is there a way to return data for multiple movie ids? I am trying to do something like this: http://api.themoviedb.org/3/movie/11,90?api_key=[blah] , but it's only returning the first movie. My main goal is to query a movie list and then get more info (such as duration) on each movie in that list. Is there just a way I can add a param to include more info in a list request?
Réponse de Travis Bell
le 12 août 2013 à 09h36
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
Réponse de rustybailey
le 12 août 2013 à 10h05
So if I want info on 50 movies, is themoviedb API's standard usage to send out 50 requests, or is there a more efficient way to do this?
Réponse de Travis Bell
le 12 août 2013 à 15h42
Hi rustybailey,
50 requests. There is no other way.
Réponse de angelxmoreno
le 6 septembre 2013 à 18h11
One thing to note @rustybailey is the limitation of 20 simultaneous connections and the fact the curl lets you make concurrent connections using multiCurl - here is an example of it http://multicurl.nisu.org/ - this might help make those 50 calls faster
Réponse de T.I.P
le 24 août 2016 à 12h36
Hi, has the situation changed anyhow after almost three years? I have a list of 15 IDs and need to show movie posters and titles. Now I do it in a loop but it is terribly slow. Please, surprise me and inform me about a new, more efficient, method.
Thank you!
Réponse de Travis Bell
le 24 août 2016 à 12h41
Hi T.I.P,
No this has not changed.
Réponse de nkallen
le 20 octobre 2016 à 12h28
I'm really happy with the TMDB API so far. But I really wish you had a multiget interface though! GET /movies/?id=1,2,3 would be nice and restful...
Currently my code sends parallel requests, and in order to avoid getting 429 rate limited I have to batch them at a controlled frequency. The code is a bit of a hassle and I'm sure it's more resource-intensive on your servers than you would like!
Réponse de Travis Bell
le 20 octobre 2016 à 18h15
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Réponse de Alexey
le 10 juillet 2017 à 17h36
Another year passed, any chance? This is really necessary feature. Thanks!
Réponse de Travis Bell
le 10 juillet 2017 à 17h53
Hi Alexey, there are still no plans for this. There's some potential changes up and coming around rate limits and before that were to ever change it could make sense to look at a multi get. But for now nothing is planned.
Réponse de toshik
le 14 septembre 2017 à 15h31
i was curious any change to be able to use this ?? I started building my android app few months ago and now its been put on halt because of this can you help?
Réponse de Travis Bell
le 15 septembre 2017 à 18h18
Hi @toshik There has been no change with regards to this.
Réponse de toshik
le 15 septembre 2017 à 19h01
hi @travisbell thanks for reply
I know this is for the good and ethical practices that is one should not store any data, not even movie id,
would it be problem if i save movie id and movie name on user machine(mobile android) not on the server solely on user device as saved movies?
Réponse de Travis Bell
le 18 septembre 2017 à 15h44
We have no problems with you caching the data. That is perfectly fine.
Réponse de Chris Krueger
le 27 septembre 2017 à 17h16
I can also fully agree with the previous post! :) We need a query for multiple movies! It blow up with too much requests when my app is running :D This is my only bottleneck...