What the plan decides, and what it doesn't
HighLevel's API article documents standard API access on Starter, Unlimited and Agency Pro, along with both ways to authenticate: OAuth 2.0 and Private Integration Tokens. For many integrations, the plan isn't what stands in the way.
What the plan does decide is a set of restricted endpoints. HighLevel marks Create Sub-Account and Enable SaaS for Sub-Account as Agency Pro restricted. Its changelog for Starter says the same from the other side: Starter can install agency-distributed Marketplace apps, but the Create Sub-account and SaaS APIs are excluded.
The plan isn't the only gate, either. Each endpoint also depends on the scopes and permissions your token or app has been given.
HighLevel has changed this before
API access by plan has moved over time, so a guide or forum answer saying the entry plan has no API may simply be out of date. HighLevel's current article, updated November 2, 2026, says API access comes with every plan. It's the newest source we have, so it's what we go by.
The same article isn't fully consistent with itself. Its table lists OAuth as available on every plan, while its FAQ calls OAuth advanced API access. Until HighLevel settles the wording, test your app's OAuth install on the plan you're actually on before you build on it.
Check the date on anything that tells you which plan has the API.
Pick the plan from your endpoint list
Work from the calls your integration makes, not the features you'd like. A little reading now saves choosing the wrong plan.
- Write down every endpoint your integration will call.
- Look each one up in HighLevel's API documentation and note any plan restriction on it.
- Check the authentication each endpoint accepts, the scopes it needs and its API version. Use the documentation's version switcher, since API v1 reached end of support on December 31, 2025.
- If any endpoint on the list is Agency Pro restricted, such as Create Sub-Account or Enable SaaS for Sub-Account, plan on Agency Pro.
- If none are, the plan won't block you. Scopes and permissions still can, so set them before testing.
- Make one real call per endpoint on your own account before committing to a design.
Mistakes that stop an integration
The common failure looks like this: the token works, most calls succeed, and one endpoint refuses. API access was never the question. That endpoint's restriction or scope was.
- Treating API access on the plan as access to every endpoint
- Building on v1 endpoints after their end of support
- Granting too few scopes and reading the error as a plan problem
- Planning to create sub-accounts or turn on SaaS from a Starter or Unlimited account
- Trusting an old answer about which plan has the API without checking its date
Rather have it set up for you?
We'll check your endpoint list against HighLevel's plan restrictions and scopes, then set up the integration's access. We begin with a 30-minute 1:1 with Rob.