What we do
Tools
Industries
Department
How we workLet's talk →
Home/ClickUp/ClickUp API
ClickUp

The ClickUp API: Authenticate, Stay Under the Limit, and Keep Webhooks Healthy

ClickUp's REST API (v2) covers tasks, lists, custom fields, comments and time tracking, which is most of what you can do by hand in the app. The parts that trip people up are small: the header has no Bearer for personal tokens, the rate limit depends on the Workspace's plan, and a failing webhook gets suspended without telling anyone.

Your first ClickUp API call

Get a personal token. It starts with pk_ and doesn't expire.

Avatar Settings Apps API Token Generate

Send it raw: Authorization: pk_... with no Bearer, to https://api.clickup.com/api/v2/. OAuth tokens are the exception: those go as Authorization: Bearer ....

Start with GET /team to list the Workspaces the token can see. Their IDs are what most other calls hang off.

Personal token or OAuth app?

Personal token

Your own scripts and internal syncs

  • One click to generate, no app registration.
  • Acts as you, so it sees exactly what your user sees.
  • Doesn't expire. If it leaks, regenerate it from the same screen, which kills the old one.
  • When you leave the company, it stops with your account. Use a dedicated integration user.
OAuth app

Anything other people connect

  • Created by a Workspace owner or admin under Settings, Apps, which gives a client ID and secret.
  • Users authorize at app.clickup.com/api and can pick one or more Workspaces.
  • Swap the code for a token at api.clickup.com/api/v2/oauth/token.
  • Access tokens don't currently expire, but ClickUp says that may change, so handle re-auth anyway.

Internal integration for your own Workspace: personal token on a service user. A tool you'll offer to clients or other teams: OAuth.

ClickUp API rate limits by plan

Limits are per token, set by the plan of the Workspace that hosts the token, and the same for personal and OAuth tokens. Go over and you get HTTP 429.

Workspace plan Requests per minute, per token What it means for a build
Free Forever, Unlimited, Business 100 A full backfill of a big Space will hit this. Page through slowly and cache list and custom field IDs instead of fetching them every run.
Business Plus 1,000 Room for a live two-way sync on most teams, as long as webhooks do the watching instead of polling.
Enterprise 10,000 Rarely the bottleneck. Your receiver and the other system's limits usually are.

Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, the last as a Unix timestamp. Read Remaining and slow down before you hit zero, rather than waiting for the 429. The API itself is included on every plan, Free Forever too; what you pay for with a higher plan is headroom.

ClickUp webhooks: what to build into the receiver

Webhooks can watch a Space, Folder, List or single Task, for named events like taskStatusUpdated or * for everything. These are the rules that decide whether yours keeps running.

  • Verify X-Signature on every request

    It's an HMAC-SHA256 of the raw body with the webhook's secret, in hex. Store the secret when you create the webhook, because that's when you get it.

  • Answer within 7 seconds

    Slower than that counts as a failure. Accept the event, queue it, return 200, then do the work.

  • Expect retries, then silence

    A failed event is retried five times, then dropped, and fail_count goes up by one. At 100 the webhook is suspended. A 401 or 410 suspends it at once.

  • Watch its health yourself

    ClickUp doesn't notify anyone when a webhook goes from active to failing or suspended. Check fail_count on a schedule, and reactivate with PUT /api/v2/webhook/{webhook_id}.

  • De-duplicate on webhook_id and history_item_id

    Retries can deliver the same change twice. Joining the two IDs gives an idempotency key, and the history_items array carries the before and after values.

  • Don't create it as a person who might leave

    A webhook runs on its creator's token. If that user is disabled, the webhook still exists but stops firing.

ClickUp integrations: native, Zapier or the API

ClickUp's own integrations list is strong for communication and dev tools: Slack, GitHub, Gmail and calendars, plus a native HubSpot integration for CRM data and tickets. Accounting is where it thins out. Neither QuickBooks nor Xero is on the list, which is why most teams reach for Zapier or Make first. That's fine for a simple trigger, but task-based pricing climbs with volume and the mapping stays generic.

Building on the API means someone writes the rules: which custom field maps to which account, what happens when a task is reopened after it was billed, and how errors get retried. That's the work n-frames does, for example a sync that rolls logged ClickUp time up per task and hands the finished total to the billing system when the period closes. Before you write code, check whether a built-in ClickUp automation already covers the in-app part.

Questions people ask

Does ClickUp integrate with QuickBooks?

Not through ClickUp's own integrations list, which doesn't include QuickBooks or Xero. The practical routes are a middleware tool like Zapier, the ClickUp REST API, or a custom integration built against both APIs, depending on how much billing logic the sync has to carry.

Is the ClickUp API free to use?

Yes. API access comes with every ClickUp plan, including Free Forever, and isn't billed separately. The rate limit is what changes: 100 requests per minute per token up to Business, 1,000 on Business Plus and 10,000 on Enterprise.

Does ClickUp have a native Slack integration?

Yes. Slack is one of ClickUp's native integrations, used for posting task updates and notifications into channels.

What's the difference between using Zapier and building against the ClickUp API directly?

Zapier is faster to set up for a simple trigger and action, but it's priced per task run and limited to generic field mapping. Building on the API directly costs more up front and handles conditional rules, your own data structure and proper error handling.

Does ClickUp support webhooks?

Yes. You create them through the API on a Space, Folder, List or Task, for specific events or all of them. Each request is a signed JSON POST. Build in signature checks, fast responses and health monitoring, because a failing webhook is suspended without notice.

Who can build and run a ClickUp API integration for us?

n-frames builds them: the sync logic against ClickUp and the other system, a webhook receiver with signature checks, and monitoring that catches a suspended webhook or a run of 429s before your data drifts.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.