APIs & Integrations
HighLevel
Overview
Pre-built tooling
Pre-built use-cases
No pre-built use cases yet (time to contribute: <48h)
Not seeing the use case you need? Build your own independently.
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
Setup guide
No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Useful links
Contribute useful links by editing this page
API gotchas
- HighLevel offers two different authorization flows for their users. The
standard
option allows for general OAuth2 authentication, while thehighlevel-white-label
option allows users to generate access tokens, enabling them to white-label the platform. This means users can rebrand the platform with their own branding elements and customize it to match their brand identity - HighLevel enforces rate limits for its public V2 APIs. For more details check HighLevel rate limits.
- When creating an app, there are 2 types of access: Location Level Access (also known as Sub-Account) and Agency Level Access (also known as Company). These access levels provide comprehensive control over location data at either the individual location or agency-wide level.
- The App Type determines the accessibility and visibility of your application. A public app is available for anyone to use and access, while a private app is restricted to a specific group or individuals and is not publicly listed in the marketplace. For more details check profile information
Contribute API gotchas by editing this page