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.

Just noticing that the Search Contacts endpoint only looks at the main email and phone number on a contact. If you try searching by a secondary email or phone, it won’t return anything. It would also be great if searches were case-insensitive and not limited to exact matches. For example, searching for john@gmail.com or John@Gmail.com should return the same result. This should apply across all searchable fields, not just email. Right now, the phone search is also limited — it only works if the number is in E.164 format (for example, +13145557878). The older endpoint https://services.leadconnectorhq.com/contacts/ used to match all of these formats: 📱 +13145557878 📞 13145557878 ☎️ 3145557878 📱 (314) 555-8888 📞 314-555-8888 But the new one https://services.leadconnectorhq.com/contacts/search only works if it’s exactly like this: 📱 +13145557878 Would be awesome if the new search: 🔍 Included secondary emails and phone numbers 📱 Accepted any standard phone format 🧩 Supported a case-insensitive operator for all search fields

Create Read Write Add Delete List/ Fetch Execute Archive Search/Query

🧠 Summary Please expand the public HighLevel API to include full CRUD access for Courses (Products/Memberships) as well as related content like Categories , Lessons , and Enrollments . This will empower users to automate course creation, sync with external platforms, and enhance learning experiences with real-time data access. 📌 Requested API Endpoints ✅ Courses / Products GET /products – List all courses POST /products – Create a new course GET /products/{id} – Retrieve a single course PUT /products/{id} – Update a course DELETE /products/{id} – Delete a course ✅ Categories (Modules) GET /categories – List categories/modules POST /categories – Create a category PUT /categories/{id} – Update a category DELETE /categories/{id} – Delete a category ✅ Lessons GET /lessons – List lessons POST /lessons – Create a lesson PUT /lessons/{id} – Update a lesson DELETE /lessons/{id} – Delete a lesson ✅ Enrollments GET /enrollments – List enrollments POST /enrollments – Enroll a user in a course DELETE /enrollments/{id} – Unenroll a user ✅ Progress Tracking (Read-only) GET /progress?userId={id}&courseId={id} – Retrieve a user’s progress ✅ Certificates GET /certificates – List course certificates POST /certificates – Generate/download a user certificate ✅ Webhooks (Triggers) Course created / updated Lesson published / completed Enrollment created / deleted Course completed 🌐 Reference Examples Teachable API Thinkific API Current HighLevel Memberships API 🙌 Why This Matters Allow external dashboards or apps to display or manage course data Enable custom onboarding and course enrollment automation Improve reporting , progress tracking, and compliance (e.g., certifications) Unlock white-labeled LMS features for agencies and SaaS owners Support real-time workflows through webhook triggers

💡 Description / Use Case When building external or custom apps using the HighLevel API, developers currently have to manually maintain large, static lists of: permissions scopes scopesAssignedToOnly Every time HighLevel introduces a new feature (e.g., Voice AI, Launchpad, Certificates, Blogging, etc.), those lists must be copied, updated, and redeployed inside our apps just to stay compatible. This creates a massive maintenance overhead, since there are hundreds of items — and any mismatch causes API errors such as “Each value in scopes must be a valid enum value.” By introducing GET endpoints like: GET /permissions/schema GET /scopes GET /scopes/assigned-only developers could dynamically fetch the most current and valid data directly from HighLevel. ✅ Benefits Keeps all external and internal apps automatically up to date Eliminates repetitive copying/pasting of hundreds of static values Prevents validation errors from outdated scopes Greatly reduces ongoing maintenance for partners and agencies building integrations Encourages faster adoption of new modules and features

Currently the Get Contact/Get Opportunity API only returns the filled custom fields, not all of the custom fields. It would be great to get all custom fields returned in those calls. Also, would be great to be able to Get Custom Fields by Folder Name (ex. Get all Custom Fields for Opportunities)

When fetching the templates, it's great that they are there and we can see what templates there are, but they're useless if we can't even use the HTML or use them themselves to send emails... PLEASE PLEASE create an HTML endpoint!

We should be able to control a brand from an api endpoint, uploading and syncing with brand colors, logo, voice etc