Do NOT deprecate the V1 Api. Ever.
S
Seth Turin
I spent 6 hours trying to get the V2 API working. In the end I was told to enter a ticket because the thing I wanted just didn't work.
I spent 10 minutes doing the same task in V1 and it just worked.
I realize it's a security issue. But let us take that risk if we choose. Speed of implementation is everything.
Log In
S
Sunny Lim
You can do a custom integration in Zapier or you code a micro. The latter is more challenging and, like one the earlier comment said you will need a place to store the response for you to refresh the token when it expires.
W
Will Bowman
I dont need a marketplace app! I need a really simple one-off integration for one client, not something others are going to use, not something marketable, dont want to wait 10 days for approval and dont want to deal with refresh tokens.
C
Chris Thompson
Will Bowman 100% agree. If I just want to use the API for internal stuff, I do not want to go through the hassle of publishing an app in the marketplace, even if I can make it private. It seems like a lot of friction.
E
Eric Briel
We've implemented API2 except for one issue: PUT location is requiring an agency level token. API1 always allowed this at the location level. Are they going to relax this restriction before sun-setting API1?
I
Ishan Bansal
Or at least make permanent access token available.
S
Sam Kuo
Totally agree!!!
I am deeply frustrated with updating the refresh token every time an access token is refreshed in the V2 authentication system.
This approach is highly inefficient and deviates from the standard practice established by platforms like Salesforce, Zoho, and Zoom SDK, which use a fixed refresh token system.
I have to put enormous effort to implement additional locking mechanisms to manage concurrent to token refreshing which is unnecessarily complex and burdensome.
This is particularly problematic for clients who utilize serverless architectures, as there is no feasible method to store and safely update the V2 refresh tokens.
I hope it can keep the more straightforward V1 or adopt a fixed refresh token mechanism for V2.
This decision has significantly impacted our operational efficiency and client satisfaction.
D
Djibril Mara
I have the whole architecture done for API V2 oauth for Location & Company with access_token & refresh_token.
contact me if you need this, we can work it out: tech@salespanthera.io
J
Jacob Radcliffe
You can diy this: www.ghlapiv2.com
A
Ali Khansari
I agree 100%. I spent hours to figure out how I can manage all locations without having authorizing over and over. It felt devastating that the refresh token, access token were expiring within a short time period of time. And I'm not sure if newer locations would even show up under the agency, or I have to re-authorize every time.
GHL's custom values and website lack a lot of flexibility and without using API, we're stuck with Zapier, which is not ideal to have our data exposed everywhere and pay for each zap/task.
I do like that V2 has more features and abilities but at the same time, it's more complicated to do simple things.
C
Chris Stone
Security flaws = liabilities for businesses. Liabilities can = lawsuits.
I'm sure you know why there's a new version of the API that includes these security measures that the old version doesn't...