A shame reallyā¦
ā¦at this point learning to code might just be a worthy investment especially for people in emerging markets or āthird world countriesā.
At $250/month just to learn (or have access to use) what type of solutions you can build with Glide API Call is not viableā¦
Oh wellā¦
Hello 
Pythonā¦
We are releasing a new feature, and this addition to Glide makes it less viable now?
We also have a Business trial if you want to try it.
Learning to code is always a worthy investment, in any case, but you will not be able to make something like a Glide app with Python.
I would love to try the business plan but at the moment, I just cannot afford it and I donāt see the point of working on something and then after 2 weeks have to decommission it due to costsā¦
I am currently on a starter plan and even that it is mainly for learning purposes for now.
I have been using Glide for close to 2 years now and I have been on and off the ābasicā paid packages just so that I can have access to learn Glide features which are not available on the free plan.
For me to make an investment of $250 per month just to be able to have access to learn the use of Glideās API and what type of solutions I could come up with is a bridge too far.
It would have been nice to have even limited access on the Pro plan but as you say, there is a new feature that complicates things.
I know that Glide is predominantly focussed in the US Markets and this is reflected in the pricing methodology but it would be nice to also see some form of plans towards emerging markets especially in Africa and the far east which may present greater opportunities for growth compared to the US which has vast alternatives for such solutionsā¦
Iām so annoyed right now. Glide wants $250 so we can use the call API action.
I donāt like how they are deferring their best features to unaffordable plans, the paywalls for innovation are getting too high, and itās short-sighted.
Itās my fault that I built something operational with the feature. But come on guys what the heck is this doing behind $250?
I believe the vision is to reach 1 billion users. I donāt believe this will happen with strategies like this.
Placing the best features behind a high paywall and providing only 14 days isnāt good planning.
Releasing the āpay as you goā feature was probably the smartest thing they could do to manage action-costs, so I donāt see any excuse for limiting innovation and creativity on their platform by doing this.
Logical fallacy if there ever was one Robert 
Nothing stopping anyone, except anyone who doesnāt have $250.
I get it, Glide is a business, I just believe this is a bad business move.
Correction, the vision is to create 1 billion developers which makes it even more difficult because these days with Glide itās more like you have to pay to build (anything meaningful) because all of the best and powerful features are behind a massive paywall.
What would make sense though would be some form of āplaygroundā where builders can have access to these solutions to test out and build different solutions without necessarily being able to publish it and make it accessible to other users or limit the number of users to such a solution and then when you are confident and ready to take it to the market then you can publish and present your solutions to clients. I really wish the team at Glide can think critically around this sensitive issue because some of us have really invested too much time and effort in learning the platform and finding other alternatives is just not an easy fix 
In most cases where the app is an internal tool for a business (i.e. Glideās target market), wouldnāt the business be paying for the Glide subscription rather than any individual?
I think in that context $250 a month isnāt unreasonable when you consider what Glide is enabling us to build and the financials of a company that is making money.
Iām just saying itās silly to complain about a NEW feature being available at a higher plan. Prior to / without this feature, I am still able to build awesome apps on the lower plans. I can still use Zapier or Make to do what this feature does, just with a few more steps. Iām not upset that a powerhouse feature comes at a cost.
Thanks for that Robert 
Although I donāt think Iām being silly.
As far as I can tell the criticisms are valid, and yet I donāt disagree with any of those following statements.
I think the point of the criticism is being missed if the concern is surrounding Glide getting paid for itās features.
It has more to do with how the structure of pricing restricts course towards their own goals. There are many ways they can ensure/protect revenue for this new feature without hiding it behind a $250 paywall, some obvious ways already discussed in this thread (ways they have already built too!).
I run 2 businesses that rely on Glide apps for both internal and client-facing applications.
It is precisely this sort of assumption I dread to think is being made in the boardroom. If the idea is that their 1 billion developers exist in an economy where $250 a month is an insignificant cost consideration for businesses, then I really donāt know where the conversation goes from there - there arenāt even 1 billion SMEs 
In 2022, the number of small businesses in the US reached 33.2 million, making up nearly all (99.9 percent) US businesses.
According to the US Small Business Administration, āsmall businessesā are defined as āfirms with fewer than 500 employees.ā The report shows that there are around 27 million small businesses that do not hire any employees. 5.4 million have fewer than 20 employees, and 650,000 businesses have under 500 employees.
Looks like Glide oriented only for 650000 businesses and 1 billion developers is to much for it.
May be i fully disunderstand Glide targeting
While $250 per month subscription is not a lot for an enterprise, its a lot of money for the individual who would be building that solution for that enterprise.
Itās easy to think that enterprises will build these solutions themselves, maybe in the US but not down here in Africa. Glide is not actively targeting these enterprises since they are more focused in US based enterprises.
It is people on the ground (like myself and many others) that have to think of ways how Glide can be useful in many company processes and there are many and some of the solutions are near impossible to even try and build because the cost of building those solutions is just too much.
I can understand why people in the US will find $250 as a small cost but I can assure you for some countries especially in Africa, Brazil, India, etcā¦IT IS NOT!
A 14-days trial is not enough to build a solution and acquire a client at the same time.
I have already made suggestions on how Glide can position themselves globally if they are serious about their vision.
Another point that the image suggests, is that this will replace webhook. so who has a pro plan will not call api and no webhook? it could just be a misinterpretation of mine, I hope so.
My use case, for calling the api, would be exclusively for basic actions like batch editing, adding and deleting lines in applications that I already have running. In my country, 1 dollar is equivalent to 5 Reais, that is, it would be 250 x 5. Iām not willing to pay that to have access to do something so basic, like adding more than one line simultaneously without involving external tools, Iāll come back to study Flutter Flow, a tool that has a different pricing for emerging countries. Perhaps the target audience of glide is really the American market or first world countries.
This is what has me seething. I started building and testing on the premise that I was previewing a Pro feature. Iāve spent all day re-building the apps with Webhooks, and I am very disappointed with this turn of events.
This is a very good point. If webhooks disappear I am well and truly stuffed. It would mean the immediate end of all my apps It would be good to have word on this.
I would like Glide to make this accessible at Pro. If itās a cost issue, make it 2-actions just donāt hide it from us! 
In this case fortunately, we have Make/Zapier to makeup for it.
Perhaps one thing Glide could do if they anticipate a new feature to be for business plans only is to Preview it only for those plans. Otherwise it can:
These considerations may not be well understood by business plan users, but feel real to pro plan users.
āCall API will be the successor to: Trigger Webhookā
Does this mean that the current form of integration with Make will disappear and we will no longer be able to trigger webhooks the same way we do now?
From this perspective, then, we cannot expect to see Webhooks with the ability to delete, and/or if Webhooks go away, any plan that has access to Webhooks right now should have access to Call API.
Really, I see this as a Basic Function, even if it is ānewā. It really is what Webhooks should have always been.
Yes, Iām sure there will have been an innocent reason, perhaps they wanted to have a bigger beta pool to get feedback from - but on balance and from my perspective it doesnāt feel good to be in this situation.
Bring it back 
Agreed, if one feature/function is designed to succeed another it should do so for the same users of the original feature/function, not exclude users. Perhaps something different was meant by āsuccessorā.
Quick question: When I connect Glide to a payment provider (Lemon Squeezy or Stripe) via Call API and check if the subscription status changed from āactiveā to āpausedā will it always count as a Sync/Update EVEN when the status didnāt change (before check: āactiveā, after check: still āactiveā)? Am I getting charged when I check the subscription status but the status is still the same and therefore data didnāt change?
In your documentation you say the following:
āSometimes Glide will sync your data source and find that no data has changed. In this event, the Sync is not counted (you are not charged for Syncs that donāt provide new data).ā
