Designing for Airtable API Limits

I’m hitting Airtable’s monthly 100k API limit much faster than expected these days. I’ve got an internal tool for about 40 users.

We have about 3k records. Some pages load up a ton of records at once (I use the infinite scroll tables, for instance.)

Does anyone have any tips/advice on how to design to limit the number of API calls I’m making? Or is this a fool’s errand and I should just pay for more?

(…and before someone says it – yes, I’m very much considering moving entirely to Softr’s databases. But we are mid-project and it’s going to be hard to move over right away).

Hi,

Here is a documentation page about it: Troubleshooting Airtable API call limit exceeded – Softr Help Docs

You can try removing infinite scroll as a minimal solution (pagination to be preferred) — but upgrading your Airtable plan might end up being necessary sooner than you think, unfortunately :sweat_smile:.