šŸ’” 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.