> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/guides/app-reference/highlevel.md).

# HighLevel

To connect HighLevel API v2 using a token, create a **Private Integration Token** in the sub-account (location) you want to connect. Private Integration Tokens replace legacy v1 API keys.

{% embed url="<https://marketplace.gohighlevel.com/docs/Authorization/PrivateIntegrationsToken/index.html>" %}

1. Sign in to HighLevel and switch to the sub-account you want to connect to Middle.
2. Go to **Settings → Private Integrations**, under **Other Settings**.
3. Click **Create new Integration**.
4. Name the integration **Middle** and add a description.
5. Select the following scopes to enable all currently implemented Middle HighLevel features:

   | **Scope**                         | **What Middle uses it for**                                                                   |
   | --------------------------------- | --------------------------------------------------------------------------------------------- |
   | `contacts.readonly`               | Look up contacts by email and sync contacts into Middle.                                      |
   | `contacts.write`                  | Create or update contacts, update their custom field values, and add or remove contact tags.  |
   | `locations/customFields.readonly` | Retrieve custom field definitions for syncing and matching field keys when updating contacts. |
6. Create the integration and copy the generated token. HighLevel displays it only once.
7. In Middle’s HighLevel connection, enter the generated token in the “Private Integration Token” field and the matching location ID in “Sub-Account ID,” then save. The legacy “API Key” field is unused by the attached v2 implementation.

{% hint style="info" %}
If **Private Integrations** is missing in HighLevel, ask your administrator to check your permissions and whether the feature needs to be enabled in Labs. [Sub-account setup guide](https://help.leadconnectorhq.com/support/solutions/articles/155000002774-private-integrations-everything-you-need-to-know).
{% endhint %}

{% content-ref url="/pages/12S4me8UzRBzHvDJv3s5" %}
[Contact custom fields](/middle-docs/guides/app-reference/highlevel/contact-custom-fields.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/guides/app-reference/highlevel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.