Jonathon's AI Wiki

Testing Draft Marketplace Apps

4 min read

Source: ai-research/ghl-2026-05-01/support-solutions-articles-155000004759-how-do-i-test-my-draft-private-marketplace-app-on-highlevel.md

A short reference covering how to test a draft or private Marketplace app on HighLevel before publishing it publicly. The official support article (last modified 11 Mar 2025) is unusually thin — the page renders breadcrumbs, related articles, and feedback form but no body content describing the testing flow itself. This article preserves what is documented and flags every gap explicitly so developers know when to escalate to the developer Slack or the Marketplace docs portal.

Key Takeaways

  • The article exists in the GHL Developer Resources knowledge base under the path Knowledge base → Developer Resources → Developer Resources → How do I test my draft/private Marketplace app on HighLevel? (last modified 11 Mar 2025).
  • Source body is empty. As captured, the support article does not contain step-by-step testing instructions — only navigation chrome and links to adjacent topics.
  • Adjacent docs in the same folder that may carry the actual testing steps include “How to Get Started with the Developer’s Marketplace,” “Configure Marketplace App Listing Type,” and “Marketplace App Distribution Type.”
  • Distribution type matters for testing. The companion article on Distribution Type (referenced from this page) is the documented control for whether an app is visible only to the developer agency, to specific sub-accounts, or to the public Marketplace.
  • Related cross-links from the GHL portal include “Selling Snapshots on the App Marketplace” and “Usage Based Pricing on App Marketplace,” neither of which document testing.

What the Source Documents

The captured page contains only:

  • Breadcrumb path: Home → Knowledge base → Developer Resources → Developer Resources → How do I test my draft/private Marketplace app on HighLevel?
  • Last-modified date: Tue, 11 Mar, 2025 at 1:48 PM
  • Article-helpfulness feedback widget
  • Links to other articles in the same folder

There is no installable URL pattern, test agency configuration step, or sub-account access flow documented in the page body itself.

Open Questions

The following are NOT answered by the source as captured. Treat as gaps to confirm via the GHL developer Slack, the Marketplace developer portal, or by inspecting the in-product app configuration UI:

  • What is the install URL pattern for a draft app? Does the developer install via a special preview link, the OAuth Authorization URL with the app’s client_id, or a Marketplace-internal “install draft” action?
  • Which sub-accounts can install a draft app? Only the developer’s own sub-accounts? Sub-accounts under the developer agency? Sub-accounts the developer has been explicitly granted access to?
  • How does Distribution Type interact with draft state? Does a “Sub-Account” distribution app behave the same in draft as in published, or is the access model different pre-publish?
  • Are scopes the same in draft as in published? Or do draft apps have a restricted scope surface until approved?
  • How do webhook subscriptions and OAuth callbacks behave in draft? Is there a sandbox URL, or do they hit production endpoints from day one?
  • What is the path from “draft, working in my agency” to “public listing”? Is there a review queue? An approval workflow? A QA checklist required before submission?

For canonical answers, the most likely sources are:

Try It

  1. Open the GHL Marketplace developer portal and create a new app in draft state.
  2. Read the Marketplace App Distribution Type doc to choose the right distribution model for testing (most likely “Sub-Account” or “Agency” rather than public).
  3. Install the draft app into a development sub-account using the OAuth URL bound to the app’s client_id. Confirm the redirect lands on your registered callback.
  4. If install fails or the install URL behavior is unclear, post the question in the GHL developer Slack and link the captured support article so the GHL team can fill the documentation gap.
  5. Once the testing flow works in your draft, document the exact steps internally — the public docs do not currently capture them, so your team’s runbook becomes the canonical reference.

Graph View

Backlinks