A Private Integration Token, or PIT, is a static API token you create inside GoHighLevel to let your own scripts and tools call the HighLevel API. It replaced the old API keys. You pick its scopes (which data it can read or write) when you create it, and you can change the scopes later without changing the token. Requests send it as a Bearer token in the Authorization header.
PITs exist at both the agency level and the sub-account level. A sub-account PIT only reaches that one sub-account.
In practice
In the sub-account (or agency) Settings, open Private Integrations and create a new integration (as of October 2026). Name it, choose only the scopes it needs, and copy the token right away. HighLevel shows it once. If you lose it, you rotate it.
HighLevel recommends rotating PITs every 90 days. A normal rotation keeps the old and new tokens working for 7 days so you can update your tools. If a token leaks, use the option to rotate and expire it immediately. Agency owners can restrict which users are allowed to create PITs through roles and permissions.
The trade-off against a marketplace app: a PIT is quick for one sub-account, but connecting fifty clients means fifty tokens to create, store and rotate.
Where it shows up in RGS Tools
RGS Tools accepts a Private Integration Token to connect a single sub-account. To connect every sub-account in an agency at once, you install the marketplace app instead. Either way, the connected sub-accounts then appear in each tool's dropdown.