How to Get Workspace Seats with the ClickUp API

The ClickUp platform offers an API endpoint that lets you retrieve detailed information about workspace seats so you can track usage, availability, and billing-related data programmatically.

This how-to guide walks you through using the GET /workspaces/{workspace_id}/seats endpoint, explaining the request, parameters, and response fields based strictly on the official API reference.

Understanding the ClickUp workspace seats endpoint

The workspace seats endpoint in ClickUp returns a structured summary of the seats associated with a specific workspace. You can use this data to monitor capacity, check how many paid seats are in use, and review trial details for each plan.

The endpoint you will call is:

GET /workspaces/{workspace_id}/seats

This is a read-only operation that does not change any data. It simply reports the current state of seats across the workspace and its members.

Prerequisites for using the ClickUp API

Before sending requests to the seats endpoint, ensure you have the following items in place:

• A valid ClickUp account with access to the target workspace.
• An API token that authorizes access to that workspace.
• The numeric workspace_id for the workspace whose seats you want to inspect.
• A tool for making HTTP requests, such as curl, Postman, or a programming language with an HTTP client library.

If you need broader implementation or automation help beyond this specific endpoint, you can work with a consulting partner like Consultevo for workflow and integration support.

How to call the ClickUp workspace seats endpoint

Follow these steps to request workspace seat information from the ClickUp API.

Step 1: Build the ClickUp request URL

Start by constructing the full URL for the endpoint. Replace {workspace_id} with the actual workspace identifier.

https://api.clickup.com/api/v2/workspaces/{workspace_id}/seats

For example, if your workspace ID is 123456, your URL would be:

https://api.clickup.com/api/v2/workspaces/123456/seats

Step 2: Add required ClickUp authentication

Authentication is handled using your API token in the request headers. The token must have permission to view the specified workspace.

A typical curl command will look like this (replace YOUR_API_TOKEN and WORKSPACE_ID):

curl -X GET \
  "https://api.clickup.com/api/v2/workspaces/WORKSPACE_ID/seats" \
  -H "Authorization: YOUR_API_TOKEN"

Make sure that:

• The Authorization header is present.
• The token is valid and not expired or revoked.
• The token has access to the workspace you are querying.

Step 3: Send the request to the ClickUp endpoint

After constructing the URL and headers, send the request using your chosen HTTP client. Since this endpoint is a GET request, you do not need a request body.

On success, the ClickUp API responds with a 200 OK status code and a JSON body that contains summary data for the workspace seats and details for each plan.

Interpreting the ClickUp workspace seats response

The response from the workspace seats endpoint consists of high-level summary counts and a list of detailed records for each relevant plan. This section explains the key fields you can expect to see.

Top-level seat summary fields in ClickUp

The object at the top level of the response includes aggregated counts for the entire workspace. Typical fields include:

• total – The total number of seats in the workspace across all included plans.
• occupied – How many of those seats are currently in use by members.
• available – The number of seats that are not yet assigned.
• trial – Information about trial seats, if the workspace has an active trial plan. This can include how many seats are trial seats.

These values help you quickly determine if you are near capacity or if additional members can be added without changing your plan.

Plan-level seat details in ClickUp

Below the top-level summary, the response provides a list of plan details for the workspace. Each entry describes the seat allocation and usage for a specific plan tier.

Typical fields per plan include:

• plan_id – Identifier for the specific plan applied to the seats.
• name – Human-readable name of the plan (for example, Business or Enterprise).
• total_seats – Total seats purchased or allocated for that plan.
• used_seats – Seats currently in use by members on that plan.
• available_seats – Remaining seats that can be assigned without upgrading or purchasing more.
• trial_seats – Trial-specific seat counts when applicable.
• billing_period – Indicates whether the plan is billed monthly, annually, or via another billing cycle when exposed.

Depending on your workspace configuration, some fields may not be present or may be set to null. Always code defensively and check for missing fields when integrating with the response.

Common use cases for the ClickUp seats endpoint

Once you understand the response structure, you can incorporate the seats data into a variety of operational and reporting workflows.

Monitoring ClickUp seat utilization

You can run periodic checks to answer questions like:

• How many total seats does the workspace have?
• How many seats are actually occupied?
• Is there enough capacity for upcoming new hires?
• Are trial seats approaching their limit?

By pulling this data on a schedule, you can create internal dashboards or alerts that notify administrators when the number of available seats drops below a predefined threshold.

Aligning ClickUp billing and provisioning

The seat data from this endpoint also helps finance and operations teams align billing with user provisioning. Sample applications include:

• Comparing purchased seats vs. used seats to identify underutilization.
• Detecting when usage exceeds a given ratio and may justify a plan change.
• Automating processes that request approval before assigning the last available seat.

All of these rely on fresh data from the seats endpoint and can be integrated into internal tools or external billing systems.

Best practices for working with the ClickUp API

When integrating the workspace seats endpoint into your systems, keep these general practices in mind:

• Handle rate limits – Do not poll the endpoint excessively. Cache responses when possible and refresh only as often as needed for your use case.
• Secure API tokens – Store tokens securely using environment variables or a secret manager rather than hard-coding them in source files.
• Validate responses – Check for HTTP status codes and handle error responses gracefully, including 4xx and 5xx codes.
• Plan for schema changes – Implement robust parsing that tolerates new fields or optional fields that may appear or disappear over time.

Where to find the official ClickUp documentation

This tutorial is based strictly on the official reference documentation for the workspace seats endpoint. For the most accurate and up-to-date details, including any new fields or constraints, refer directly to the official docs:

Official ClickUp workspace seats API reference

Use that page alongside this how-to guide while you build, test, and maintain your integrations to ensure your implementation matches the current behavior of the API.

Next steps for your ClickUp integration

With the workspace seats endpoint in place, you can expand your ClickUp integration to include additional operations such as managing members, auditing usage across spaces, or building administration dashboards.

Combine the seats data with other API endpoints to create a complete picture of workspace health, supporting better planning for growth, billing, and compliance.

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

“`