whenever i attempt to use http://api.netflix.com/catalog/titles/index, i get this response...
<status>
<status_code>403</status_code>
<message>Over queries per day limit</message>
</status>
the puzzling part is that it has now been over 48 hrs since i was able to successfully use that function. so unless my query per day limit is zero, something isn't right. other API functions are working fine, just this one is a problem.
We currently have a unique 20 requests/day limit on this resource currently, since it is such a large file and shouldn't need to be accessed frequently (it updates daily). That being said, 48 hours is too long. Investigating.
We've increased this limit substantially in the short-term to give users of this API some more headroom. Ideally, we'd have a unique access limit per-developer for this resource but that is not supported just yet, so we have to keep overall access to the resource by all developers relatively low for now. Hope the increased limit helps in the short term.
To prevent further "are we there yet" type comments, I'm going to lock this thread. When we re-adjust the limits, we will notify everyone via either the blog or forum.
Thanks!
[ Page 1 of 1 ]
This topic is locked and new posts are not allowed
whenever i attempt to use http://api.netflix.com/catalog/titles/index, i get this response...
<status>
<status_code>403</status_code>
<message>Over queries per day limit</message>
</status>
the puzzling part is that it has now been over 48 hrs since i was able to successfully use that function. so unless my query per day limit is zero, something isn't right. other API functions are working fine, just this one is a problem.
Message edited by JR Conlin 3 years ago
Michael Hart – 3 years ago
We currently have a unique 20 requests/day limit on this resource currently, since it is such a large file and shouldn't need to be accessed frequently (it updates daily). That being said, 48 hours is too long. Investigating.
Michael Hart – 3 years ago
We've increased this limit substantially in the short-term to give users of this API some more headroom. Ideally, we'd have a unique access limit per-developer for this resource but that is not supported just yet, so we have to keep overall access to the resource by all developers relatively low for now. Hope the increased limit helps in the short term.
roy – 3 years ago
Hi,
Is this limitation still applicable today (1/1/2009)?
Thanks
Michael Hart – 3 years ago
Yes, it is.
royce – 3 years ago
Hi there, is this limit still in effect? 2/3/09?
Unknown – 3 years ago
To prevent further "are we there yet" type comments, I'm going to lock this thread. When we re-adjust the limits, we will notify everyone via either the blog or forum.
Thanks!