Hi CANALE83,

At this time we do not offer any premium or upgraded access. Everyone using our service must adhere to the same rate limits.

Keep in mind that these limitations are only imposed by IP address, and not API key. I've rarely heard from anyone that these limits cause an issue, especially with append_to_response.

Cheers.

Hi Travis,

The only limit i see is with /3/tv/{id}/season/{season_number}/episode/{episode_number} (if you want to have external_ids, videos for each episode). As you have to grab each episodes for each seasons, the limit will get very soon.

Travis,

Can you clarify the relation between append_response and rate limiting?

I understood the API documentation "This request is the same as making these 3 separate requests, all we're doing is combining the responses into a single response for you." as one combined request counting the same as three separate requests with regard to rate limiting.

One of my common queries is to ask for a movie including the directors and all directors alias names. I walk over all programs on TV, lookup all candidates for movies, collect all names, find out the best match (if any) and move on to the next program. With 1 director per movie and say 3 candidate movies for each movie in the guide I end up with 1 (search) + 3 (get the movie) + 3 (get the crew of each movie) + 3 (get the name aliases of each director) = 10 requests per movie on tv.

Due to a bug wrt caching on my side it takes ages to match a day of tv guide data against themoviedb. If combining the requests gives a benefit that would change the fix I have planned. (Basically completely replacing the themoviedb client api module and caching module with custom code that is optimized for my use case. Should I request all information of one movie in one or multiple requests and cache on that granularity.)

Hi skrobs,

The only limit i see is with /3/tv/{id}/season/{season_number}/episode/{episode_number} (if you want to have external_ids, videos for each episode). As you have to grab each episodes for each seasons, the limit will get very soon.

I guess it all depends on your needs. If you're attempting to create a local cache of data, crawling the API will take a while. If you on the other hand, have an interface where only certain data is showed to the user at a time, you can make these calls only as needed.

https://api.themoviedb.org/3/tv/1419/season/1?api_key=###

Shows a good amount of list data, if you need the external ids for each episode you'll have to hit each episode:

https://api.themoviedb.org/3/tv/1419/season/1/episode/1?api_key=###&append_to_response=external_ids

Now, you could try splitting up these calls and build something like this:

https://api.themoviedb.org/3/tv/1419/season/1?api_key=###&append_to_response=episode/1/external_ids,episode/2/external_ids

It gets a little crazy but it does work. We limit the number of append_to_response objects to 20.

Hi,

Yes i got a local cache of datas, it's easier for me to handle datas like i need.

BTW, yes, the append_to_response trick like crazy, but if it work, it's a good point ! Thanks