APIs

GoHighLevel must become the leader in being an API first company ie anything that can be done via GUI can be accomplished via API so that soon with GHL you can do more via APIs than the GUI.

I need the ability to add a contact into any subaccount. Having my agency API key with the ability to choose which subaccount to add a contact to would be tremendously helpful and reduce the number of complex coding and additional API keys needed to accomplish this.

Currently you are using highlevel.spotlight.io for the V2 API URL. Perhaps add an extra workspace at spotlight for leadconnector or change your subdomain name.

We want to open up on this endpoint: https://services.leadconnectorhq.com/conversations/messages The new internal comments feature. It gives this currently: [401] Auth channel OAUTH is not supported.

It would be very helpful to have an API endpoint to POST internal notifications to users. Currently, the only way to accomplish this is to create an inbound webhook trigger and then internal notification action.

Need to add inventory/ product availability to the List PRODUCT api endpoint: https://highlevel.stoplight.io/docs/integrations/7f6ce42d09400-list-products Not sure why this isn't included? Only the following variables are: _id string required The unique identifier for the product. Example: 655b33a82209e60b6adb87a5 description string product description Example: This is a really awesome product variants array[object] An array of variants for the product. medias array[object] An array of medias for the product. locationId string required The unique identifier for the location. Example: 3SwdhCsvxI8Au3KsPJt6 name string required The name of the product. Example: Awesome Product productType string required The type of the product (e.g., PHYSICAL). Example: PHYSICAL availableInStore boolean Indicates whether the product is available in-store. Example: true userId string The unique identifier for the user who created the product. Example: 6YAtzfzpmHAdj0e8GkKp createdAt string<date-time> required The creation timestamp of the product. Example: 2023-11-20T10:23:36.515Z updatedAt string<date-time> required The last update timestamp of the product. Example: 2024-01-23T09:57:04.846Z statementDescriptor string The statement descriptor for the product. Example: abcde image string The URL for the product image. Example: https://storage.googleapis.com/ghl-test/3SwdhCsvxI8Au3KsPJt6/media/65af8d5df88bdb4b1022ee90.png total array[object] required list products status total number required Total number of products Example: 20

I previously raised a query regarding including product details in the one-time product payment payload. Currently, we are only receiving them for recurring products. If adding the product name and description is not feasible, please consider including the product ID. This would allow us to retrieve the necessary details and display the product name in transaction records. Thank you for your consideration.

it would be great to be able to manage custom objects via API (perhaps recalling existing objects via ID)

From my understanding the V1 API will be deprecated eventurally. Currently we and others use this to automate insertion of API keys after a new account is created. We are not able to do this with the Oauth unless we can pass in and Agency API key when authorizing which then would allow us to populate a RPC with all the sub account under that Agency which then would allow us to map in the API keys in situations where we need things to happen dynamically. Example. Creaeting a new sub acount and loading a snapshot thru the API then taking that response from the newly created account to update the custom values on that account. We can't do this without dynamically passing the API key from the new account to the update custom values endpoint dynamically. There are a few othe instances we ourselves and I know many others use so I hope they consider and alternative with the Oauth by allowing us to pass in our Agency API keys so we have the option to make an Agency connection to then dynamically pass in locations we want to make the API call to.

For our whitelabel community, we would like a way to programmatically generate a login link for a user in a location. This way, our users can seamlessly transition between our platform and our whitelabel HL