My engineers use my account’s API key to POST information into our Airtable base. Sometimes the data doesn’t always come through, the POST request appears successful but the data won’t make it to the table. This happens a lot. I wonder if it’s because my engineer uses my account’s API key and since I have an open session using the base with my account Airtable gets confused as to how the same person is editing the base in two different ways…
We don’t have any code that prevents this sort of thing. Is their code giving back any errors from Airtable?
Hi EvanHahn, thanks for responding! Not as far as I know, I have asked them to reply on this thread so maybe they can give you more clarity. However, maybe it’s a rate limit issue? Is the rate limit per database or per API key? Either way, my personal experience with rate limits is that even if you hit the rate limit the server will cache the pending requests and process them later, is this not the case with Airtable APIs?
Our rate limit will start to give errors if you run up against them. I’d be curious to know what responses y’all are getting from the Airtable servers—that might help illuminate the issue.
We are going to add some extra logging to try find out what is causing this.
In the meantime, I have a question, can you tell me if the rate limit is per API Key or per database?
The rate limits for the public API endpoints are by base. (I admit we’re tweaking some of this so you may temporarily see higher rate limits than 5 requests per second per base, but please don’t rely on that—it should properly be 5 requests per second per base soon.)
Ya know - one way to defend the Airtable servers from unintentional rate-limit abuse is to simply expose an event model internal to the API (and/or webhooks) that allow us to integrate external processes without polling for change.
Wouldn’t now be like the perfect time for Airtable to pave the way for developers to use your platform more efficiently while expanding the innovation possibilities?
I completely understand that saying this is easy and there are vast complexities involved, but it seems that without an event model, you will be playing whack-a-mole with this data accessibility issue for a long time. And all the while, innovation will be constrained.
A webhook-style workflow is something that’s definitely on our radar. I don’t have any specifics I can share (though I’d like to tell all!!) but trust that this is something on our minds.
Thanks for responding @EvanHahn!
If I could I’d click that thumbs up 200 times. I figured you guys were on that pathway - kind’a goes without saying in the API economy.
Holler if you need an old guy to test it.