# Public Beta: Glide API v2.0 for Big Tables

**URL:** <https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382>\
**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:** 1

<div class="post-metadata">

**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:** [April 16, 2025, 9:47pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/1 "2025-04-16T21:47:35Z")

</div>

**Glide API v2.0 lets you work with Glide Big Tables programmatically.**

The new and improved API consumes significantly fewer updates than v1.

We’ve also introduced [stashes](https://apidocs.glideapps.com/api-reference/v2/stashing/put-stashes-serial) to let you easily import thousands of rows at a time.

[Try it for yourself in our interactive API docs.](https://apidocs.glideapps.com/api-reference/v2/general/introduction)

_Note: API support for regular Glide Tables is coming soon._

## Pricing

- **Add, Edit** , or **Delete** rows = 0.01 updates per row changed (100x cheaper)
- **Get** rows = 0.001 updates per row (no more rounding to 1 update per 1k rows)

## Walkthrough

https://www.loom.com/embed/3863de1c8f7e4df3a67a3c1715e89361

---

<div class="post-metadata">

**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:** [April 17, 2025, 12:31am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/2 "2025-04-17T00:31:38Z")

</div>

> [@DJP](#):
>
> Functionality is limited to Glide Big Tables but will be expanded to Glide Tables soon.

This will be huge. I love this API version and have been using its since beta. Thank you!

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [April 17, 2025, 5:51pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/3 "2025-04-17T17:51:58Z")

</div>



---

<div class="post-metadata">

**Author:** ![Dilip\_Adiga](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dilip_adiga/32/60330_2.png) [@Dilip\_Adiga](https://community.glideapps.com/u/Dilip_Adiga)\
**Post date:** [April 18, 2025, 11:12am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/4 "2025-04-18T11:12:49Z")

</div>

Hi DJP,

This is a great feature to have and really appreciate the work put here.

I was just wondering that if we are going to get Math column values or Rollup column values in the future versions of this API? is that something that will be considered?

@DJP Wanted to know as we are planning some features based on this.

Regards,  
Dilip

---

<div class="post-metadata">

**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:** [April 18, 2025, 2:52pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/5 "2025-04-18T14:52:47Z")

</div>

> [@Dilip\_Adiga](#):
>
> I was just wondering that if we are going to get Math column values or Rollup column values in the future versions of this API? is that something that will be considered?

I don’t think it’s likely, but is there a reason you don’t build your stuff around workflows that have access to computed columns?

---

<div class="post-metadata">

**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:** [April 18, 2025, 7:38pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/6 "2025-04-18T19:38:35Z")

</div>

Agree with Thinh here. If you are trying to use or perform a computation programmatically, workflows are your best option. [Glide doc](https://www.glideapps.com/docs/getting-started/introduction-to-workflows#the-workflow-editor) here for reference.

---

<div class="post-metadata">

**Author:** ![Eitan](https://avatars.discourse-cdn.com/v4/letter/e/aca169/32.png) [@Eitan](https://community.glideapps.com/u/Eitan)\
**Post date:** [April 18, 2025, 10:11pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/7 "2025-04-18T22:11:44Z")

</div>

Great! This looks awesome.

I was just wondering about query parameters? In v1 of the API for big tables we could query with a limited set of SQL — can we still do this for v2 when getting rows?

---

<div class="post-metadata">

**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:** [April 18, 2025, 11:48pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/8 "2025-04-18T23:48:51Z")

</div>

That’s a good question and I used it a lot, I wonder if this is supported in v2 as well.

If not, I would just use the v1 method for it 😅

---

<div class="post-metadata">

**Author:** ![Mikaeldorval](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mikaeldorval/32/67405_2.png) [@Mikaeldorval](https://community.glideapps.com/u/Mikaeldorval)\
**Post date:** [April 23, 2025, 4:15am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/9 "2025-04-23T04:15:46Z")

</div>

Does that mean the make and zapier integrations consume only 0.01 updates when used on big tables?

---

<div class="post-metadata">

**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:** [April 23, 2025, 7:20pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/10 "2025-04-23T19:20:40Z")

</div>

No, this only applies to using the Glide API v2.0

---

<div class="post-metadata">

**Author:** ![Dilip\_Adiga](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dilip_adiga/32/60330_2.png) [@Dilip\_Adiga](https://community.glideapps.com/u/Dilip_Adiga)\
**Post date:** [April 24, 2025, 5:22am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/11 "2025-04-24T05:22:21Z")

</div>

Hi @ThinhDinh @DJP ,

Thank you for replying. My computed columns are basically Adding values from Multiple columns, Or multiplying, Or even rollup Columns etc,

These dont come in API response right ?

Regards,  
Dilip

---

<div class="post-metadata">

**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:** [April 24, 2025, 6:41am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/12 "2025-04-24T06:41:21Z")

</div>

> [@Dilip\_Adiga](#):
>
> These dont come in API response right ?

No, they don’t.  
As a general rule, computed columns are evaluated on the users device, and so they are not available in the backend, which means the API does not have access to them. A further complicating factor is that computed columns often give user specific results, and API queries cannot emulate any specific user.

---

<div class="post-metadata">

**Author:** ![Dilip\_Adiga](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dilip_adiga/32/60330_2.png) [@Dilip\_Adiga](https://community.glideapps.com/u/Dilip_Adiga)\
**Post date:** [April 24, 2025, 10:18am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/13 "2025-04-24T10:18:12Z")

</div>

Hi @Darren_Murphy ,

Thank you for replying.

If I have to get those values How can I work around them?

Regards,  
Dilip

---

<div class="post-metadata">

**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:** [April 24, 2025, 10:44am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/14 "2025-04-24T10:44:34Z")

</div>

You should use the new workflows if you intend to do something that’s related to computed columns. But granted, not all computed columns are supported, e.g JavaScript is not.

---

<div class="post-metadata">

**Author:** ![Dilip\_Adiga](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dilip_adiga/32/60330_2.png) [@Dilip\_Adiga](https://community.glideapps.com/u/Dilip_Adiga)\
**Post date:** [April 25, 2025, 3:23am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/15 "2025-04-25T03:23:55Z")

</div>

Hi @ThinhDinh ,

Thank you for replying. Let me try this and get back.  
Regards,  
Dilip

---

<div class="post-metadata">

**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:** [April 25, 2025, 1:36pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/16 "2025-04-25T13:36:40Z")

</div>

Hey Darren and all the Experts and @NoCodeAndy :

It certainly seems GBT is the future but still with caveats and work-arounds. I am finally about to move 4 google tables to glide big tables and want to make sure my App doesn’t break completely. The ‘good’ news is I don’t do too much ‘fancy’ in these google tables although I use the hashvalue computed column to create an Index that I write into other tables and then use as a Query/LookUp (I think that will break) as well as Querying computed columns between the two soon-to-be GBTs. The return set of these are \<100 but not sure if this query is allowed. (FYI these computed columns strip characters to find ‘fuzzy’ matches between the two tables).

Some general questions

if computed columns are usually evaluated on the users device:

- What are the 'today’s" design implications of using GBT with the computed column restrictions  
–Does and Don’ts. Specific work arounds?
- Is there a list of computed columns that are processed on the server versus the client?  
– LookUps? ITE? There have been (and continue to be) upgrades/changes to GBT and I am guessing this has to do with where processing occurs
- Is their a recent video or two or three highlighting the upgrades to GPT and design considerations (@Robert_Petitto @NoCodeAndy ??)

I have looked through pretty much everything in the community but much of it doesn’t take into account the latest updates to GBT which seemed to have major implications.

Thanks as always

---

<div class="post-metadata">

**Author:** ![Mikaeldorval](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mikaeldorval/32/67405_2.png) [@Mikaeldorval](https://community.glideapps.com/u/Mikaeldorval)\
**Post date:** [April 26, 2025, 2:53am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/17 "2025-04-26T02:53:04Z")

</div>

Is it possible to delete rows in bulk with a single api call like it used to work with mutations?

---

<div class="post-metadata">

**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:** [April 27, 2025, 12:26am UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/18 "2025-04-27T00:26:31Z")

</div>

Good question. I believe it’s a no considering the “delete” docs.

> **[Delete Row - Glide API Docs](https://apidocs.glideapps.com/api-reference/v2/tables/delete-table-row)**
>
> Deletes a row from a Big Table

However, I have never used this. If I need to delete rows, it has almost been a case of replacing the whole table with latest data so I use “overwrite table” anyway.

> **[Overwrite Table - Glide API Docs](https://apidocs.glideapps.com/api-reference/v2/tables/put-tables)**
>
> Replaces the schema and/or data of a Big Table

---

<div class="post-metadata">

**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 1, 2025, 7:59pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/19 "2025-05-01T19:59:33Z")

</div>

Just want to drop a big thanks for this feature, I’m going to implement it right away in a few places and I’m thrilled about how many headaches and compromises this resolves 😅

Fun fact is that for one project with invoice line-item reading we run into an API call cost issue because of the volume and insane number of items on some documents.

So, I came up with an idea and developed a fully functional work-around allowing to edit, add and delete line items, based on a single JSON array dynamically parsed out to display in UI.

And I did this… just one day before this post dropped 🤣

Glad I built that because it was fun but even more glad I’ll never need to do it again 😄

---

<div class="post-metadata">

**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 1, 2025, 9:48pm UTC](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382/20 "2025-05-01T21:48:39Z")

</div>

How does pricing work for “server-side” updates?

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?

Thanks

[Next page](https://community.glideapps.com/t/public-beta-glide-api-v2-0-for-big-tables/81382.md?page=2)