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.

🧠 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

currently no way to pull subscription or payment information from the API. it is also not associated with the actual contact or customer in goHL . So for example, if a paypal customer uses an e-mail, we cant see the paypal email they used to pay when inputting a different one on the order form

Missing the word 'bearer' in Authorization header. -- header 'Authorization: bearer <YOUR_PRIVATE_INTEGRATION_TOKEN>' non experienced developers will miss this. After that my API calls started giving 200.

I would like to be able to merge contacts through the API. In HL, when you merge, you can select which of the records you want to use on the new merged record. The API could either send back a list of "pick a record" or select a default setting. The default settings could be hierarchical. For instance, "first, pick the record that exists if the options are [record] or [null]." Second, if two records exist, "pick the newest record." For numbers, biggest, smallest, or average. The use case here is that I have an AI messaging system set up that responds on the same channel a message came in from. If someone first uses SMS, then it creates a record. If later, they use a website chat widget or Facebook, a new record is created. If the system asks for their email/phone on the second record, but that email/phone already exists, the workflow breaks. I need a way to merge those two records.

Because of the 200k API limit/day, it would be great to be able to upload the .CSV to update/create contacts from API, so that only 1 API call would be spent.

I spent 6 hours trying to get the V2 API working. In the end I was told to enter a ticket because the thing I wanted just didn't work. I spent 10 minutes doing the same task in V1 and it just worked. I realize it's a security issue. But let us take that risk if we choose. Speed of implementation is everything.

Hi there we need complete reporting API like same that you guys are using for dashboard where we can see unassigned and total contacts report properly and will be able to proper counts its been very difficult to fetch all stats like how many leads from which source how many leads each agent got how many are open how many are lost something like this

What? Contact search endpoint should return attributionSource and lastAttributionSource Why? Currently the 'GET Contact' endpoint is the only endpoint that returns attributionSource and lastAttributionSource. Unless the GHL team want API users to hammer the https://services.leadconnectorhq.com/contacts/{contactId} endpoint with thousands of queries to to retrieve up-to-data attributionSource and lastAttributionSource, it should be made available via the search endpoint. This would allow integration for end-to-end data analytics system (e.g. funnel.io )

I need to be able to send proposals through the API.