clickup-data-managerlisted

# ClickUp Data Manager Scripted workspace management: cleanup, enrichment, bulk operations. Uses the REST API directly via curl or Python, not the `cu` CLI (which is for interactive use). ## Auth API tokens are in `.env.local` files, one per workspace: ```bash grep "CLICKUP_API_TOKEN" .env.local # CLICKUP_API_TOKEN_OWNER=pk_... # the personal workspace # CLICKUP_API_TOKEN_TEAM=pk_... # the team workspace ``` **The token decides the workspace.** Using the team token against a personal workspace 401s on objects that plainly exist, which reads as a permission bug rather than as the wrong token. ## API patterns and IDs Request patterns (curl and Python bulk-script), the endpoint map for hierarchy, task and view CRUD and the columns update format are all in [references/api-reference.md](references/api-reference.md). Read it before writing any call. **Deletable views**: only user-created views (IDs like `8cbypq9-XXXXX`). System views (`4-SPACEID-28`, `5-FOLDERID-28`, `6-LISTID-8`) return errors on DELETE. Skip them. ## List descriptions and the pin `PUT /list/{id}` takes **`markdown_content`**, not `content`. Plain `content` is stored verbatim and rendered literally, so `**bold**` reaches the buyer with the asterisks on screen. Both fields read back as the flattened `content`, so a plain-looking readback is not evidence the markdown failed. Open the list. The pin that makes a description show at the top of the board is `settings.is_description_pinned` on the list's *