Nov 17, 2016 11:29 AM
Is the API Rate Limit tied to an API Key? Or to an APP ID? Or a combination of both?
I have developed several websites that pull and/or sync data with Airtable, and while none of them individually will generate more than 5 requests per second, I’m now concerned that (since they’re all using the same API Key) they will collectively generate more than 5 requests per second.
However, if the Rate Limit is tied to the API Key and APP ID, I have nothing to worry about as each application is built using a different Airtable Base.
Please advise! Thanks!
Nov 21, 2017 07:56 AM
I’m not sure how they calculate it, but I’ve fired bursts of calls (like you) before without running into problems…
Feb 10, 2018 07:29 PM
From my testing, it looks as though 429 Rate Limiting currently occurs on a per-IP Address basis only, regardless of API Key used or Base queried.
For example, you could use 5 API keys, each querying a different base, and still get 429 Rate Limited because all the requests are coming from one IP Address.
May 22, 2019 10:26 AM
@airtable_team do you know if this has been changed to “API key and base ID” yet? Thanks!
Aug 06, 2020 06:40 AM
is this limitation still on Airtable ??
Jul 04, 2022 01:38 AM
So, for example, if more than 100 people with different IPs access and record in one base from their cell phones, is there no problem?
Jul 04, 2022 06:18 AM
Typically all their requests would go through the same server with the same API key.
To have all those different IP addresses, the code would have to run on the client, which would mean exposing the API key, which is a se unity risk. Or it would mean that users would have to provide their API keys, which has problems of its own.