Usage of the API has increased recently, so to keep things running nice and smooth for everyone we need to introduce a rate limit
What's the limit?
Quite simple - 5 per second per customer API key. Our logs show that most consumers should be fine with this, but if you've written code that fires multiple API calls at the same time, then you may want to change that to work sequentially, so the requests go out one at a time.
What happens if I hit the limit?
You'll get a
429 status code result and the request will fail. You'll also get some information in the body of the response telling you what the current rate limits are.
Might this change in the future?
It's possible that this limit may be reviewed and changed in the future. You can find the latest rate-limit information by logging into Timetastic and heading to the API page. You can also review the response headers we send back when you call the API - in particular, we pass back "X-Rate-Limit-Limit" and "X-Rate-Limit-Remaining" which detail the current rate limit period (5s for 5 seconds), and how many calls you have remaining for that period.
When does it come into force?
We'll be activating the API limit on the 20th February 2018.