GoHighLevel SaaS Config API Guide

GoHighLevel SaaS Configurator API Guide

If you manage SaaS accounts across tools like ClickUp and GoHighLevel, understanding the SaaS Configurator public API endpoints is essential for automating pricing, free trials, and rebills. This guide explains how to use the official SaaS Configurator endpoints so you can integrate them safely into your own workflows and applications.

The information in this tutorial is based strictly on the official GoHighLevel help documentation for public API endpoints used with the SaaS Configurator feature.

What the GoHighLevel SaaS Configurator API Does

The SaaS Configurator area in GoHighLevel allows you to define and manage the subscription structure for your SaaS mode accounts. The public API endpoints exposed for this feature are designed to be used by external systems that need to work with SaaS plans, pricing, and related configuration data.

These endpoints let you:

  • Read information about SaaS plans that have been created in the SaaS Configurator.
  • Retrieve configuration values such as prices, trial days, and rebill details.
  • Use that data in custom dashboards, middleware, or billing automations.

Everything is read-focused: the endpoints are intended to pull data from the SaaS Configurator so you can use it elsewhere in your GoHighLevel-centered ecosystem.

How the GoHighLevel SaaS Configurator API Is Structured

The SaaS Configurator endpoints exist as part of the public API surface for GoHighLevel. Each endpoint is built to return structured data that mirrors what you configure in the SaaS settings inside your account.

In practice, this means:

  • You define your SaaS plans and settings inside the GoHighLevel UI.
  • The API endpoints then expose those plan records and configuration values.
  • Your external app or script calls these endpoints to read the data as needed.

This architecture lets you centralize your SaaS pricing logic in GoHighLevel while still giving external systems access to the same configuration information.

Prerequisites for Using GoHighLevel SaaS API Endpoints

Before you can call these public endpoints successfully, a few conditions must be met inside your GoHighLevel account:

  • You must have SaaS Mode enabled at the agency level.
  • You must have at least one SaaS plan created in the SaaS Configurator.
  • You need valid API credentials and proper authorization to make calls.

Because these endpoints expose billing-related configuration data, access control and authentication are critical. Always keep your API keys secure and follow your organization’s security policy.

Typical Use Cases for GoHighLevel SaaS API

The SaaS Configurator public API endpoints are designed to support a range of automation and integration scenarios. Common use cases include:

Using GoHighLevel SaaS Data in Custom Dashboards

Agencies often want to see SaaS plan details alongside metrics from other systems. By reading SaaS plan data from the API, you can build dashboards that show:

  • Which SaaS plans are available and their current pricing.
  • Trial length and rebill settings for each plan.
  • How plans differ for specific market segments.

Your BI tools or custom admin portal can call the same public endpoints that the GoHighLevel UI relies on.

Syncing GoHighLevel SaaS Plans With External Systems

Another common pattern is syncing SaaS configuration data from GoHighLevel into external billing or provisioning platforms. For example, you might:

  • Pull plan pricing to display on a custom payment page.
  • Use trial and rebill configuration in a separate subscription manager.
  • Align product names and tiers between GoHighLevel and your accounting software.

The public endpoints ensure that external systems read the same configuration that your internal GoHighLevel account uses.

Step-by-Step: How to Work With the SaaS Configurator Public API

While the exact endpoint paths, request formats, and response bodies are defined in the official documentation, you can follow this standard process when working with the SaaS Configurator API.

Step 1: Review the Official GoHighLevel API Documentation

Always begin with the official reference so you are using the most current paths, parameters, and headers. The SaaS Configurator public endpoints and details are documented here:

GoHighLevel SaaS Configurator Public API Endpoints

This reference is the authoritative source for:

  • Endpoint URLs and HTTP methods.
  • Required headers and authentication details.
  • Example request and response structures.

Step 2: Configure SaaS Plans in GoHighLevel

The API simply exposes what is already configured. Before calling any endpoints, make sure you have created or updated plans inside the SaaS Configurator area:

  1. Open your agency-level settings in GoHighLevel.
  2. Navigate to the SaaS Configurator section.
  3. Create or edit SaaS plans, setting values like price, trial days, and included features.
  4. Save your changes to ensure they are available to the API.

Only after these plans exist and are active will they appear in responses from the SaaS Configurator API.

Step 3: Authenticate Your API Requests

To keep your GoHighLevel data secure, all calls to public endpoints must use proper authentication. As outlined in the official documentation, you will typically:

  • Include your API key or token in the request headers.
  • Ensure your token has permission to read SaaS configuration data.
  • Test authentication with a simple read operation before deeper integration.

If authentication fails, you will not be able to access any SaaS Configurator endpoint, even if you have plans set up in your account.

Step 4: Call SaaS Configurator Endpoints

Once authentication is working, you can begin reading data from the SaaS Configurator endpoints as documented. A typical workflow might be:

  1. Send a GET request to the relevant SaaS Configurator endpoint.
  2. Receive a JSON response containing your SaaS plan details.
  3. Parse the response in your application or integration tool.
  4. Map values like price, trial duration, and rebill configuration to your own data model.

Because the SaaS Configurator is central to your SaaS structure in GoHighLevel, your integration should treat this data as the single source of truth for those configuration values.

Best Practices When Integrating GoHighLevel SaaS Data

When building around these public API endpoints, follow these best practices to ensure stability and maintainability.

Cache GoHighLevel SaaS Configuration Where Appropriate

Plan configurations do not typically change minute by minute. To reduce API load and improve performance:

  • Cache responses for a reasonable period (for example, one hour).
  • Refresh cache when you intentionally update SaaS plans inside GoHighLevel.
  • Avoid unnecessary repetitive calls in high-traffic components.

Monitor for Changes in GoHighLevel API Behavior

Because the public endpoints are documented and maintained by the platform, they may evolve over time. You should:

  • Review the official documentation periodically for updates.
  • Implement logging around calls to the SaaS Configurator endpoints.
  • Handle unexpected fields or response changes gracefully in your code.

Where to Get More Help With GoHighLevel API

If you need assistance designing or troubleshooting your SaaS Configurator integration for GoHighLevel, you can work with specialized consultants, developers, or agencies that focus on this platform. For example, you can find implementation support and broader automation strategies at https://consultevo.com.

For the most accurate and detailed technical specifications, always rely on the official GoHighLevel article describing the SaaS Configurator public API endpoints, as it is kept current by the platform team.

Summary

The SaaS Configurator public API endpoints give you structured access to the SaaS plan configuration stored in your GoHighLevel agency account. By reading from these endpoints, you can align external billing pages, dashboards, and integrations with the same configuration that powers your internal SaaS mode setup. Use the official documentation as your primary reference, configure plans carefully inside the platform, secure your authentication, and follow integration best practices to build a stable, scalable workflow around your SaaS stack.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.

Scale GoHighLevel

“`