Public API

ClickUp Chat API v3 Channel Filtering Issue
Issue Summary The ClickUp Chat API v3 endpoint /api/v3/workspaces/{workspace_id}/chat/channels is not respecting the room_types parameter filter when set to CHANNEL. Despite explicitly requesting only channels of type CHANNEL, the API continues to return channels of all types including DM and GROUP_DM. API Endpoint GET https://api.clickup.com/api/v3/workspaces/{workspace_id}/chat/channels Expected Behavior When the room_types parameter is set to CHANNEL, the API should only return channels with type: "CHANNEL". Actual Behavior The API returns channels of all types (CHANNEL, DM, GROUP_DM) regardless of the room_types filter. Example Request GET https://api.clickup.com/api/v3/workspaces/{workspace_id}/chat/channels?room_types=CHANNEL&limit=100&with_comment_since=1234567890000 Headers: Authorization: Bearer {access_token} Content-Type: application/json Example Response (Problematic) The API returns channels with mixed types despite the filter: { "channels": [ {"id": "123", "name": "General", "type": "CHANNEL"}, {"id": "456", "name": "", "type": "DM"}, {"id": "789", "name": "", "type": "GROUP_DM"}, {"id": "101", "name": "Development", "type": "CHANNEL"} ] } Observed channel types returned: ['GROUP_DM', 'CHANNEL', 'DM'] Expected channel types: ['CHANNEL'] only Impact This forces developers to implement client-side filtering after receiving the API response, which: - Wastes bandwidth by returning unwanted data - Defeats the purpose of server-side filtering - May cause pagination issues when most results are filtered out client-side Additional Context - This affects workspace with many direct messages and group DMs - We tested with a workspace containing ~100 channels of mixed types - The filter works correctly for other parameters like limit and with_comment_since - Only the room_types parameter appears to be ignored Request Please investigate why the room_types parameter is not being applied correctly to filter results server-side, or provide documentation if there's a different expected format for this parameter.
0
Load More