Create Team Views in ClickUp

/ ClickUp / By

Create Team Views in ClickUp via API

Using the ClickUp REST API, you can programmatically create powerful shared Team Views that match your workspace workflows and reporting needs. This how-to guide walks you through each step of the Create Team View endpoint so you can build consistent, reusable views for your entire team.

What the ClickUp Create Team View endpoint does

The Create Team View endpoint lets you define a view configuration and share it at the Team (Workspace) level. Once created, the view becomes available to all members of that team, following the visibility, filters, and layout options you specify.

You can use this endpoint to:

  • Standardize views across departments or clients.
  • Automate creation of reporting dashboards.
  • Deploy default list, board, or calendar views for new workspaces.

The official endpoint reference is documented at ClickUp Create Team View API.

Prerequisites for using the ClickUp API

Before calling the Team View endpoint, make sure you have the following prerequisites in place.

1. ClickUp API token

You need a valid API token associated with your ClickUp workspace. This token is sent in the request header as a bearer token. Treat it like a password and keep it secure.

2. Workspace (Team) ID in ClickUp

The endpoint requires a team_id (also called Workspace ID). You can get this from other API calls or from the URL when you open the workspace in your browser.

3. HTTP client or integration environment

Use one of the following to send your API requests:

  • Command-line tools like curl.
  • API platforms such as Postman or Insomnia.
  • Server-side code in Node.js, Python, or any language that supports HTTPS.

ClickUp endpoint overview

The HTTP method and path for creating a Team View are:

  • Method: POST
  • URL: https://api.clickup.com/api/v2/team/{team_id}/view

Replace {team_id} with the ID of the workspace where you want the view to live.

You must include:

  • Authorization header with your ClickUp API token.
  • Content-Type: application/json header.
  • A valid JSON body describing the view settings.

Required fields when creating a ClickUp Team View

The request body accepts several properties. Some are required, while others are optional depending on your use case.

Core required properties

At a minimum, you generally need:

  • name: The display name of the view, such as Team Board or Weekly Sprint.
  • type: The type of view to create. Typical values include list-style, board-style, and other supported layout types documented in the API reference.
  • grouping or layout options: Settings that determine how tasks are grouped or sorted, depending on the view type.

Because the endpoint is specifically for Team Views, you do not need to associate the view with a folder, list, or space in the body. The team_id in the URL handles that association.

Optional configuration fields

Depending on the view type, you can also specify:

  • Filters: Rules to show or hide tasks by status, assignee, tag, priority, or custom fields.
  • Sorting: Settings to sort by due date, status, or other task attributes.
  • Visibility options: Whether the view is private or shared with everyone in the workspace.
  • View settings: Columns, swimlanes, grouping options, and more, depending on the layout.

Step-by-step: Create a Team View in ClickUp

Use this sequence to configure and send your first request.

Step 1: Define your view goal

Decide what this Team View should help your workspace see. Common goals include:

  • Monitoring all active tasks for the whole organization.
  • Tracking sprint progress across multiple teams.
  • Reviewing backlog items grouped by owner or priority.

Clarifying this goal helps you set the right type, filters, and grouping in your request body.

Step 2: Choose a ClickUp view type

Pick a view layout that matches your objective. For example:

  • A list-style view for detailed task tables.
  • A board-style view for Kanban workflows.
  • Other supported types as documented in the official API.

Set the chosen type in the type property of your JSON body.

Step 3: Build your request body

Create a JSON object that includes your core properties and any optional filters or settings. A simplified structure might look like this:

{
  "name": "Company-wide Board",
  "type": "board",
  "filters": {
    "statuses": ["to do", "in progress", "review"],
    "archived": false
  },
  "grouping": {
    "field": "status"
  }
}

The actual property names and structures must match those listed in the official ClickUp reference page for the endpoint.

Step 4: Send the POST request

Use your preferred tool to send the request. In curl, the pattern is:

curl -X POST 
  "https://api.clickup.com/api/v2/team/{team_id}/view" 
  -H "Authorization: <YOUR_API_TOKEN>" 
  -H "Content-Type: application/json" 
  -d '{
    "name": "Company-wide Board",
    "type": "board"
  }'

Replace {team_id} and <YOUR_API_TOKEN> with live values from your ClickUp workspace, and expand the body to include any advanced configuration you need.

Step 5: Review the ClickUp API response

If the request is successful, the API returns a JSON response describing the new view. It typically includes:

  • The unique ID of the view.
  • The name and type you specified.
  • All persisted settings, such as filters, grouping, and visibility.

Save the view ID if you plan to update or delete this Team View later using other endpoints.

Handling errors from the ClickUp endpoint

Errors usually come from invalid input or authentication issues. Common problems include:

  • Missing or incorrect API token in the Authorization header.
  • An invalid or non-existent team_id value.
  • Supplying unsupported types or malformed JSON in the body.

When you see an error response, check the status code and message, then compare your request body against the documented schema on the official ClickUp reference page.

Best practices for managing Team Views in ClickUp

To keep your workspace organized and performant, consider the following practices.

Standardize naming conventions

Use a clear naming pattern such as Department – Purpose – Layout. For example:

  • Marketing – Campaigns – Board
  • Engineering – Sprints – List

This makes it easier for the entire team to recognize and reuse the right views.

Limit redundant or overlapping views

Before creating a new Team View through the API, check whether a similar view already exists in ClickUp. Too many nearly identical views can clutter your workspace and confuse users.

Use filters to keep views fast and relevant

Design filters so that each Team View shows only what people actually need, such as active work, specific teams, or current sprints. Well-scoped filters keep the interface responsive and easier to navigate.

Automate view creation during onboarding

If you manage multiple workspaces, you can integrate this endpoint into your onboarding scripts. That way, every new workspace in ClickUp automatically gets a consistent set of Team Views tailored to your operations.

Where to learn more about the ClickUp API

For the full schema, supported types, and detailed field descriptions of the Create Team View endpoint, always refer to the official documentation at ClickUp Create Team View reference.

If you want strategic help designing scalable workflows, automation patterns, and API architecture around your workspace, you can also visit Consultevo for professional consulting services.

By following this guide and the official reference, you can reliably create and manage Team Views in ClickUp via the REST API, giving your organization consistent, shared visibility across all its work.

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

“`