Home/HighLevel/Features/App Marketplace/Configure the App Installer Details API in HighLevel

Mobile and Desktop Apps

Configure the App Installer Details API in HighLevel

In short

The App Installer Details API returns verified data about the user who installed a Marketplace app, the subaccount and agency where it lives, and agency white label branding fields. Developers use it to tailor onboarding, UI theme and outreach while avoiding broad company level OAuth scopes.

AreaApp Marketplace · Get Started with App Marketplace
Used forDental practice, Digital marketing agency, SaaS startup
Setup steps6 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Marketplace developers who need to know which user added their app and the agency context for personalized experiences.
  • Agency owners who want to see branding data for their white label installations without exposing it to subaccount clients.

02App installer details API, explained

The endpoint returns the installer’s ID, name and email together with the subaccount ID (if any) and the parent agency ID. It also supplies agency profile fields such as company name, owner name and a set of optional white label attributes like brand name, logo and support URLs. The response is scoped to the token used for the call, either an Agency token or a Subaccount token.

When an Agency token is presented, the API resolves both the installer and the agency, and can indicate the subaccount where the installation occurred. A Subaccount token resolves the installer and the agency that the subaccount belongs to. The call is made via a GET request to the /marketplace/app installer/details path and requires an Authorization header with a Bearer token and a Content Type of application/json. The data can be cached per token/context to minimise calls.

03How businesses use the App Installer Details API

  • Dental practice. The practice adds the installer details call to its onboarding flow. It reads the installer name to address the user and applies the agency’s white label brand name and logo to its dashboard, keeping the UI consistent with the agency’s branding.
  • Digital marketing agency. The agency calls the endpoint from a subaccount workflow to retrieve the agency owner’s contact details. Those details are used to send a welcome email directly to the owner, staying within privacy guidelines.
  • SaaS startup. The startup implements the GET request during app initialization. It caches the white label brand name and primary domain to theme its UI for each client agency and avoids requesting full company level scopes.

04The numbers and rules that matter

  • Response fields include installer.userId, installer.name, installer.email, installationContext.subAccountId, installationContext.agencyId, agency.companyName, agency.companyEmail, agency.ownerName, whiteLabel.brandName, whiteLabel.supportEmail, whiteLabel.supportUrl, whiteLabel.primaryDomain, whiteLabel.logoUrl, whiteLabel.faviconUrl.
  • Rate limiting: 429 responses indicate limit exceeded.
  • Caching recommendation: Cache per token/context, refresh on login or when branding changes.

05Before you start

  • Generate an Agency token and a Subaccount token for testing.
  • Store the tokens securely, for example in a vault or secret manager.

06How to set up and use the App Installer Details API in HighLevel

Set up App Installer Details integration

  1. Create and securely store an Agency token and a Subaccount token for testing.
  2. Add a GET request to the /marketplace/app installer/details endpoint including the Authorization header with the token.
  3. Map the response fields to internal structures and cache the white label data.
  4. Implement error handling for 401, 403, 404, 429 and add exponential backoff retries.
  5. Validate that agency branding is not shown to unintended subaccount audiences.
  6. Add observability metrics for request success, latency and cache hit ratio.

07Settings that matter

  • Authorization. Specifies the Bearer token used for the call, determining whether the response resolves agency or subaccount context.
  • Content Type. Indicates that the request payload (if any) and response are formatted as JSON.

08Things to know before you rely on it

  • Rate limiting may return 429; use exponential backoff with jitter and cache results to reduce call frequency.
  • Cache the installer and white label response per token/context with a short TTL (15 to 60 minutes) to avoid repeated calls.
  • The endpoint is a new Marketplace API and follows standard versioning; consult official docs for Accept Version or URL segment usage.

09If something goes wrong

  • 401 Unauthorized. Refresh the token and ensure the Authorization header follows the Bearer format.
  • 403 Forbidden. Use the appropriate Agency or Subaccount token that has the required privileges.
  • 404 Not found. Prompt the user to install the app or switch to a valid account context.
  • 429 Rate limited. Apply backoff with jitter and rely on cached data where possible.
  • 5xx Server error. Retry the request using exponential backoff.

10How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

The App Installer Details API is a practical way for a tiny agency focused SaaS to look smart without asking for big permissions. It lets you greet the installer by name and match the agency’s colors, keeping the brand intact.

Don’t let the temptation to call the endpoint on every screen drive you into rate limit trouble.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about the App Installer Details API.

Which token should I use, Agency or Subaccount?

Use the token that matches the current execution context. An Agency token resolves agency and installer details and can indicate a subaccount install, while a Subaccount token resolves the installer and its agency.

Does the endpoint require company level OAuth scopes?

No. A key advantage is that you can obtain agency branding without requesting broad company level scopes.

What white label fields are returned?

The response may include brand name, support email and URL, primary domain, logo URL and favicon URL. All fields are optional and should be cached with a short TTL.

Can I cache the response?

Yes. Cache the data per token/context and refresh it when a new session starts or when you detect a change in branding fields.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.