Hey @Abraham_Bochner!
When utilizing the Airtable Web API, there is a flat API request limit of 5 requests per second per base.
Beyond that API limit, some of the endpoints have certain limitations that you need to be aware of.
Here are some that I can think of off the top of my head:
| API Endpoint | Limitation |
| List Records (GET) | Results are paginated for calls that return more than 100 records. |
| Record Upserts (PATCH & PUT) | A maximum of 10 records objects can be passed in the records array in the update or upsert request. |
| Update Record (PATCH & PUT) | A maximum of 10 record objects to update can be passed in the records array in the request. |
| Create Records (POST) | An array of up to 10 record objects can be passed. |
| Delete Records (DELETE) | An array of up to 10 record IDs can be passed at a time. |
If you're using scripting, there are also limitations on the number of times some of the methods on Airtable's built-in objects can be called. I'm not certain on the exact number, but as an example, I believe that if you call more than thirty asynchronous operations on a table object (think table.updateRecordAsync() or table.selectRecordAsync()), then the script will return an error.
There is not a way to increase your API request limits.
If you are consistently pushing your rate limits, you should consider implementing a caching layer to your data. There are many added benefits of doing so and it will allow you to comfortably scale your application(s) without having to worry about working around the API limits.
