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.

GHL provides pre-built Email Marketing Results such as "Emails Sent", "Emails Delivered", "Emails Bounced", "Emails Opened", "Emails Clicked", "Emails Unsubscribed", "Emails Spam". The goal is to put Real Time Update of Email Marketing Results to Google Sheet. There are "Email Event" triggers in GHL automation, but they are only "Opened", "Clicked", "Spam", "Unsubscribed", and "Bounced". There is no API endpoint to get "Sent" and "Delivered" triggers. To calculate "Delivery Rates", "Open Rates", etc to engage Email Marketing Performance, we just need to grab "Emails Sent" and "Emails Delivered".

Would be greate to select a smartlist to be able to schedule and send bulk SMS and Email's thru the API. Currently using MailChimp for this still in two steps Create Campaing Send the Campaign Could works same for SMS to select a list etc...

Do we have ability to add new service and push appointment via API of that service ?

At the moment we can manually add in appointment notes. However, the ability to push appt. additional data via API into the notes field would be fantastic.

If we are to adopt the business object then we need to have access to custom fields from the API

Description: I've built a workflow triggered by an inbound webhook that receives events from our evergreen webinar platform. The webhook sends a request to the GHL automation each time a contact performs different actions such as: Registering for the webinar Attending the webinar Clicking the call-to-action button Each event sends a unique payload with different event fields (e.g., "register", "attend", "viewCta"), but all events relate to the same contact. Issue #1: Workflow Incorrectly Flagged as Loop The workflow is being locked in Draft status with this message: "This Workflow has been locked in Draft status because it is causing a loop. To activate this Workflow, please contact Support." GHL appears to be interpreting this as a loop because the same contact is entering the automation multiple times. However, these are distinct events/actions, not a loop. Each webhook trigger represents a different stage in the customer journey and should be processed as separate workflow entries. Issue #2: No Notification When Workflow Auto-Locked (CRITICAL) The workflow was automatically set to draft on September 17, 2025, but I wasn't notified. I only discovered this on October 7, 2025 - nearly 3 weeks later. This is a business-critical workflow that generates substantial income for us. The lack of notification resulted in significant lost revenue and missed customer touchpoints during this period. Requests: Fix the loop detection: Allow the same contact to trigger a webhook-based workflow multiple times when the events represent different actions, or provide a setting to differentiate between actual loops and legitimate multiple entries with different event data. Add notifications: Implement immediate email/in-app notifications when a workflow is automatically deactivated or set to draft for ANY reason. This is critical for business continuity.

Introduce hidden, fillable custom fields within contracts that can be automatically populated with dynamic merge tags through workflows. These hidden fields would act as unique identifiers, making it easier to track and search contracts via the API. Example Use Case: An opportunity moves to a new stage, triggering a workflow that sends a contract. The workflow inserts a dynamic merge tag (such as the opportunity ID) into a hidden custom field in the contract. When the contract is signed, another workflow captures the contact ID. Using the hidden custom field, we can look up the contract and directly tie it back to the correct opportunity. This enhancement would provide a seamless way to link contracts to specific opportunities without relying on manual tracking or external mapping. Current Workaround: Right now, we’re forced to use a non-public endpoint to download the full JSON of the contract, then run regex to extract the ID we need in order to upload the contract to the right opportunity. This is fragile and risky since that internal endpoint may be shut down at any time. Adding official support for hidden contract fields would eliminate the need for this workaround and create a reliable, long-term solution.

I'd like to make custom changes to things within the software utilizing css but finding the classes constantly can be a pain. If there was a directory built up over time, that would be amazing

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.