clickup-apilisted

# clickup-api ClickUp v3 quirks the team has been bitten by. Read before sending any message, creating any channel, or calling any ClickUp endpoint. ## Hard rules (NEVER violate) ### Never create public channels **Forbidden:** `POST /chat/channels` — creates a public channel visible to the entire 50+ person workspace. This has caused real noise/cleanup incidents. **Required pattern:** `POST /chat/channels/direct_message` with `user_ids` — creates a private DM (1 user) or group DM (2+ users). All messaging to teammates routes through DMs, never new public channels. ### Always prefix team-facing messages with 🧞 Any ClickUp message sent to teammates via Claude — DM, group DM, thread reply, or channel post — MUST start with the 🧞 emoji. Lets recipients identify Claude-authored messages at a glance. Applies to all scripts, MCP tools, and direct API calls. No exceptions. ## Endpoint reference ### DM creation - `POST /chat/channels/direct_message` body: `{"user_ids": [<numeric>, ...]}` - 1 user_id → private 1:1 DM - 2+ user_ids → group DM - Returns channel ID — then `POST /chat/channels/{id}/messages` to send. ### Thread replies - Reply to a message: `POST /messages/{message_id}/replies` - **NOT** the channel endpoint. A common mistake is posting back to the channel as a new top-level message instead of as a reply on the thread. ### Channel listing - `GET /chat/channels` — paginated. Use the `cursor` from `next_cursor` field for the next page. `total_count` field returns