The Movie Database Support
Support → API-support
Query for multiple movies ids with a comma separated list?
Inlagt av rustybaileySTAFFMOD den 11 augusti 2013 vid 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?
Svar från Travis Bell
den 12 augusti 2013 vid 9:36 AM
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
Svar från rustybailey
den 12 augusti 2013 vid 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?
Svar från Travis Bell
den 12 augusti 2013 vid 3:42 PM
Hi rustybailey,
50 requests. There is no other way.
Svar från angelxmoreno
den 6 september 2013 vid 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
Svar från T.I.P
den 24 augusti 2016 vid 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!
Svar från Travis Bell
den 24 augusti 2016 vid 12:41 PM
Hi T.I.P,
No this has not changed.
Svar från nkallen
den 20 oktober 2016 vid 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!
Svar från Travis Bell
den 20 oktober 2016 vid 6:15 PM
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Svar från Alexey
den 10 juli 2017 vid 5:36 PM
Another year passed, any chance? This is really necessary feature. Thanks!
Svar från Travis Bell
den 10 juli 2017 vid 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.
Svar från toshik
den 14 september 2017 vid 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?
Svar från Travis Bell
den 15 september 2017 vid 6:18 PM
Hi @toshik There has been no change with regards to this.
Svar från toshik
den 15 september 2017 vid 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?
Svar från Travis Bell
den 18 september 2017 vid 3:44 PM
We have no problems with you caching the data. That is perfectly fine.
Svar från Chris Krueger
den 27 september 2017 vid 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...