I discovered something interesting by exploring the ClickUp API — maybe helpful for others working on Team/Group assignment via API.

What I found

The official ClickUp documentation for Update Task clearly shows support for group_assignees.

However, when I tried to use group_assignees in a Create Task (POST) call, the API responded with 500 Internal Server Error, without any useful error message.

Doing the same operation with a PUT (Update Task) — after creating the task — works fine: the group is correctly assigned and appears in the ClickUp UI.

Example that fails (Create Task with group_assignees)

curl --location --request POST \

'https://api.clickup.com/api/v2/list/<LIST_ID>/task' \

--header 'Authorization: Bearer <TOKEN>' \

--header 'Content-Type: application/json' \

--data '{

"name": "Task via API",

"status": "to do",

"group_assignees": {

"add": [ "<GROUP_ID>" ]

}

}'

→ Result: 500 Internal Server Error

Example that works (Update Task via PUT)

curl --location --request PUT \

'https://api.clickup.com/api/v2/task/<TASK_ID>' \

--header 'Authorization: Bearer <TOKEN>' \

--header 'Content-Type: application/json' \

--data '{

"group_assignees": {

"add": [ "<GROUP_ID>" ]

}

}'

→ Result: 200 OK — group assigned correctly

Conclusion / Warning

The API supports group_assignees, but only via Update Task (PUT) https://developer.clickup.com/reference/updatetask — not on Create Task (POST).

This behavior seems undocumented / unsupported (despite appearing in doc), so it may break anytime.

If you automate task creation + assignment of Teams, a reliable workflow today is: create task first (POST), then run an update (PUT) to assign users/groups.

I see that the https://clickup.com/api/clickupreference/operation/GetTask/ api now includes group_assignees in the json returned. I am still not able to set group_assignees via either https://clickup.com/api/clickupreference/operation/CreateTask/ or https://clickup.com/api/clickupreference/operation/UpdateTask/ though

I'd expect engineering teams to follow the design principle of "API first" ... therefore making an internal API public seems fundamental to me for various use cases (automation, etc)

Please make it work with SCIM to facilitate user management with platforms such as Okta.

+1 on this, Teams should be ubiquitous with users for assignment purposes based on the way this product is marketed, so this is a major shortcoming of the API.

Voting up this feature +1

I'm requiring to create tasks via an integration and add assignees (people and/or teams) but looks like API v2 endpoint lacks of this parameter for teams.

The endpoints for "Tasks" require this urgent update

To support add/rem and retrieve "group_assignees" field just like the web version.

To be explicit, I'd like to have the ability to set the assignee to a User Group using the Create Task and Create Comment endpoints as well as change these using the Update Task and Update Comment endpoints.