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?
Etkö löydä elokuvaa tai TV-ohjelmaa? Kirjaudu sisään lisätäksesi se.
Haluatko pisteyttää vai lisätä tämän nimikkeen listaan?
Ei rekisteröitynyt jäsen?
Vastaus käyttäjältä Travis Bell
12 elokuu 2013 klo 9:36AM
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
Vastaus käyttäjältä rustybailey
12 elokuu 2013 klo 10:05AM
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?
Vastaus käyttäjältä Travis Bell
12 elokuu 2013 klo 3:42PM
Hi rustybailey,
50 requests. There is no other way.
Vastaus käyttäjältä angelxmoreno
6 syyskuu 2013 klo 6:11PM
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
Vastaus käyttäjältä T.I.P
24 elokuu 2016 klo 12:36PM
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!
Vastaus käyttäjältä Travis Bell
24 elokuu 2016 klo 12:41PM
Hi T.I.P,
No this has not changed.
Vastaus käyttäjältä nkallen
20 lokakuu 2016 klo 12:28PM
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!
Vastaus käyttäjältä Travis Bell
20 lokakuu 2016 klo 6:15PM
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Vastaus käyttäjältä Alexey
10 heinäkuu 2017 klo 5:36PM
Another year passed, any chance? This is really necessary feature. Thanks!
Vastaus käyttäjältä Travis Bell
10 heinäkuu 2017 klo 5:53PM
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.
Vastaus käyttäjältä toshik
14 syyskuu 2017 klo 3:31PM
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?
Vastaus käyttäjältä Travis Bell
15 syyskuu 2017 klo 6:18PM
Hi @toshik There has been no change with regards to this.
Vastaus käyttäjältä toshik
15 syyskuu 2017 klo 7:01PM
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?
Vastaus käyttäjältä Travis Bell
18 syyskuu 2017 klo 3:44PM
We have no problems with you caching the data. That is perfectly fine.
Vastaus käyttäjältä Chris Krueger
27 syyskuu 2017 klo 5:16PM
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...