Is the API Rate Limit per API Key or APP ID?

[Chester_McLaugh]

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!

[Tuur]

I’m not sure how they calculate it, but I’ve fired bursts of calls (like you) before without running into problems…

[Roman_Scher]

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.

[Sachal_Lakhavan]

@airtable_team do you know if this has been changed to “API key and base ID” yet? Thanks!

[Cube_Dev]

is this limitation still on Airtable ??

[Denji_Mo]

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?

[kuovonne]

Denji_Mo:

if more than 100 people with different IPs access and record in one base from their cell phones

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.