APIs

🧠 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

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.

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

Right now, there are zero public Affiliate APIs in GoHighLevel. We can’t programmatically: -Create, read, update or delete affiliates -Generate or list referral links -Track clicks, leads, appointments, opportunities or sales -Trigger workflow actions or webhooks for any affiliate event -Query commissions, payouts or overrides That gap forces everyone to build fragile workarounds (URL-param parsing, custom fields, external databases), drastically limiting what we can automate or report on. -------------------------------------------------------------------------------------------- Why It Matters: Pay-per-lead and pay-per-appointment affiliate models are common—yet GHL only supports pay-per-sale triggers today. Without native APIs, you can’t build external dashboards, CRMs or analytics that tie affiliate performance to existing GHL objects (contacts, opportunities, calendars). Workflows can’t natively tag or notify affiliates on lead or appointment events—only on completed purchases. Lack of API parity blocks multi-tier, tiered-rate or override commission structures that require programmatic control. -------------------------------------------------------------------------------------------- Affiliates: • GET /v1/affiliates — List all affiliates • POST /v1/affiliates — Create a new affiliate • GET /v1/affiliates/{id} — Retrieve affiliate details • PUT /v1/affiliates/{id} — Update affiliate metadata & commission model • DELETE /v1/affiliates/{id} — Deactivate/remove affiliate Referral Links: • POST /v1/affiliates/{id}/links — Generate a new referral link • GET /v1/affiliates/{id}/links — List all links for an affiliate • DELETE /v1/links/{linkId} — Revoke a referral link Event Tracking: • POST /v1/events/click — Record click on referral link • POST /v1/events/lead — Record a New Lead via affiliate • POST /v1/events/appointment — Record scheduled appointment via affiliate • POST /v1/events/conversion — Record opportunity or sale conversion • POST /v1/events/purchase — (alias) Record purchase Workflow Hooks: • POST /v1/webhooks — Register webhook for any Affiliate.* event • DELETE /v1/webhooks/{id} — Unsubscribe Contact Integration: • POST /v1/contacts/{contactId}/affiliate — Link an existing contact to an affiliate manually • GET /v1/contacts/{contactId}/affiliate — Retrieve affiliate attribution on a contact Commissions & Payouts: • GET /v1/affiliates/{id}/commissions — Calculate commissions (flat, %, tiered, multi-level) • POST /v1/affiliates/{id}/payouts — Trigger a payout • GET /v1/affiliates/{id}/payouts — List past payouts -------------------------------------------------------------------------------------------- Workflow & Smart List Parity Trigger Events: Affiliate.Click , Affiliate.Lead, Affiliate.Appointment, Affiliate.Conversion, Affiliate.Payout Workflow Actions: Lookup Affiliate (by linkId or contact field) Tag Contact (affiliate_{name}) Set Custom Field (Affiliate ID, First Click, Commission Due) Smart Lists & Columns: Filter by Affiliate Source, First Click Date, Campaign, Tier Show columns: Affiliate Name, Link ID, Lead Count, Appointment Count, Sales Count -------------------------------------------------------------------------------------------- Benefits: Full automation of every affiliate lifecycle stage Native lead-level triggers so you can reward “pay-per-lead” and “pay-per-appointment” models Eliminate fragile workarounds—everything lives inside GHL and respects existing permissions Rich data for external BI tools or embedded portals: real-time click, lead and sales metrics Consistent experience: uses GHL’s authentication, rate limits, workflows and reporting framework

So the affiliate manager is like a blackhole. please make some APIs

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.

We need to be able to create and schedule an email campaign using all the same settings via the UI. So the contact can be selected from a smart list or something like that. Can use a template ID, from email, subject, etc

We want to open up on this endpoint: https://services.leadconnectorhq.com/conversations/messages The new internal comments feature. It gives this currently: [401] Auth channel OAUTH is not supported.

Example: I live in Georgia and neither GHL nor TWILIO support Georgian numbers. In addition, I cannot connect to the SIP Trunk of the local provider. Because of this, I lost three very large companies, because I physically cannot use the call center function