Changelog

Follow up on the latest improvements and updates.

RSS

We’ve implemented a significant enhancement to how refresh tokens are managed, particularly for concurrent API calls in distributed environments. This improvement ensures greater stability and efficiency when refreshing access tokens.
What’s Improved?
Concurrent Refresh Token Call Handling:
To optimize performance and prevent race conditions in distributed systems, we’ve refined our refresh token mechanism. Now, if multiple concurrent calls are made within a 30-second window using the exact same client_id and client_secret and refresh_token combination, the system will return the same refresh token for all these calls.
Why was this enhancement necessary?
This enhancement is targeted to help large-scale developers who have distributed systems:
  • Improve Stability
    : Reduces the likelihood of invalidating refresh tokens prematurely due to concurrent requests from different services or instances.
  • Simplify Distributed Architecture
    : Makes it easier to manage token refreshing in environments where multiple services might simultaneously attempt to refresh tokens.
Note
: No changes are required on your end to benefit from this enhancement. It is automatically applied to all relevant API interactions.
Overview:
We’ve added API support for the User Management permission (view & manage users and view users), which governs the ability to view, create, and edit users. Earlier these permissions being security sensitive and critical were restricted from update via users API.
What’s New:
We have added another check in the Enhanced Account Security to allow agencies flexibility in terms of whether they want to enable or disable above scope in API.
How to Enable User Management permissions via API
Navigate to:
Settings > Company > Advanced Settings
Disable the Enhanced Security option to allow API-based user management.
Why It Matters:
  • Operational Efficiency → Reduce manual overhead for high-volume agencies
Preview:
Screenshot 2025-06-24 at 2
Screenshot 2025-06-24 at 1
The Marketplace team is proud to announce Simplified App Distribution, a series of fundamental changes to the app development, discovery, and installation journey designed to grow the adoption of Marketplace apps.
What's new?
Simple and Clear Distribution Settings for app-developers
  • “Who is the target user?” → Sub-account (recommended) or Agency
  • If Sub-account: “Who can install?” → “Agency & Sub-account” or “Agency only”
image
User-centric design aimed at improving the discovery of Marketplace apps for Agency Owners & Admins
  • Unified Catalogue
    : Instead of splitting apps by “Where” (Agency vs. Sub-account marketplace), apps are now shown based on “Who” is browsing.
  • Agency users (in either marketplace) see all apps in one place. This ensures that they can discover new apps on the Marketplace, while limiting sub-accounts' access to approved apps only.
  • Sub-account users see only apps that the agency owner/admins have approved them to see.
image
Agency Trust
  • Agency users can switch to preview the sub-account view of any app’s listing/details.
  • Ensures clarity around what sub-accounts will see, and hence inspires agency trust.
image
Expand the market for developers’ apps
  • Developers can now build apps that are discoverable and installable by 100% of GHL users.
  • Sub-account admins can discover and install apps to their sub-accounts.
  • Meanwhile, the same app can also be discovered and bulk-installed to multiple sub-accounts by Agency owners and admins.
  • Backwards Compatibility
    : We've ensured that existing token exchange mechanisms are maintained, so no config changes are required for live apps. However, developers can expand their market by implementing the dual token mechanism and enabling the appropriate settings in their app.
Why is this important?
The changes enable
growth for Marketplace apps
through:
  1. Wider reach of Marketplace apps, ensuring developers' success on the HighLevel Marketplace.
  2. A unified app discovery experience for agency owners, ensuring they can always view all the apps.
  3. Improved agency trust in the Marketplace by allowing them to preview the sub-account's view of the marketplace and the apps, giving them confidence that they are in control of their offerings to their sub-accounts.
We're thrilled to announce the release of Contact Update bulk Tags Public API! This new feature allows you to easily create/remove tags using public APIs.
What's New?
Managing tags for contacts notes just got easier! With these new public APIs, you can now:
  • Create Tags: Add new tags to up to 500 contacts in bulk. Maximum tags limit is 50
  • Remove Tags: Remove all tags to contacts in bulk.

new

Automations

App Marketplace

Conversations

API

Agency Billing

Marketplace | Usage-based pricing

What's new?
App developers can now set a per-usage price on their Marketplace apps. An app can have a usage-based price for three modules:
  1. A per-execution price for Marketplace Actions and Triggers.
  2. A per-message price for Conversation Providers. They can set a custom price for inbound and outbound messages.
  3. A custom per-usage price for events that are app-specific and billed using the Marketplace billing APIs. For example, an app that offers AI Voice calling agents can bill a per-minute price using the Marketplace billing APIs.
