*Glide api updates usage bugged
*
Team ID:
App ID:
Description
-
I started using api recently, and when I read about it, it was said it uses ONE update per 1k rows. I just checked my usage for this month saying that the glide api used over 4.5k updates.I don’t remember using it for over 4 milion rows. This must be a bug. I am using a python script that takes the rows from somewhere else ( external app ) and uploads the new invoices ( yes it checks it from the cache of the script and has the last invoice number sent to glide so it doesn t get the rows again from glide ). We have been using this for tests first, but it’s only been for a week now. It seems impossible to get over 4.5k updates
Are you also using call API columns?
Which version of the API are you using?
V1 is one update per mutation (add/edit/delete row)
2 Likes
Call api was used once for only one table and the result was stored in a cache file, so it doesn’t call for it multiple times ( even if it was used 3-4 times, the table had less than 100 rows not almost 4 milion )
I used the “show api” that’s given in the Data→ Show Api
Okay, that’s V1.
And as I said, V1 charges one update per mutation. So if you add or update 100 rows, for example, that would be 100 updates.
V2 charges less, but only works with Glide Big Tables.
I analyzed the documetation and checked the “show api” for the specific table ( right click on table → show api ) as in the documentation, but it gives the same thing as what I used before, but I will try like this and check what happens. I used the api for glide big tables, but I do have one table for inventory which is a simple table and had to get the rows once from there too with the api, and I got almost 3k rows in there, so probably that’s why it charged 3k updates ( as u said, 1 update per row in normal tables ). I didn’t know it charges differently for table type
Get Rows in the V1 API is one update per call. So fetching 3000 rows should be only 2 or 3 updates.
1 Like
