1/ Rate limiting is based on combination of API key and IP address, so you can use only one API key hardcoded in your app.

2/ TMDB serves over 3 billion requests a day (according to TMDB about page) without any noticeable problems.

3/ Don't know about Radarr, but Plex runs it's own cache layer (on their servers) between end users and TMDB API.

@talestalker said:

1/ Rate limiting is based on combination of API key and IP address, so you can use only one API key hardcoded in your app.

I'll add one clarification, rate limiting is only done by IP address. We don't take your API key into consideration.

I don't know where the limit of 20 connections per IP address came from. I can only answer you from my personal experience that if I need to do 150 requests at once, I split them into 3 batches of 50 requests each, which I do at the beginning of each measured second at once, and I have no problem. If I increase the load to say 60, I start getting HTTP Error 429 for the "extra" requests. I use javascript and promises.

Here I see only 50 request per second .

Here you can find the first comment or reply by @travisbell where he stated this '20 connection per IP' 8th july 2022, 7:43pm is the timing of that reply for locating the exact reply --- Btw when did you last used APIs from here and fired 50 calls at a time, if you didn't face any issue, I should also not worry about it.

@DhruvNetflix said:

Btw when did you last used APIs from here and fired 50 calls at a time, if you didn't face any issue, I should also not worry about it.

Right now:

updatePersonList(): Got 354 results (0 cached) in 8811 ms

@DhruvNetflix said:
Here you can find the first comment or reply by @travisbell where he stated this '20 connection per IP' 8th july 2022, 7:43pm is the timing of that reply for locating the exact reply --- Btw when did you last used APIs from here and fired 50 calls at a time, if you didn't face any issue, I should also not worry about it.

This was said by:
Reply by Travis Bell STAFF
on July 8, 2022 at 11:13 AM
I believe that from 2022 to today there have already been changes.

Can you please tag or bring travis bell here @travisbell to clarify whether changes took place or not since 2022

@talestalker said:

@DhruvNetflix said:

Btw when did you last used APIs from here and fired 50 calls at a time, if you didn't face any issue, I should also not worry about it.

Right now:

updatePersonList(): Got 354 results (0 cached) in 8811 ms

Hey, I have no idea what you did here, probably updated the data, but that's an admin privilege right? the rate limit maybe different there or maybe rate limits are not defined from moderator handle

@DhruvNetflix said:

Can you please tag or bring travis bell here @travisbell to clarify whether changes took place or not since 2022

They did. See here a year later.
https://www.themoviedb.org/talk/6442ced4d35dea02fcfb0fab#6442d4a0d35dea0455fb1a07

And Travis Bell is already part of this conversation.
https://www.themoviedb.org/talk/5d34aec717792c0011bc9bd9#5d34c7bd17792c0014bcd438
Let's wait for him to stop by.

I used the standard Personal API key. User status (mod/user) has nothing to do with it.

• guys, I just tested the API in a demo app on my local machine, I made 80 api calls at the same time/at once using Prmomise.all and all of them were resolved.
  
• Is the limit removed or is it because it is running on my local machine and development environment or will it throw error in production environment when I'll deploy it somewhere ? @travisbell hello travis, would really like a confirmation please

The only limit is a rough rate limit of ~40 requests per second by IP address. You might get a bit more more from time to time, but generally that is the approximate limit.