As part of this release, we're also rolling out an experiment. For a handful of developers, the premium action/trigger fees will be waived on all their actions/triggers that are billing via our platform. The objective is to give them full-control over their service/feature's pricing, reduce and simplify the overall pricing to customers, and thereby grow adoption of these marketplace actions/triggers. Read more about the experiment here.
Why is this feature important?
This model significantly improves developers' earning potential on the Marketplace.
Release Plan:
This feature will be enabled only on select and vetted developers' accounts in the first phase.
Help Articles:
For Marketplace app developers:
For customers
:
What's next?
  1. Ability for agencies to mark up and rebill the developers' usage-based price to their clients.
  2. Ability for agencies to set daily limits on usage.
Preview Images:
Usage-based pricing details on the app details page - Pricing section
image
Per-execution charges in the Workflow builder - Discover tab
.
image
Developer portal
:
image
What's new?
App developers can now configure custom webhook endpoints for specific events based on the event's priority.
Why is this important?
This enhancement enables developers to prioritise real-time webhook events and send them to high-priority queues while letting other events, such as those meant for reporting, go to default/lower-priority queues.
What's next?
In Q3, we'll add the capability to configure custom webhook endpoints via API for a specific agency/sub-account level. This will allow apps with high adoption to optimise events at a customer level.
Preview Images
image
The Marketplace team has released an enhancement to the app review process to improve the general quality of apps and API access governance.
What's new?
For all new public apps launched on the Marketplace from now on, developers must furnish the following details:
  1. A Loom demonstrating all the features of the app end-to-end
  2. A Loom explaining why they need the scopes they've requested, along with demo of the relevant features of the app that need those scopes
  3. If the app integrates with a third party app, we seek test account credentials that will allow us to test the features/integrations ourselves
  4. Any other details/comments that would help the Marketplace team review the app quickly and effectively.
Why is this important?
  1. This enhancement aims to improve the baseline quality standards of all the apps on the Marketplace, ensuring that the apps work and they're only seeking API permissions that they truly require.
  2. We've restricted this new process to the first-time review submission only so that we don't add friction to active developers updating their apps frequently.
Preview Images
image
Context:
  • A sizable number of marketplace app installs are done using the Marketplace OAuth link(example). These links are embedded in third-party products' integrations page that allows integration with HighLevel.
  • This is similar to the Google OAuth link, where Google informs the user that an external site is about to access their account data and seeks your confirmation to proceed
  • When users arrived on this site, until today, they weren't made aware of which permissions the app was getting access to from their accounts.
What's new?
  • We have created a new OAuth page where we give users a heads-up about the app they're about to install and inform them about the permissions the app will have access to.
  • If a private app attempts to access sensitive permissions, such as user.write, we explicitly warn the user.
  • This feature is also available on the Marketplace's grey-labeled OAuth page(example)
Why is this important?
This feature provides sufficient details to users, allowing them to make informed decisions about the API access they're granting to third-party apps and thereby securing their accounts from unauthorised access.
Preview Images
image
image
Developers can access the agencies' White-label when sub-accounts install an app.
What's new?
The
AppInstall
webhook event now includes four new fields:
  • Parent agency's name
  • Is the parent agency white-labeled?
If the parent agency is white-labeled
  • Parent agency's domain
  • Parent agency's logo
Why is this important?
This enhancement enables developers to build a white-labelled experience for the sub-accounts within their apps, thereby improving the apps' adoption among the white-labelled agencies.
What's next?
We'll soon add the above details to the
GET /locations/{locationId}
API so developers can get the parent agency's white-labelled details on demand.
Agency-level APIs and agency-distributed marketplace apps are now available on the Starter plan ($97 plan).
What's new?
  • Agencies on the Starter plan ($97 plan) can install agency-level Apps
  • Agencies on the Starter plan ($97 plan) can use majority of agency-level APIs, except Create Sub-account and SaaS APIs which are available only on the $497 plan.
Why is this important?
Today, ~60% of Marketplace Apps are built such that they can be distributed only via Agencies. The current restriction was limiting agencies on the Starter plan from accessing the majority of Marketplace Apps. Hence, we have now removed this restriction.
Load More