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.

OpenClaw AI enables fully autonomous AI employees that operate directly through GoHighLevel’s API, allowing businesses to automate real work, not just simple triggers. Once properly integrated with GHL API keys, OpenClaw can independently send SMS, WhatsApp messages, and emails, manage conversations, and execute tasks based on objectives defined by the account owner. Unlike traditional automation tools, OpenClaw is task driven rather than rule bound. Owners assign goals, and the AI determines the required actions, sequences, and follow ups on its own. This allows it to function as a true digital employee that can handle lead engagement, follow up, scheduling, and internal operations without constant human input. OpenClaw is designed to go further by autonomously building workflows, pipelines, websites, and system structures inside GHL. At present, these capabilities are limited by the permissions and scope exposed by the GoHighLevel API. If deeper or expanded access were made possible, OpenClaw could dynamically design, deploy, and optimize entire CRM systems end to end, representing a major leap in platform capability. Despite its power, OpenClaw is built with containment and governance in mind. All actions are constrained by defined permissions, scopes, and owner approved objectives, ensuring autonomy remains controlled, auditable, and safe. With proper access boundaries, OpenClaw becomes not just an automation layer, but a scalable workforce multiplier for agencies and businesses operating inside GoHighLevel.

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

I want the ability to create a funnel and associated workflows through the API. Is this something that can be done and if so, how soon can it be included in an update?

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.

GHL shipped gift cards. That's great. But right now there's no API and no workflow actions to actually interact with them programmatically — which means the only thing you can do with gift cards is sell them manually or let customers buy them from a link. That's the whole list. There's no way to issue a gift card through a workflow. No way to issue one through an external system via API. No way to check a contact's gift card balance. No way to mark a card redeemed. No way to retrieve a list of gift cards tied to a contact record. The gift card feature was shipped as a standalone sales tool and never connected to the rest of the platform. Here's what that means in practice: A business wants to automatically send a $25 gift card when a customer hits a VIP tag after their 5th appointment. Can't do it — no workflow action exists. A business wants to issue a referral reward gift card when a referred customer pays in full for a service. Can't do it — nothing triggers gift card creation from a workflow or an external build. An agency wants to build a loyalty points system where points convert to gift card credit after a threshold is hit. Can't do it — no API endpoint to create, query, or update gift cards. A business running an external integration (Zapier, Make, a custom Cloudflare Worker, a third-party booking tool) wants to trigger a gift card when a condition is met inside their stack. Can't do it — no API exists. A business wants to pull a report showing which customers have unredeemed gift card balances and send a "don't forget your credit" follow-up campaign. Can't do it — no way to query gift card data from workflow filters or external tools. What's needed is a gift card API — a set of endpoints that let developers and the workflow engine interact with gift cards the same way they can interact with contacts, appointments, and invoices: Issue a gift card to a contact (amount, code, expiration) Retrieve gift cards by contact ID Check balance on a specific gift card Mark a gift card as redeemed or adjust its balance List all gift cards in an account with filter options (issued, redeemed, expired, balance range) On the workflow side, the same operations should be available as workflow actions: "Issue Gift Card" action (amount, recipient contact, message) "Check Gift Card Balance" action (for conditional branching) The infrastructure is already built. The gift card system exists. This is just exposing it so the rest of GHL — and the developers building on GHL — can actually use it. The business cases that unlock immediately once this API exists: Referral programs: Issue a gift card automatically when a referred customer completes and pays for a service. The referrer gets rewarded without the business doing anything manually, and the reward stays inside the business instead of going out as cash. Loyalty programs: Issue gift cards automatically at milestone appointments (5th visit, 1 year as a customer, $1,000 in lifetime spend). Fully automated, zero manual work. Win-back campaigns: Issue a small gift card to a contact who hasn't booked in 90 days. Trigger from a workflow, send via SMS or email, track whether they came back and used it. Apology/recovery workflows: When a complaint tag is added to a contact, auto-issue a gift card as a goodwill gesture while the team follows up. Reward campaigns: Run a promotion where any customer who books a service during a specific window automatically receives a gift card for their next visit — all triggered via workflow with zero manual issuance. The gift card system is already built. Connect it to the API and the workflow engine and it becomes one of the most powerful retention and referral tools on the platform. Right now it's a dead end. It should be a lever.

🧠 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

What it says on the tin. Currently there's no way to deploy or update webpages or funnels via the API

My client needs to be able to create pipelines and pipeline stages from the API.