Netflix solves this in 2 ways - per-user limits, but that requires users to authenticate before using the api. The other way is they make daily XML dumps available of their data so you can process those daily and build your own DB. Not sure if RT wants to do that though.
Personally I cache some of the RT results in a DB so I can reduce the calls into the api, while making sure I keep in line with the TOS
My users all have local databases, and the results are cached as local information in the files. However, I still have the issue that we would need more calls if all of my users were to use this API
Interesting... I would have expected the limit to be based upon IP at least, not solely on API calls. This strikes me as odd as any application that's remotely popular would easily use 10.000 calls. Did anyone run into this limit, this way? I'm assuming one would need a Rotten Tomatoes (or netflix) account for per-user limits?
I've just checked the logs of the API usage, and we seem to be going over the limit once a week or so, this is with the functionality set to optional at the moment. If I was to turn in on as a permanent feature, we'd blow through the limits in no time.
Hi Omertron,
I've raised your limits. Given the numbers you quoted, I am unsure if this new limit will continue to meet your demands. For further increases to your limit, please contact us at licensing [at) flixster-inc.com
Is there a way to increase the API limit?
I released this feature to my users the other day and they have already blown through the 10,000 calls per day limit with only a few users using it.
Each of my users has on average 500 movies, so the API key only supports 20 users (scanning their libraries from scratch)
I'd rather not go down the route of maintaining multiple API Keys (and I'm sure you wouldn't either)
Message edited by Omertron 2 years ago
Tags
mosdl – 2 years ago
Netflix solves this in 2 ways - per-user limits, but that requires users to authenticate before using the api. The other way is they make daily XML dumps available of their data so you can process those daily and build your own DB. Not sure if RT wants to do that though.
Personally I cache some of the RT results in a DB so I can reduce the calls into the api, while making sure I keep in line with the TOS
Omertron – 2 years ago
My users all have local databases, and the results are cached as local information in the files. However, I still have the issue that we would need more calls if all of my users were to use this API
12aon – 2 years ago
Interesting... I would have expected the limit to be based upon IP at least, not solely on API calls. This strikes me as odd as any application that's remotely popular would easily use 10.000 calls. Did anyone run into this limit, this way? I'm assuming one would need a Rotten Tomatoes (or netflix) account for per-user limits?
Omertron – 2 years ago
I've just checked the logs of the API usage, and we seem to be going over the limit once a week or so, this is with the functionality set to optional at the moment. If I was to turn in on as a permanent feature, we'd blow through the limits in no time.
Omertron – 2 years ago
For example, on August 14th & 15th we used 32k and 43k requests, which obviously means that 22K and 33k requests were denied to my users.
Please please please, give us the option to raise the limits!
Steve N. – 2 years ago
Hi Omertron, I've raised your limits. Given the numbers you quoted, I am unsure if this new limit will continue to meet your demands. For further increases to your limit, please contact us at licensing [at) flixster-inc.com
Omertron – 2 years ago
Hi Steve, thanks for that, it seems to be helping some looking at the graphs
Regards
Stuart