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 的回复
于 2013 年 08 月 12 日 9:36上午
Hi rustybailey,
We do not currently have the ability to query multiple ids at once.
rustybailey 的回复
于 2013 年 08 月 12 日 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 的回复
于 2013 年 08 月 12 日 3:42下午
Hi rustybailey,
50 requests. There is no other way.
angelxmoreno 的回复
于 2013 年 09 月 06 日 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áš 的回复
于 2016 年 08 月 24 日 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 的回复
于 2016 年 08 月 24 日 12:41下午
Hi T.I.P,
No this has not changed.
nkallen 的回复
于 2016 年 10 月 20 日 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 的回复
于 2016 年 10 月 20 日 6:15下午
Hi nkallen,
Thanks for the note. We don't have any plans to change this right now.
Alexey 的回复
于 2017 年 07 月 10 日 5:36下午
Another year passed, any chance? This is really necessary feature. Thanks!
Travis Bell 的回复
于 2017 年 07 月 10 日 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 的回复
于 2017 年 09 月 14 日 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 的回复
于 2017 年 09 月 15 日 6:18下午
Hi @toshik There has been no change with regards to this.
toshik 的回复
于 2017 年 09 月 15 日 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 的回复
于 2017 年 09 月 18 日 3:44下午
We have no problems with you caching the data. That is perfectly fine.
Chris Krueger 的回复
于 2017 年 09 月 27 日 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...