GEgetaptly
Inboxes

Assign or unassign a thread

Assigns the thread to a user, or unassigns it when assigneeId is null. Runs the same assignment the Aptly apps do: the acting user must be able to see the thread, the assignee must be in the company (and in the thread's channel when that channel is shared), the thread's history records the assignment, and the assignee is notified.

The acting user is the delegate token's own user. With an API key or partner token, name one in userId.

If the acting user would lose access to the thread, or it would leave their Mine view, the request answers 409 with code STREAM_LOSE_ACCESS or remove_stream_from_mine_view. Repeat it with force: true to proceed.

post/api/inboxes/{channelId}/threads/{threadId}/assign

Request

Path parameters

channelIdstring required

External channel meta ID (meta.id) of the inbox.

threadIdstring required

Thread id from the threads list.

Request body

assigneeIdstring nullable required

User to assign the thread to, or null to unassign it.

userIdstring

Acting user. Required with an API key or partner token.

forceboolean

Proceed past the two 409 access warnings.

Response

Assigned.

Changes

No recorded changes to this operation across all 1 revision of this API.