Add clear documentation for which Agency API endpoints require a SaaS Pro plan
S
Scott Heliker
š” Description:
It would be extremely helpful to have a centralized list in the API documentation showing which Agency-level endpoints require a SaaS Pro plan and which do not.
Right now, this requirement is only mentioned on the Create Sub-Account endpoint, but itās also required on related PUT and DELETE requests ā and several User endpoints are mixed between Agency and Location tokens with no SaaS mention at all.
This makes it difficult for developers to know which endpoints are restricted without manually testing every call under a non-SaaS account.
š Suggested Improvement:
Add a dedicated āSaaS Access Requirementsā page in the API docs that lists:
š Endpoints available to all agencies
š Endpoints restricted to SaaS Pro agencies only
Include a āRequires SaaS Planā badge or note at the top of each relevant endpointās documentation page.
š» Developer Value:
This would make it much easier for developers to:
Properly document and label endpoints in external apps (Make, Zapier, custom integrations, etc.)
Avoid wasting time testing endpoints that silently fail for non-SaaS accounts
Keep integrations accurate and up to date with HighLevelās latest API changes
š§  Summary (for short overview field):
Having a clear list of which Agency endpoints require a SaaS plan would save developers time, prevent permission errors, and ensure integrations stay properly documented.
Log In
