Create Spaces in ClickUp via API

/ ClickUp / By

Create Spaces in ClickUp with the API

The ClickUp API lets you create Spaces programmatically so you can automate workspace setup, standardize structure, and integrate project creation into your own tools.

This how-to guide walks you through the official ClickUp Create Space endpoint, explaining the required headers, URL parameters, and JSON body fields step by step.

Understanding the ClickUp Create Space endpoint

The Create Space endpoint in the ClickUp API allows you to add a new Space to a specific Workspace (also called a Team in the API). You will send a POST request with JSON data that defines the Space name, features, and default settings.

Before you start, you need:

  • A ClickUp account with access to the target Workspace
  • A valid ClickUp API token
  • The Workspace (team) ID where the Space will be created

Prerequisites for using the ClickUp API

To call the Create Space endpoint successfully, prepare these items in advance.

1. Get your ClickUp API token

Sign in to your ClickUp account and navigate to your personal settings to generate or copy your API token. This token must be kept secret, as it authorizes requests on your behalf.

  • Use one token per integration or system where possible.
  • Rotate your token if it is ever exposed.

2. Find your ClickUp Workspace (team) ID

Each Space in ClickUp belongs to a Workspace. The API uses the Workspace ID as a URL path parameter.

You can typically locate your Workspace or team ID by:

  • Using other ClickUp API endpoints that list teams/workspaces.
  • Inspecting API responses from existing integrations.

ClickUp Create Space endpoint details

The Create Space endpoint is a POST request to a ClickUp API URL that includes the team ID.

Request URL format

Use the following pattern when sending a request to create a new Space:

POST https://api.clickup.com/api/v2/team/{team_id}/space

Replace {team_id} with the Workspace ID where you want the Space to be created.

Required headers for ClickUp requests

Include these headers in every Create Space request:

  • Authorization: Your ClickUp API token.
  • Content-Type: application/json.

An example header section might look like this (language-agnostic):

Authorization: <YOUR_CLICKUP_API_TOKEN>
Content-Type: application/json

Building the JSON body for your ClickUp Space

The request body is JSON that defines how your Space behaves in ClickUp. Some fields are required, while others are optional and control settings and features.

Required field: name

You must provide a name for the Space:

{
  "name": "Product Development"
}

Choose a clear, descriptive name that matches how your team uses ClickUp, for example:

  • “Client Projects”
  • “Engineering”
  • “Marketing Campaigns”

Common optional fields for ClickUp Spaces

The Create Space endpoint supports several optional properties. On the source page, some key examples include:

  • multiple_assignees: Allow tasks in the Space to have more than one assignee.
  • features: Enable or disable certain ClickUp features for the Space.
  • private: Set whether the Space is private or visible to the whole Workspace, depending on your plan and permissions.

The exact structure and available options are defined on the official reference page, and you should always verify that against your ClickUp plan and permissions.

Step-by-step: Create a Space in ClickUp via API

Follow these steps to create a Space programmatically using the ClickUp API.

Step 1: Prepare your request data

  1. Identify the Workspace (team) ID where you want to add the Space.
  2. Confirm that your API token has permission to create Spaces in that Workspace.
  3. Decide on the Space name and any optional feature settings you want to apply.

Example minimal JSON body:

{
  "name": "Client Success"
}

Step 2: Construct the ClickUp request

Combine the base URL, team ID, headers, and JSON body into a single HTTP POST request.

Conceptually, your request will include:

  • Method: POST
  • URL: https://api.clickup.com/api/v2/team/{team_id}/space
  • Headers: Authorization and Content-Type
  • Body: JSON with at least a name field

This pattern is identical whether you use cURL, Postman, a backend language, or a no-code integration tool that can call the ClickUp API.

Step 3: Send the request and review the response

After sending the POST request:

  • On success, the ClickUp API returns a JSON object representing the new Space, including its ID and settings.
  • If there is an error, the response will include a status code and message indicating what went wrong, such as missing fields or invalid authorization.

Save the Space ID from the successful response. You will need this ID for additional API operations, such as creating Folders, Lists, or tasks inside the new ClickUp Space.

Managing features in your ClickUp Space

Spaces in ClickUp can have different feature configurations. When you call the Create Space endpoint, you can define which features are enabled or disabled through the JSON body (depending on your plan).

Common configuration patterns include:

  • Disabling features you do not use to keep the interface clean for your team.
  • Enabling advanced items such as time tracking or sprints for development Spaces.
  • Standardizing features across all Spaces when you create them via automation.

Always refer to the official ClickUp developer documentation for the latest list of supported feature flags and their allowed values.

Error handling and best practices for ClickUp automation

When automating Space creation through the ClickUp API, follow these best practices.

Validate ClickUp API responses

Implement checks to validate the response from each Create Space call:

  • Confirm the HTTP status code is successful (for example, 200-level).
  • Verify that the response body includes a Space ID and the correct name.
  • Log errors if the request fails and store the response for troubleshooting.

Protect your ClickUp API token

Never hard-code your ClickUp token in public repositories or client-side code. Instead:

  • Store the token in environment variables or secure secrets storage.
  • Limit who has access to the token.
  • Regenerate the token if there is any suspicion of compromise.

Where to find full ClickUp API details

The official developer documentation is the authoritative source for the Create Space endpoint, all available parameters, and current behavior. Review it regularly to stay aligned with any updates in ClickUp.

You can read the full endpoint specification here: ClickUp Create Space reference.

Next steps and further ClickUp optimization

Once you can create Spaces with the ClickUp API, you can extend your automation by:

  • Creating default Folders and Lists automatically inside each new Space.
  • Applying standardized templates for projects or clients.
  • Integrating ClickUp with your CRM, billing, or onboarding workflows.

If you need help designing a scalable API strategy, automation blueprint, or workspace architecture around ClickUp, you can explore expert consulting services at Consultevo.

By combining the Create Space endpoint with other parts of the ClickUp API, you can build powerful systems that keep your Spaces consistent, reduce manual setup time, and maintain clean structure across every new project or client.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your ClickUp workspace, work with ConsultEvo — trusted ClickUp Solution Partners.

Get Help

“`

Verified by MonsterInsights