# Airtable API call reducing with Thunkable **URL:** \ **Category:** Questions about Thunkable X\ **Created:** [April 6, 2026, 2:59pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534 "2026-04-06T14:59:33Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![maurizio.polverini89](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/maurizio.polverini89/32/145191_2.png) [@maurizio.polverini89](https://community.thunkable.com/u/maurizio.polverini89)\ **Post date:** [April 6, 2026, 2:59pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/1 "2026-04-06T14:59:34Z")
Hello everyone, I hope you’re all doing well. I have a question regarding how data is retrieved from Airtable in Thunkable. My app is performing very well, and I’m currently working on reducing the number of API calls to Airtable as much as possible. However, I’ve noticed that when using certain blocks (like the one shown), the value returned is not always the most up-to-date. This makes me wonder whether Thunkable caches the Airtable data when the app starts, instead of making a fresh API call every time. ![image](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/9/5/954bc0c73c1b1e897da8bf93c0f8af42e28a7498.png) So my question is: Does this block trigger a new API call to Airtable each time it is used, or does it retrieve data from a locally cached version (possibly managed by Thunkable) that was previously fetched? I hope my question is clear. I look forward to your feedback. Thanks, Maurizio ---
**Author:** ![maurizio.polverini89](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/maurizio.polverini89/32/145191_2.png) [@maurizio.polverini89](https://community.thunkable.com/u/maurizio.polverini89)\ **Post date:** [April 10, 2026, 7:01am UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/2 "2026-04-10T07:01:34Z")
up ---
**Author:** ![brianl](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@brianl](https://community.thunkable.com/u/brianl)\ **Post date:** [April 17, 2026, 7:04pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/3 "2026-04-17T19:04:52Z")
@maurizio.polverini89 I believe there is some amount of caching that is done. I need to double-check with our engineering team on the exact details. I would highly recommend having caching within your own app, regardless. It does highly depends on what you are trying to build. I can give a better reccomendation if you can tell me what you are trying to do. ---
**Author:** ![maurizio.polverini89](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/maurizio.polverini89/32/145191_2.png) [@maurizio.polverini89](https://community.thunkable.com/u/maurizio.polverini89)\ **Post date:** [April 18, 2026, 10:49am UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/4 "2026-04-18T10:49:53Z")
Unfortunately the app has to take always the latest info from Airtable, so caching for this specific task is not a viable solution. Thank you for asking your engineering team - please let me know! ---
**Author:** ![brianl](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@brianl](https://community.thunkable.com/u/brianl)\ **Post date:** [April 20, 2026, 11:02pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/5 "2026-04-20T23:02:32Z")
I’ll have an answer on Wednesday when I speak with them, the engineer that I talk with was unfortunately out sick. In the meantime, I would personally use their api so I can manage the amount of calls going in and out. Since the database is designed to be as simple to use as possible, it means that it can’t be optimized in every use case. Depending on the kind of app you want to build/feature, it might also be worth looking at other db options. Off the top of my head, Xano and Baserow are some nice alternatives. ---
**Author:** ![maurizio.polverini89](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/maurizio.polverini89/32/145191_2.png) [@maurizio.polverini89](https://community.thunkable.com/u/maurizio.polverini89)\ **Post date:** [April 22, 2026, 8:57pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/6 "2026-04-22T20:57:09Z")
I wish i was at that stage @brianl , but thank you for your help. I’m not in the position right now to change root features, i do have already paying clients and the reliability of the app cant be placed in discussion with such big changes. Please let me know what your team say, i look forward this info, Thank again! ---
**Author:** ![brianl](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@brianl](https://community.thunkable.com/u/brianl)\ **Post date:** [April 23, 2026, 5:15pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/7 "2026-04-23T17:15:38Z")
So I talked with the engineer, and basically, there isn’t any caching anymore from the backend. Every time you use the blocks to get information from Airtable, it makes a new api call, so it should be the most up-to-date information. ---
**Author:** ![maurizio.polverini89](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/maurizio.polverini89/32/145191_2.png) [@maurizio.polverini89](https://community.thunkable.com/u/maurizio.polverini89)\ **Post date:** [April 23, 2026, 6:14pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/8 "2026-04-23T18:14:37Z")
It’s a very precious information, thank you very much for your help and please thank the engineer too. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)\ **Post date:** [July 22, 2026, 6:15pm UTC](https://community.thunkable.com/t/airtable-api-call-reducing-with-thunkable/4108534/9 "2026-07-22T18:15:16Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.