The Movie Database 지원
지원 → API 지원
Query for multiple movies ids with a comma separated list?
8월 11, 2013일 9:23 오전시에 rustybaileySTAFFMOD님이 게시함
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?
Travis Bell님의 댓글
8월 12, 2013 at 9:36 오전
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
rustybailey님의 댓글
8월 12, 2013 at 10:05 오전
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?
Travis Bell님의 댓글
8월 12, 2013 at 3:42 오후
Hi rustybailey,
50 requests. There is no other way.
angelxmoreno님의 댓글
9월 6, 2013 at 6:11 오후
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
Tomáš님의 댓글
8월 24, 2016 at 12:36 오후
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!
Travis Bell님의 댓글
8월 24, 2016 at 12:41 오후
Hi T.I.P,
No this has not changed.
nkallen님의 댓글
10월 20, 2016 at 12:28 오후
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!
Travis Bell님의 댓글
10월 20, 2016 at 6:15 오후
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Alexey님의 댓글
7월 10, 2017 at 5:36 오후
Another year passed, any chance? This is really necessary feature. Thanks!
Travis Bell님의 댓글
7월 10, 2017 at 5:53 오후
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.
toshik님의 댓글
9월 14, 2017 at 3:31 오후
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?
Travis Bell님의 댓글
9월 15, 2017 at 6:18 오후
Hi @toshik There has been no change with regards to this.
toshik님의 댓글
9월 15, 2017 at 7:01 오후
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?
Travis Bell님의 댓글
9월 18, 2017 at 3:44 오후
We have no problems with you caching the data. That is perfectly fine.
Chris Krueger님의 댓글
9월 27, 2017 at 5:16 오후
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...