HighLevel Updates
LeadConnector WordPress Plugin V4: A Security Rebuild
Latest
HighLevel relisted the LeadConnector WordPress plugin on WordPress.org as v4.0.0 - a top-to-bottom security, compliance, and performance overhaul.
HighLevel Update
HighLevel Public API v3 Is Officially Released
HighLevel has officially released v3 of its Public APIs, announced by co-founder Shaun Clark. v3 builds on the existing API versioning foundation with a more consistent endpoint architecture, better performance, and advanced capabilities for complex workflows, while your existing integrations keep running exactly as they do today. Below is the full breakdown: what changed, every API resource you can call, how authentication works, and how to migrate on your own timeline.
What's new in HighLevel API v3?
- v3 API endpoints: a new generation of endpoints designed for performance, long-term scalability, and richer data functionality.
- Unified structure: a more predictable, standardized endpoint and payload schema that simplifies building advanced, data-heavy workflows.
- Dedicated v3 documentation: full schemas, reference guides, and a v3-specific changelog are live.
- Seamless version switcher: select v3 directly from the version dropdown in the developer portal to view the updated documentation.
What APIs are available in HighLevel?
The HighLevel Public API covers the whole platform, grouped into more than 30 resource categories. Each one is a set of REST endpoints you call over HTTPS. Here is the full catalog of what you can read and write, grouped by area, along with the base path for each resource, so you know exactly what is reachable before you build.
CRM and contact data
| API | Endpoint (base path) | What it does |
|---|---|---|
| Contacts | /contacts/ | Create, read, update, delete, and search contacts; manage tags, notes, tasks, appointments, followers, and custom field values. |
| Companies | /companies/ | Manage company and organization records and link them to their associated contacts. |
| Businesses | /businesses/ | Read and manage business records inside a sub-account. |
| Objects (Custom Objects) | /objects/ | Define and manage custom object records that go beyond the built-in contact model. |
| Associations | /associations/ | Create and query relationships that link records across objects (contacts, custom objects, and more). |
| Custom Fields V2 | /custom-fields/ | Programmatically create and manage custom fields and folders used across the CRM. |
Conversations and messaging
| API | Endpoint (base path) | What it does |
|---|---|---|
| Conversations | /conversations/ | Send and read SMS, email, and other channel messages; access the unified inbox and message threads. |
| Emails | /emails/ | Manage email templates and builder assets used in campaigns and workflows. |
| LC Email | /email-isv/ | LeadConnector email services, including email verification and sending controls. |
| Campaigns | /campaigns/ | Access and manage marketing campaign data. |
Scheduling, sales, and pipelines
| API | Endpoint (base path) | What it does |
|---|---|---|
| Calendars | /calendars/ | Read availability, create, reschedule, and cancel appointments, and manage calendars, groups, and resources. |
| Opportunities | /opportunities/ | Manage pipeline deals: create opportunities, move stages, update values, and pull pipeline data for reporting. |
Commerce and billing
| API | Endpoint (base path) | What it does |
|---|---|---|
| Payments | /payments/ | Orders, transactions, subscriptions, coupons, and payment-integration data. |
| Products | /products/ | Manage the product catalog, prices, and inventory. |
| Invoices | /invoices/ | Invoices, estimates, schedules, templates, and Text2Pay flows. |
| Store | /store/ | Ecommerce store configuration, shipping, and fulfillment. |
Marketing and content
| API | Endpoint (base path) | What it does |
|---|---|---|
| Funnels | /funnels/ | List funnels and their pages and steps. |
| Forms | /forms/ | Read form definitions and retrieve submissions. |
| Surveys | /surveys/ | Read survey definitions and submissions. |
| Social Planner | /social-media-posting/ | Schedule, retry, and manage social posts across connected accounts. |
| Blogs | /blogs/ | Manage blog posts, authors, categories, and sites. |
| Trigger Links | /links/ | Create and manage trackable trigger links. |
| Media Library | /medias/ | Upload and manage files in the media library. |
| Courses | /courses/ | Import and manage course and membership content. |
Automation, agency, and platform
| API | Endpoint (base path) | What it does |
|---|---|---|
| Workflows | /workflows/ | List workflows and add or remove contacts from them. |
| Sub-Accounts (Locations) | /locations/ | Create and manage sub-accounts, plus their custom fields, values, tags, tasks, and templates. |
| Users | /users/ | Manage users, roles, and permissions. |
| SaaS | /saas-api/ | SaaS-mode configuration: plans, rebilling, and sub-account provisioning. |
| Snapshots | /snapshots/ | List and manage account snapshots for cloning setups. |
| Custom Menus | /custom-menus/ | Manage custom menu links in the sub-account navigation. |
| Marketplace | /marketplace/ and /oauth/ | App and marketplace endpoints for installed apps and OAuth token exchange. |
| Country List | Reference lookup | Supported-country and related reference data used to validate address and locale fields. |
How do you authenticate with the HighLevel API?
The Public API is served from services.leadconnectorhq.com and expects a Version header on every request. There are two ways to authenticate, and which one you pick depends on whether you are building a distributed app or a single-account integration.
- OAuth 2.0 (marketplace apps): the standard for apps distributed through the HighLevel Marketplace across many sub-accounts. You register an app, request scopes, and exchange an authorization code for access and refresh tokens.
- Private Integration Token (PIT): a scoped token for a single agency or sub-account. Simpler for internal tools and dashboards; send it as a Bearer token with no OAuth round-trip.
- Version header: pass the API version (for example Version: 2021-07-28 on date-based endpoints) so HighLevel serves the schema you built against.
Are there rate limits on the HighLevel API?
Yes. HighLevel enforces both a burst limit and a daily limit per app and resource, so build in retry-with-backoff and cache reads you do not need in real time. Some endpoints also have their own pagination quirks (for example, paginate payment transactions by offset, not skip), so verify that returned record IDs actually change between pages instead of assuming a call succeeded. Always check the current limits in the developer portal before shipping high-volume jobs.
Is v3 backward compatible?
Yes. HighLevel emphasizes zero disruption to live apps: your existing date-based API configurations remain fully functional, completely accessible, and fully documented. Nothing changes for current implementations, so your team can explore and adopt v3 on its own timeline.
How to use HighLevel API v3
- Open the Public API Documentation in the developer portal.
- Locate the Version Switcher dropdown at the top of the interface.
- Select v3 to view the new endpoints, schemas, and technical references.
- Choose your auth method (OAuth 2.0 for a marketplace app, or a Private Integration Token for a single account).
- Build, test against a sandbox sub-account, and deploy.
What this means going forward
HighLevel says all new feature endpoints and non-breaking API enhancements will be added exclusively to the v3 framework as it expands core coverage. If you build or maintain GHL integrations, plan new work against v3, while existing date-based apps need no immediate change. Need a custom HighLevel integration or automation built against v3? That is exactly what we do at BrewedOps.
Frequently asked questions
What APIs does HighLevel offer?
The HighLevel Public API covers more than 30 resource groups across the platform, including Contacts, Companies, Businesses, Custom Objects, Associations, Custom Fields, Conversations, Emails, LC Email, Campaigns, Calendars, Opportunities, Payments, Products, Invoices, Store, Funnels, Forms, Surveys, Social Planner, Blogs, Trigger Links, Media Library, Courses, Workflows, Sub-Accounts, Users, SaaS, Snapshots, Custom Menus, and Marketplace. Each is a set of REST endpoints you call over HTTPS.
Does HighLevel API v3 break existing integrations?
No. HighLevel states there is zero disruption to live apps. Existing date-based API configurations stay fully functional, accessible, and documented, so current integrations keep working and you can move to v3 on your own schedule.
How do I authenticate with the HighLevel API?
Two ways. Use OAuth 2.0 for marketplace apps that run across many sub-accounts, or a Private Integration Token (PIT) for a single agency or sub-account. Both hit services.leadconnectorhq.com and require a Version header. OAuth issues access and refresh tokens; a PIT is sent as a Bearer token with no OAuth round-trip.
How do I switch to HighLevel API v3?
Open the Public API Documentation, find the Version Switcher dropdown at the top of the interface, and select v3. That reveals the new v3 endpoints, schemas, and technical reference guides for building and testing.
Does the HighLevel API have rate limits?
Yes. HighLevel enforces a burst limit and a daily limit per app and resource, so build retry-with-backoff into high-volume jobs and cache reads you do not need in real time. Confirm the current limits in the developer portal before shipping, and watch endpoint-specific pagination behavior.
Where will new HighLevel endpoints be added?
Going forward, all new feature endpoints and non-breaking API enhancements will be added exclusively to the v3 framework as HighLevel expands its core coverage. The earlier date-based versions remain supported for existing apps.
Is there documentation for API v3?
Yes. HighLevel shipped dedicated v3 documentation with full schemas, reference guides, and a v3-specific changelog, accessible by selecting v3 in the developer portal version switcher.