01Who this is for
- Agency owners can automate client project structures, saving time on repetitive setup.
- Software developers can integrate task workflows into their own tools, extending HighLevel functionality.
02Project management public API, explained
The API provides programmatic access to the full range of project management objects, including spaces, folders, lists, tasks, subtasks and comments. Endpoints let you create, read, update and delete these items, as well as manage permissions and status configurations. It also supports recurring task definitions and the ability for a single task to appear in multiple lists.
The API is reachable via standard HTTP calls and requires a version header of Version: v3. Authentication can be done with a Private Integration Token, OAuth, or an APP channel token, each identifying the subaccount differently. Responses follow JSON format and pagination is available for large result sets.
All calls are limited to subaccounts that have the Project Management Private Beta enabled. The API documentation lists the 45 endpoints across eight groups, along with required parameters and permission scopes for each operation.
03How businesses use the project management public API
- Marketing agency. An agency can use the API to automatically create a Space for each new client, add standard folders and lists, and populate initial tasks. The integration runs when a client onboarding form is submitted, creating the full project hierarchy without manual clicks.
- SaaS product company. A SaaS product can synchronize its internal ticketing system with HighLevel by sending API calls that generate tasks for new support tickets. It can also update task statuses based on ticket resolution events, keeping both systems aligned.
- Consulting firm. A consulting firm can define recurring task definitions via the API for regular deliverables, such as weekly status reports. The API creates the schedule, and the platform automatically generates the tasks at the defined intervals.
04The numbers and rules that matter
- 45 endpoints across 8 API groups.
- Header required for each request: Version: V3.
05Before you start
- The subaccount must be enrolled in the Project Management Private Beta.
- Valid authentication credentials (Private Integration Token, OAuth, or APP channel) are required.
- The integration must be granted permission scopes matching the API actions it will perform.
06How to set up and use the project management public API in HighLevel
Confirm that the subaccount has Private Beta access
- Log into the HighLevel subaccount.
- Navigate to Contacts then Tasks.
- Look for the new Project Management experience in the interface.
- Verify that the subaccount is listed as having Private Beta access.
Create a Private Integration Token for authentication
- Open Settings and select Private Integrations at the appropriate account level.
- Click the Create New Integration button.
- Enter a name and description for the integration.
- Choose the permission scopes needed for the intended API calls.
- Create the integration and copy the generated token securely.
Configure an API request to the Project Management endpoint
- Pick the required endpoint from the Project Management API Documentation.
- Add the authentication credentials to the request.
- Include the header Version: v3.
- Supply any mandatory parameters and ensure the token has the needed scopes.
Test the configured API request for a successful response
- Open the Project Management API Documentation.
- Select an operation, such as retrieving Spaces.
- Follow the documentation’s request instructions for that operation.
- Add the authentication details and the Version: v3 header.
- Send the request using an API client or integration tool.
- Review the response to confirm the request succeeded.
07Settings that matter
- isPrivate. Controls whether a Space, Folder, or List is visible only to specified members.
- userIds. Specifies which users are granted access to a Space, Folder or List; existing members are not removed automatically.
- statusGroup. Identifies the group that marks a task as complete.
- key. Provides a unique identifier for a task status within a Space or List.
- label. Defines the display name shown for a task status.
- parentTaskId. Links a newly created subtask to its parent task.
- Version: v3. Header required on every API request to select the correct API version.
- Private Integration Token. A token that authenticates external applications when calling the API.
08Things to know before you rely on it
- Only subaccounts with Project Management Private Beta enabled can use the API.
- Adding members using userIds does not automatically remove existing access.
- Recurring task schedules use structured options; raw RRULE strings are not accepted.
- Task searches may return subtasks in collapsed, expanded, or separate result formats.
09If something goes wrong
- API request fails. Verify Private Beta access, ensure authentication credentials have the proper permission scopes, and confirm all required parameters and the Version: v3 header are included.
10How it connects to the rest of HighLevel
- Learn how to manage tasks directly within HighLevel Task management
- Set up recurring tasks that run on a schedule Recurring tasks
- Review HighLevel pricing and plan options for API access Pricing
Michael's take

I find that the API offers a way to reduce manual data entry, which can be useful for agencies handling many client projects. However, the need for Private Beta enrollment and token management adds steps that some teams might find extra work.