clickup-api

ClickUp API Proxy

When to Use

• Need to make custom ClickUp API calls not covered by specific skills
• Direct API access required for advanced operations

Usage

CUR="$PWD"
while [ "$CUR" != "/" ] && [ ! -d "$CUR/.agents/skills" ]; do CUR=$(dirname "$CUR"); done
source "$CUR/.agents/skills/_lib/sb_api_call.sh"

sb_api_call POST /api/clickup \
  -H "Content-Type: application/json" \
  -d '{
    "method": "GET",
    "endpoint": "/v2/task/12345",
    "query": {},
    "body": null
  }'

Parameters

• method: HTTP method (GET, POST, PUT, DELETE)
• endpoint: ClickUp API endpoint path, including the version segment:
  • "/v2/task/12345" for API v2 endpoints
  • "/v3/workspaces/{workspace_id}/docs" for API v3 endpoints
  • Paths without a version prefix default to v2 for backward compatibility
• query: Optional query parameters object
• body: Optional request body object

API v2 vs v3

ClickUp's v3 API covers Docs, Chat, Attachments, modern Time Tracking, Move Task, and Audit Logs. Core task/list/folder/space/comment CRUD is v2-only. Note the terminology shift: v2 "team" = v3 "workspace".

Example — v3 move task

sb_api_call POST /api/clickup \
  -H "Content-Type: application/json" \
  -d '{
    "method": "PUT",
    "endpoint": "/v3/workspaces/WORKSPACE_ID/tasks/TASK_ID/home_list/LIST_ID",
    "query": {},
    "body": { "move_custom_fields": true }
  }'

Response

JSON response from ClickUp API or error object with error field.

Post a Comment (use this for triage verdicts / replies)

Always post comments through the dedicated /comment route — NOT a raw POST .../comment proxy call. The host adds the hidden <!-- switchboard --> self-marker so the integration comment loop skips your own comment. The token stays host-side.

sb_api_call POST /comment \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "clickup",
    "id": "<ClickUp Task ID from the plan metadata>",
    "body": "Your comment text here."
  }'