Soporte de The Movie Database
Soporte → Soporte de API
Why does 'list details' return all items, and 'movie/tv ratings' return only 20 per page?
publicado por danelkhenSTAFFMOD el 1 de enero de 2017 a las 10:31
This makes it a bit hard to obtain movie/tv ratings, and makes it hard to cross-check existing movie id's against it (without resorting to making more requests). Is it possible to remove that limitation - perhaps by having an option to return only the 'ids' of the movies? This could work well for both 'list details' as well as 'ratings', as the rest of the data can always be retrieved using movie details.
Contestado por Travis Bell
el 1 de enero de 2017 a las 10:57
Hi @danelkhen When you say "list details" are you referring to v3 lists? v4 lists imposes a page limit like everything else now, and the v3 lists really never should have returned everything but that's how it was originally done so I can't change it now.
v4 might include more options like this but I doubt v3 ever will. The reality about v3 is that I don't have intentions on working on it very much. It's mostly in maintenance mode now and any work I decide to do on the API will be on v4. I'll be taking some time in a few months to look at what v4 might look like for functionality like this.
Contestado por danelkhen
el 1 de enero de 2017 a las 11:00
Oh, i thought that v4 is not yet 'production ready' and doesn't provide all apis, is it possible to already use it for everything?
Contestado por Travis Bell
el 1 de enero de 2017 a las 11:06
No, it is not able to do much beyond lists and some account features. For what has been implemented, it is production ready. It's actually what is powering all of those features here on the website, so it's being used every day by thousands of users 😉
Contestado por danelkhen
el 1 de enero de 2017 a las 13:23
Really? so why does the api key for v4 says "read only" - the website is definitely not readonly right?
Contestado por danelkhen
el 1 de enero de 2017 a las 14:19
ok, update: trying v4 authentication from browser, but failing on request_token because the browser first sends an OPTIONS request, which fails with lua exception:
https://api.themoviedb.org/4/auth/request_token (request is sent with { "Authorization" : "bearer "+read_access_token } header
...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:396: don't know how to respond to OPTIONS stack traceback: [builtin#19]: at 0x7f6d1a5a3320 Traceback
stack traceback: [C]: in function 'error' ...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:396: in function 'handler' ...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:130: in function 'resolve' ...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:161: in function <...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:159> [C]: in function 'xpcall' ...rrent/cache/luarocks/share/lua/5.1/lapis/application.lua:159: in function 'dispatch' ...api/current/cache/luarocks/share/lua/5.1/lapis/nginx.lua:214: in function <...api/current/cache/luarocks/share/lua/5.1/lapis/nginx.lua:212>
Contestado por Travis Bell
el 1 de enero de 2017 a las 15:01
Good find, I don't think I have any OPTIONS methods hooked up on v4. I'll look at this, this week sometime.