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?
No trobeu una pel·lícula o una sèrie? Inicieu la sessió per a crear-la.
Desitgeu valorar o afegir aquest element a una llista?
No n'ets membre?
Resposta per Travis Bell
el 12 e de 2013 a les 9:36 A.M.
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
Resposta per rustybailey
el 12 e de 2013 a les 10:05 A.M.
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 per Travis Bell
el 12 e de 2013 a les 3:42 P.M.
Hi rustybailey,
50 requests. There is no other way.
Resposta per angelxmoreno
el 6 n de 2013 a les 6:11 P.M.
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 per T.I.P
el 24 e de 2016 a les 12:36 P.M.
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 per Travis Bell
el 24 e de 2016 a les 12:41 P.M.
Hi T.I.P,
No this has not changed.
Resposta per nkallen
el 20 e de 2016 a les 12:28 P.M.
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 per Travis Bell
el 20 e de 2016 a les 6:15 P.M.
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Resposta per Alexey
el 10 g de 2017 a les 5:36 P.M.
Another year passed, any chance? This is really necessary feature. Thanks!
Resposta per Travis Bell
el 10 g de 2017 a les 5:53 P.M.
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 per toshik
el 14 n de 2017 a les 3:31 P.M.
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 per Travis Bell
el 15 n de 2017 a les 6:18 P.M.
Hi @toshik There has been no change with regards to this.
Resposta per toshik
el 15 n de 2017 a les 7:01 P.M.
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 per Travis Bell
el 18 n de 2017 a les 3:44 P.M.
We have no problems with you caching the data. That is perfectly fine.
Resposta per Chris Krueger
el 27 n de 2017 a les 5:16 P.M.
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...