It means when your stash is used to add rows as Thinh mentioned
We have plans to roll out a new version of Glide Tables that is more compatible with Big Tables. That will be compatible with API 2.0 whereas Legacy Glide Tables will never be
2 Likes
Sure, thanks.
After calling List Tables I noticed there are 2 copies of the table with the same name with different IDs. I really do not want to just fire these API call trying to locate which table is which because there’s a risk of breaking something, would be great to be sure correct IDs are displayed under “Show API”.
2 Likes
This is a good callout. Yes, you need to call the List Tables endpoint in the event of duplicated tables. We will look to improve Table ID visibility
1 Like
I cannot wait for this to be introduced to Glide Tables as well, really awesome update for sure. I just wish the Maker plan had access to the Call API feature, so many use cases we’re missing out on. 
3 Likes
When will you enable the API for Maker? I have a client with a food distribution business, approximately 1,000 customers, but they need to update prices and inventory from their ERP. Within Maker, we could have thousands of users, but we don’t have the API, and if we upgrade to Business, the project can’t be scaled to 1,000 customers at $6,000 per month. So, for us, it would be great to have API access in the Maker plan, even if we have to pay for more upgrades. Someone once suggested something similar; the truth is, you’re stuck at a point where no plan fits the bill.
2 Likes
Have you considered contacting Glide Sales to see what they can offer?
2 Likes
Hi Jeff, I haven’t contacted Sales, but really giving that power to the Maker plan with a simple function like the API (Update, Add, Delete) to update tables I think would be great, charging for it as appropriate with more updates, this would make the same difference as the Business plan since it would only be enabling the API of the tables. In the case of having to communicate with external services we would do it with Hooks or parameterized URLs, failing that, Make with automations, but think about it, with that simple function, the Maker plan would be a great product for many projects that are currently left halfway, as is our case, where the Maker plan works for us because of the users we are going to manage, which would be 1,000, but we are missing the API to update the tables from the ERP, and in Business it cannot be done, it is not viable for any project that requires many users and is used in a true business environment. Think about it, and if you can confirm that I contact sales to arrange a price just to activate that function, that would be great. I want to add that, when looking at the new plans, we always miss the $125 plan, which was in the middle of the Maker and Business plans. It was great and allowed API access. Glide is a great product, but the feature cuts make it unsuitable for many projects. Thanks!
To be honest I don’t think Glide would be to excited about a business with 1000 customers getting away with just the Maker plan. I understand you need the users and that number of users would blow out the price on other plans. That’s why I mentioned contacting Sales. They will do custom plans and could maybe accommodate you for something more reasonable, but you won’t know if you don’t ask. It won’t be nearly as cheap as the Maker plan, but also probably won’t be nearly expensive as the business plan with that number of users.
3 Likes
Dear Jeff, I really appreciate your responses and the time you dedicate, but I’m not commenting with the intention of whether Glide likes it or not. If we have a company with 1000 clients from whom we collect food orders, many of those orders do not exceed 50 dollars, and not everyone buys on each round. To comment on business models and their profits, one must dive deep into each specific topic. I would not recommend such a company, nor would I offer a $6000 plan. Even though they have a thousand clients from whom they collect orders, this is absurd.
I am an advisor and developer, so I will always seek the cost-benefit balance by analyzing available tools. I will not delve into this because we’ve already discussed it on other occasions, and the stance is firm. Glide wants to charge based on the profits of companies…
If you sell a product (Maker) for 1,000,000 users, why should it bother you that it’s used for just 1000? The major issue always lies in the plans and the discussion about how the customer who subscribes uses it. We’ve already discussed this many times before.
We evaluated Glide for this, but the API doesn’t work in the plan that we, the users, need. They have a plan for sale for 1,000,000 users like Maker. We tried using it, but it lacks the API simply to update a table from the ERP. We looked at the plan that has the API, and it supports 30 users, so it’s discarded for this project. With WooCommerce, it’s robust, accurate, with great API functionality, no user limit at a $0 cost, and we integrated it with the ERP where prices, stock are updated, orders are taken, sent via Hook to the ERP, and order statuses are synchronized through the API.
We will continue evaluating Glide for simpler tasks. I could keep making comparisons and optimizations, but in my humble opinion, I believe you have a good product. However, please consider, as part of the Glide team, enabling the input API. With that, the Maker plan would gain power. A closed software is never really software; it needs to communicate with other applications.
Maker? Just connect Google sheet and do updating like you need. Like this you will save tons of updates instead API
2 Likes
As a fellow end user of Glide, I have no control how Glide runs their business. It doesn’t fit every use case out there, but at the same time they do offer customized plans through their Sales team. I have no idea what any of those custom plans look like, but generally I believe they can be better price-wise compared to what the Business plan would offer, depending on scale.
With that said, even if Call API is enabled, you still need to keep track of updates as Call API does use updates and the Maker plan has considerably less updates compared to the Business plan. Unless you’re able to take on the $0.02 charge per additional update.
Obviously you know how Glide pricing works along with their intentions for each plan, so I won’t dwell on that. All I can say is that Glide most likely values the Call API feature as a business feature. Not much else that I can do or say to help other than suggest you create a feature request or explore some of the third party integrations, such as Zapier or Make.
2 Likes
Maybe this should be the solution
@DJP is there a timeline for standard glide tables api v2?
My understanding is that the V2 API will never be available for regular Glide tables.
The op states the following: Note: API support for regular Glide Tables is coming soon.
Im assuming this is aimed at V2 as api support for regular Glide Tables already exists
hmm, maybe I am mistaken, but I could swear that I saw something recently that mentioned there was no plan to make the V2 API available for regular tables - because the back end architecture is totally different. Anyway, I’m sure DJP will clarify either way.
1 Like
Maybe a new version will be compatible
3 Likes
It would be a good idea to enable the API in the maker plans.
Sorry, this statement was unclear. We expect to migrate to a new version of Glide Tables that shares the same backend architecture as Big Tables. This new version of Glide Tables will be compatible, but the legacy version will not.
There is no definite timeline for this, so if you need to use API v2.0, Big Tables is your best bet.
6 Likes