Rate limit for purging API
API reference says that authenticated requests are subject to a limit of 1,000 non-read requests per hour.
Is this limit applied to purging APIs?
When I made a purging request with API, I couldn't find Fastly-RateLimit-* headers in its response. This means purging APIs have no limit?
-
Thanks Pawel,
Unfortunately it's hard to say exactly how many requests we will send at this time, but 1000/h makes us a bit uneasy, and purging requests will increase as our service grows.
We are considering caching our API as you describe in your guide 'Enabling API caching'.
-
Shoji Murakami I don't know details about your service but it's not easy to exceed the limit, especially when we don't have any hard limitation for purging. You should also consider purging multiple surrogate key tags , It allows you to purge up to 256 surrogate keys in one batch request. If you are considering caching API, please check also purging API cache with surrogate keys. Don't hesitate to ask if you have any questions.
-
Pawel,
Ah yes, of course I know your wonderful feature `surrogate key`, and the batch operations with it. I'm going to use it.
Nevertheless, if purging has any limitation, I think we may have to consider not to exceed the limitation. So, my original question is to confirm that there's no limitation.
I've understood there's no hard limitation for purging at least this moment. I'll consider if need when that time comes.
Thank you a lot.
Please sign in to leave a comment.
Comments
4 comments