Suporte do The Movie Database
Suporte → Suporte da API
Query for multiple movies ids with a comma separated list?
publicado por rustybaileySTAFFMOD em 11 agosto 2013 às 9:23 AM
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?
Resposta de Travis Bell
em 12 agosto 2013 às 9:36 AM
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
Resposta de rustybailey
em 12 agosto 2013 às 10:05 AM
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?
Resposta de Travis Bell
em 12 agosto 2013 às 3:42 PM
Hi rustybailey,
50 requests. There is no other way.
Resposta de angelxmoreno
em 6 setembro 2013 às 6:11 PM
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
Resposta de Tomáš
em 24 agosto 2016 às 12:36 PM
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!
Resposta de Travis Bell
em 24 agosto 2016 às 12:41 PM
Hi T.I.P,
No this has not changed.
Resposta de nkallen
em 20 outubro 2016 às 12:28 PM
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!
Resposta de Travis Bell
em 20 outubro 2016 às 6:15 PM
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Resposta de Alexey
em 10 julho 2017 às 5:36 PM
Another year passed, any chance? This is really necessary feature. Thanks!
Resposta de Travis Bell
em 10 julho 2017 às 5:53 PM
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.
Resposta de toshik
em 14 setembro 2017 às 3:31 PM
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?
Resposta de Travis Bell
em 15 setembro 2017 às 6:18 PM
Hi @toshik There has been no change with regards to this.
Resposta de toshik
em 15 setembro 2017 às 7:01 PM
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?
Resposta de Travis Bell
em 18 setembro 2017 às 3:44 PM
We have no problems with you caching the data. That is perfectly fine.
Resposta de Chris Krueger
em 27 setembro 2017 às 5:16 PM
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...