Skip to main content

Heya everyone!

So I noticed that on the Airtable update API endpoint they note about upserts:

Airtable reserves the right to throttle upsert requests differently from the standard rate limit throttling policy.


Intuitively, I’d assume that differently means that they’re more strict about it as they’d be doing comparisons on their end.

Does anyone know whether upsert is throttled more aggressively than plain updates? I’d assume so but I thought I’d get it cleared up.

Thanks!

Hi ​@Hok, I’ve looked around and haven’t found any evidence that Airtable is actually throttling upserts differently in practice. I also run a service built on top of Airtable’s API and haven’t heard such complaints from our users.

While they do “reserve the right” due to the increased cost of upserts compared to other operations, I would assume the lack of examples of this happening in practice most likely means they either don’t throttle upserts differently at all, or that they only do so in extreme cases. For now, I'd recommend implementing the same rate limiting strategy for both operations.


Perfect, thanks! That's exactly what I was concerned about. 


Reply