HighLevel Integration: PIT Token and Location ID
Use this guide to set up your HighLevel Private Integration Token (PIT) and Location ID in CleanQuote so leads, contacts, appointments, and opportunities sync correctly.
1. Where to get the PIT token
- Log in to your HighLevel dashboard.
- For a Location-level PIT (recommended for security):
- Select your sub-account (location) from the account switcher.
- Go to Settings → Integrations → API.
- Click Create new Integration or use an existing one.
- For an Agency-level PIT:
- Go to Settings → Private Integrations (may be under Labs if not visible).
- Click Create new Integration.
- Give the integration a name (e.g., "CleanQuote") and select the required scopes: contacts.write (required), opportunities.readonly, opportunities.write, calendars.write, calendars.readonly, locations.readonly, locations/customFields.readonly, locations/tags.readonly, locations/tags.write, users.readonly (for appointments).
- Copy the token. It typically starts with
ghl_pit_. You won't be able to view it again later, so save it somewhere secure.
2. Where to find the Location ID
- Open the sub-account (location) in your HighLevel dashboard.
- Look at the browser URL. The Location ID is the string after
/location/, for example:https://my.cleanquote.io/v2/location/ve9EPM428h8vShlRW1KT/...→ ve9EPM428h8vShlRW1KT. - You can also find it under Settings → Business Profile or Integrations → API on the location.
3. Where to plug them into CleanQuote
HighLevel is connected once per organization. All tools in that org use the same connection. Per-tool CRM behavior (pipelines, calendars, tags, webhooks) is set in each tool's Settings under the Advanced Configuration card. See the Advanced Configuration guide for details.
- In CleanQuote, go to Dashboard → Settings (org-level menu).
- Find the HighLevel Integration section.
- Paste your PIT token into the API token field.
- Enter your Location ID in the Location ID field.
- Click Save HighLevel connection.
Required scopes
Your PIT token must include at least: contacts.write, opportunities.readonly, opportunities.write, calendars.write, calendars.readonly, users.readonly. Add locations/tags.readonly and locations/tags.write for service area tagging.
Next: Configure per-tool behavior (pipelines, calendars, tags, webhooks, form behavior) in Advanced Configuration.