Skip to the documentation
API

Assign a thread

Give it to one person who can see it.

PUT/threads/{id}/assignee

Runs the real call on your workspace.

PUT /threads/{id}/assignee

Give it to one person who can see it.

Example

Needs threads:write. assigneeId is a user id from the team of the thread. The person is emailed unless they assigned it to themselves, and "assigneeId": null leaves the thread with nobody, as the DELETE does. Answers with who has the thread now.

curl
curl -X PUT "$OE/threads/thr_7c1e4a90/assignee" -H "$AUTH" -H "Content-Type: application/json" \  -d '{ "assigneeId": "usr_2f9c1d" }'
Response
{  "object": "thread_assignment",  "threadId": "thr_7c1e4a90",  "assignee": {    "object": "team_member",    "id": "usr_2f9c1d",    "name": "Grace Hopper",    "email": "grace@example.com"  },  "assignedBy": {    "object": "team_member",    "id": "usr_8a41be",    "name": "Ada Lovelace",    "email": "ada@example.com"  },  "assignedAt": "2026-10-14T09:12:44.000Z",  "doneBy": null,  "doneAt": null}

Somebody who cannot see the thread is a 422 invalid_parameter on assigneeId, and the thread keeps the person it had.

A key acts for the workspace owner. A key limited to particular addresses or domains reaches only the threads that arrived at them, and any other thread is a 404.

Reference