# Public Beta: Glide API v2.0 for Big Tables **URL:** \ **Category:** Archived Announcements\ **Created:** [April 16, 2025, 9:47pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382 "2025-04-16T21:47:35Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [May 2, 2025, 12:15am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/21 "2025-05-02T00:15:07Z")
Server-side updates still would count towards your updates the way they show in your workflows I guess. Assuming you use a scheduled trigger like this. ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/0/605b79cf13f2a79c6a3170d373f5985038766136.png) What shows in my usage is 10 updates. ![CleanShot 2025-05-02 at 07.14.31@2x](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/2/b2ab2b49e3f4ad969ea6769511dcfc238602f916.png) So going by your example, that would be 30k for 30k “edit row”. This post is more relevant for when you do API calls. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [May 2, 2025, 4:44am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/22 "2025-05-02T04:44:43Z")
> [@MattLB](#): > > Consider a workflow that loops on a big table that contains 30,000 rows updating a date column. > > Is that 30,000 gets plus 30,000 edits or $30 + $300? The loops don’t cost you any updates, but the edits will. When you look at a workflow run log, it’s pretty easy to calculate how many updates were used. ---
**Author:** ![Myles\_Chaput](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/myles_chaput/32/62176_2.png) [@Myles\_Chaput](https://community.glideapps.com/u/Myles_Chaput)\ **Post date:** [May 2, 2025, 1:27pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/23 "2025-05-02T13:27:16Z")
I would assume this is only partially true, because if you call the API from an http module then it would consume 0.01 updates while updating in bulk? ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [May 2, 2025, 1:58pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/24 "2025-05-02T13:58:32Z")
If you’re using the V2 API, then yes. But if you’re using the V1 API, then it’s one update per mutation. ---
**Author:** ![Myles\_Chaput](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/myles_chaput/32/62176_2.png) [@Myles\_Chaput](https://community.glideapps.com/u/Myles_Chaput)\ **Post date:** [May 2, 2025, 2:00pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/25 "2025-05-02T14:00:22Z")
This has the potential to be game changing! As my app pretty much completely runs on API calls, there is very little app interaction ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [May 2, 2025, 4:43pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/26 "2025-05-02T16:43:37Z")
Can’t wait till it’s available for Glide Tables. ---
**Author:** ![Myles\_Chaput](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/myles_chaput/32/62176_2.png) [@Myles\_Chaput](https://community.glideapps.com/u/Myles_Chaput)\ **Post date:** [May 2, 2025, 6:12pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/27 "2025-05-02T18:12:53Z")
Wait…IS this going to be available for glide tables?! ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [May 3, 2025, 12:09am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/28 "2025-05-03T00:09:10Z")
> [@DJP](#): > > Note: API support for regular Glide Tables is coming soon. Here. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [May 4, 2025, 11:45pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/29 "2025-05-04T23:45:23Z")
Net/net: it is a penny ($.01) per update for a Big Table row done through the API and $.00 if done within the app (e.g. have the row open in a screen and updating the date via a Set Col Value action). I think that is correct. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [May 4, 2025, 11:47pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/30 "2025-05-04T23:47:12Z")
> [@MattLB](#): > > $.00 if done within the app (e.g. have the row open in a screen and updating the date via a Set Col Value action). Yes, on non-Enterprise plans. ![CleanShot 2025-05-05 at 06.46.55](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/8/38fc1c2349a28ac16a404e0749d8f85589b257fc.png) But you can’t do it with 30k rows, if you ever need something like that. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [May 5, 2025, 3:10am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/31 "2025-05-05T03:10:55Z")
> [@ThinhDinh](#): > > Yes, on non-Enterprise plans. In-App updates to native tables are only counted on legacy plans now, including enterprise. ---
**Author:** ![Myles\_Chaput](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/myles_chaput/32/62176_2.png) [@Myles\_Chaput](https://community.glideapps.com/u/Myles_Chaput)\ **Post date:** [May 5, 2025, 8:46pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/33 "2025-05-05T20:46:17Z")
Once this is live for regular tables as well, I can finally change from my legacy plan, as the only reason i’ve been holding onto it is I get double the updates from API than current plans and for half the price. Cheers This isn’t true based on the math above, its 0.01 UPDATES per mutation, not dollars. Only through the V2 API. Someone can correct me if i’m wrong ---
**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\ **Post date:** [May 5, 2025, 9:48pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/34 "2025-05-05T21:48:58Z")
Best place to confirm pricing is our API documentation ([URL](https://apidocs.glideapps.com/api-reference/v2/general/introduction#pricing)) - Adding, updating, or deleting rows will use 0.01 updates per row changed - Getting rows will use 0.001 updates per row retrieved ### Screenshot ![Pricing](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/2/421a7c5b2a9ef8e8c875e867dae4d24045f601e3.png) ---
**Author:** ![idevnva](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/idevnva/32/87851_2.png) [@idevnva](https://community.glideapps.com/u/idevnva)\ **Post date:** [May 8, 2025, 10:34am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/35 "2025-05-08T10:34:58Z")
Tell me, will there be a price change for using Call API via Action? Just when changing one row or deleting one row, it still costs at least 1.01 actions ---
**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\ **Post date:** [May 8, 2025, 4:57pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/36 "2025-05-08T16:57:04Z")
No, updates for `Call API` are not being updated due to this change ---
**Author:** ![slscustom.ru](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/slscustom.ru/32/77336_2.png) [@slscustom.ru](https://community.glideapps.com/u/slscustom.ru)\ **Post date:** [May 9, 2025, 9:52am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/37 "2025-05-09T09:52:18Z")
From [https://apidocs.glideapps.com/api-reference/v2/general/introduction#pricing](https://apidocs.glideapps.com/api-reference/v2/general/introduction#pricing) What does “your commit your stash” mean? 1. Will the updates be applied to every row added to the stash? I mean, if you adding several rows in one call to stash how much it will costs? Update for each row? Or update for one call? 2. Or will they be applied to every row added from the stash to the table? When you overwriting table from stash(several rows inside stash) each row will consume updates? Or just one update ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [May 10, 2025, 12:56am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/38 "2025-05-10T00:56:41Z")
Just my guess, “commit” might mean you actually do something with the stash, not just stashing data to it. Those actions include: - Create table from stash - Overwrite table from stash - Add rows to table from stash ---
**Author:** ![Myles\_Chaput](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/myles_chaput/32/62176_2.png) [@Myles\_Chaput](https://community.glideapps.com/u/Myles_Chaput)\ **Post date:** [May 21, 2025, 2:05pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/39 "2025-05-21T14:05:31Z")
Is there an ETA for this to go live for the Glide Tables? ---
**Author:** ![Mariusz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mariusz/32/89415_2.png) [@Mariusz](https://community.glideapps.com/u/Mariusz)\ **Post date:** [May 21, 2025, 4:43pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/40 "2025-05-21T16:43:37Z")
@DJP I wanted to test the API on a copy of the table but then I realised in time that for the duplicated table the ID is the same, bearer is the same, column names are the same, and my test PUT request ended up targeting first 10 records of the wrong table. With previous API we had to include app ID which I guess would force the right table to be targeted. What are the possible ways to determine the right table to be targeted with API 2.0 when multiple copies of a table exist in one team? ---
**Author:** ![DJP](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/djp/32/62545_2.png) [@DJP](https://community.glideapps.com/u/DJP)\ **Post date:** [May 21, 2025, 4:58pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/41 "2025-05-21T16:58:37Z")
Can you send me the table names and the app IDs? I can take a look [Previous page](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382.md?page=1) [Next page](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382.md?page=3)