APIs

Add API endpoints to be able to post blog articles from the API. This would help when working with external AI based tools.

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.

Allow for the creation of custom categories in notes so we can label a note and then search notes by keyword or category. Use Case: A rep has a phone meeting with a contact and puts the notes in the CRM. They use a custom category "calls" to make it easy to find client calls later. The ads manager optimizes the client's Google Ads campaigns later, and enters a summary of what they did in the notes section and ads the custom category "ads management". A rep has another call with the client to discuss their own internal processes and upcoming changes that will affect ads. The rep marks the notes as "calls" and "ads management" so that the ads manager can find the details and make appropriate changes on their next optimization run. Categories, filter, and search could be used for billing, follow-up notes, internal communication regarding clients and leads, and significantly improve human-centric workflows inside of a business or agency. By allowing search (through the API and App), notes could be the go-to repository of client information that doesn't fit into customFields.

As a GHL user and developer, I would greatly benefit from the ability to inject custom CSS and JavaScript at the agency level through the API. This feature would allow agencies to streamline their branding and user experience by programmatically applying custom styles and scripts across all sub-accounts

It would be great to be able to hide the launchpad once we are done with it. We've been asked this several times, to be able to hide that. Once we are done with the items that we want to mark off it makes sense to be able to mark it complete and hide it so that it's not a distraction.

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.

Using data base like notion would great to develop apps using websites

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.

Currently there is no way to get the collections for a Product, the product only returns the collection ids.

Proposal: We propose an enhancement to GoHighLevel's API to include a filter for opportunities by date (and other custom fields, but specifically date for this request), similar to the existing calendar view filtering. This feature will significantly improve user flexibility when managing and tracking sales opportunities, aligning with the powerful date-filtering capabilities already available in appointments. Detail: Currently, the GoHighLevel API allows users to filter appointments by date, using parameters such as startDate, endDate, and calendarId in the endpoint: https://rest.gohighlevel.com/v1/appointments/?startDate=${startDateValue}&endDate=${endDateValue}&calendarId=${calendarId}&includeAll=true This structure could be similarly applied to opportunities, allowing users to filter opportunities by specific date ranges. The proposed endpoint could look like: https://rest.gohighlevel.com/v1/opportunities/?startDate=${startDateValue}&endDate=${endDateValue}&pipelineId=${pipelineId}&includeAll=true Parameters: startDate: Filters opportunities that were created or last updated after this date. endDate: Filters opportunities that were created or last updated before this date. pipelineId: Filters opportunities by specific pipelines, allowing more focused data retrieval. includeAll: Option to include opportunities from all pipelines, regardless of pipelineId. Why It’s Important: Data Accuracy: Filtering opportunities by date allows users to focus on relevant data, improving reporting and forecasting accuracy. Efficiency: Sales teams can quickly view opportunities from a specific period, streamlining workflow and prioritizing the most recent or time-sensitive opportunities. Consistency: Aligning this functionality with the appointment date filtering creates a uniform API experience, reducing the learning curve for developers using GoHighLevel. Enhanced Reporting: Businesses can generate time-specific sales reports and analyses, enabling better decision-making and performance reviews. Implementing date filters for opportunities will provide users with more control and make the API more versatile, aligning opportunities management with the same flexibility offered in appointments.