APIs

In the case of WhatsApp, when a message is sent, the OutboundMessage webhook is triggered with the information of that message. When the message information arrives through the webhook to the target application, the status is usually sent or delivered. If we want to track that message to know whether it has been read, we need to periodically run one of the following API calls: - Export messages by location ID ( https://marketplace.gohighlevel.com/docs/ghl/conversations/export-messages-by-location ) - Get message by message id ( https://marketplace.gohighlevel.com/docs/ghl/conversations/get-message ) In projects with a high volume of messages, making periodic calls to those endpoints just to check if the status has changed is costly in both time and resources. To optimize this process, it would be great to have a MessageStatusUpdate webhook that is triggered every time the status changes. That way, external tools could easily know if a message has been read, whether to show it in a BI dashboard or to trigger some action. This new webhook could also work for other types of messages, like Email, since it could fire when an email changes status to opened, clicked, bounced, etc.

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

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.

Write now the custom providers are for sms, email and phone only. It would be great if you could replicate the sms custom provider but have the type as messaging and detach from the phone number. Use cases: Open up custom providers to internal chat systems such as slack, mattermost, rocketchat and other services. I am currently doing this already but it's over top of the sms custom provider. Seems like 99% of the functionality is already there.

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.

Implement in webhooks that when a contact sends an audio or image, it can be shared through webhook or API that file endpoint

The Problem EVERY GHL User Faces Daily We love exporting opportunity data to Google Sheets when stages change or custom fields update - it's one of GHL's most powerful features! But there's a MASSIVE gap that's driving everyone crazy: We can see WHO made changes in the Audit Log, but we CAN'T export that "Done By" information anywhere! Even worse: GHL deletes all audit logs after just 60 days. For agencies, enterprises, and compliance-focused businesses, this is a deal-breaker. What We Need (Simple Fix) Add These Variables to Workflow Exports: {{audit.done_by_user_name}} - Who made the change {{audit.done_by_user_id}} - User ID for tracking {{audit.timestamp}} - Exact time of change {{audit.previous_value}} - What it was before {{ audit.new _value}} - What it is now Plus Basic API Access: GET /opportunities/{id}/audit-logs Result: Export complete audit trails to our own databases/sheets - keeping records FOREVER, not just 60 days! Why This Will Get MASSIVE Votes 🎯 Every Agency Owner Needs This: "Which sales rep actually closes deals fastest?" "Who's messing up our data quality?" "Show clients exactly who worked on their account and when" 🎯 Every Business Owner Needs This: Team Accountability: Stop guessing who made changes Performance Tracking: Measure real productivity, not just activity Quality Control: Identify training needs and process improvements 🎯 Every Enterprise Client Demands This: Compliance Requirements: HIPAA, GDPR, SOC 2 all require "who did what" tracking Legal Protection: Prove who authorized changes months or years later Security Audits: Track unauthorized access and suspicious activity GHL has the most powerful automation platform, but we're missing basic accountability tracking that every professional business expects. This isn't rocket science - the data already exists in audit logs, we just need access to it! Thank you... ✅ Affects EVERYONE - Every user needs accountability tracking ✅ Simple Implementation - Data exists, just needs to be exposed ✅ Immediate ROI - Better reporting = higher client retention ✅ Enterprise Requirement - Unlocks bigger deals and contracts ✅ Universal Problem - Agencies, businesses, enterprises all need this

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 when creating an inovice there is no way to get the _id paramater of the tax that was created through the UI. The only way to get this id is to manually creating an invoice with that tax tied to it then doing a Get reqeust to get that invoice which then shows the _Id of the tax. Hoping to get that endoint along with associated name, description etc so can be use as an RPC. Also maybe the ability just to include the _id of the tax which then the system would know all the rest of the information it needs as it has all decription, taxId , rate etc.. already stored.

Ability to track down all the changes of the data including who did it and the request payload or at least the IP address of the request. When doing updates through API, the source third_party is not enough we should be able to at least use custom User-Agent to further identify the source. This additional field should be part of the webhooks as well IP Address Request payload and headers (optional) We should be able to use traceId to track down specific log instead of searching by calendar event for example and loop though all the logs for the specific event.