API request limit workaround

Hi everyone! )

Say there’s an Airtable database with 50 000 records and restricted to public.
We use a script to retrieve its data via Airtable API: php sdk GitHub - sleiman/airtable-php: A PHP client for the Airtable API.
This API has limits: 5 requests per second & 100 items per request.
If we try to get the data in a faster pace we go over limits and get blocked for 30 seconds by the server (429 status code and 30 seconds cooldown before subsequent requests will succeed)

Is there a way to get around these API restrictions and recieve the data quicker?

Thank you.

Not using only the REST API.

You can use a webhook automation that runs a script that gathers data for more records and then posts to the data to your server. Note that scripting automations have their limitations, but you should be able to get more than 500 records per second.

2 Likes

Thank you for the idea! :slightly_smiling_face: We’ll try this way.

One way to receive the data quicker is to not receive the data at all. :wink:

Has anyone tested the idea that Airtable’s API supports conditional GETS?

Have you seen documentation for using conditional GETs?

No - just hoping it’s an undocumented feature.

I would be super cautious about trying to use an undocumented feature of this scale. Plus, how would you even know what to include in your header with no documentation?

I can theoretically see conditional gets as useful at the record level, except that the data for a single record tends to be fairly small and probably not worth it for Airtable to build out the architecture. I don’t see how conditional gets would really work when getting a set of records, especially if you are using filterByFormula.

Furthermore, I don’t think that conditional gets would workaround the API request limit. The limit is on the number of requests received. A conditional get would still count as a request received.

Correct, but…

The nature of the API is such that any and all activity/bandwidth consumed affects all users and processes. Given that (at scale) Airtable struggles in the enterprise, conditional GETs and ETags can provide significant reduction in the number of requests an app may need to perform.

Imagine a request of a thousand rows turns up no changes; with conditional GETs the rows don’t have to traverse the internet, only a few bytes tell the requester that there are no changes. This information can be used to better pace the calls should there be known changes.

Airtable should be all over this.

Oh, I agree that that would be really nice. I just don’t think that it exists yet, and it would be a lot of work for Airtable to implement.

Don’t think so. They have event handlers to know if data has changed and when. They simply need to support response headers that share this information.

This topic was solved and automatically closed 15 days after the last reply. New replies are no longer allowed.