Query API updates not adding up

Our Query API calls seemed very high, so we put in extra logging on our side to figure it out and what we are seeing a 1:4 ration. For every one call we are making Glide is registering 4.

We are only using GET (bulk read) API call, on a table that has about 6000 rows.

Anyone else doing a bulk GET on a large table and are you seeing a higher number of calls. I am wondering if the size of the table increases the number of updates ?

The Glide counter doesn’t update in real time so we cannot do a verfication test.

So each GET call you do externally would register 4 extra Query API calls? How many rows are you trying to get?

Hi Thinh, I read the post and that doesn’t help me answer my question.

We have started to keep a full log of all the API Query calls we make, and what we are seeing is about 300 calls per day that we can account for. However we are seeing the Glide API calls counter going up at approximately 1500 per day. We have 6000 rows in our table. We don’t have a detailed log on glide side on how they came up with that number so we are playing bit of a guessing game.

I am thinking of taking a backup of the table and truncate it to see if that would make a difference but it does say upto 10k rows and we are below that

Search for a table called something like “SQL Audit Log”.

If you are using Big Tables, this audit log table is automatically generated, and every single action that happens with a Big Table (even Data Editor edits) is logged here. You might be able to use it to help identify where the updates are coming from.

1 Like

This is regular glide tables.

Found the root cause after assistance from support.

When using a bulk API query, you are charged 1 update for every 1000 rows. I have 6500 rows so that was 7 updates for each API call I was making.

The 10k limit is that you can get a max of 10,000 rows returned in a single response, but that will cost you 10 updates.

I had bad code on my side that was making about 250-300 calls per day, and also I was being lazy and not deleting the rows, so an expensive lesson :slight_smile:

1 Like

Thanks for sharing.