curl --request PUT \
  --url https://{subdomain}.mihu.ai/api/v1/conversations/{uuid}/assign \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user_email": "jane@example.com"
}
'

{
  "success": true,
  "message": "Conversation assigned",
  "data": {
    "uuid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "assigned_to": {
      "name": "Jane Doe",
      "email": "jsmith@example.com"
    }
  }
}

Conversations

Hand a conversation to a specific operator

Names the team member who owns this conversation. The assignee comes back on the conversation object as assigned_to, so the inbox can show who is on it.

When to use it. Escalating to a colleague, handing over at the end of a shift, or claiming a conversation so two operators do not answer the same contact at once. Send user_email: null to release it back to the queue.

What it does not do. Assigning does not move the conversation to another queue, does not change who is allowed to see it, and does not stop the AI — use PUT /conversations/{uuid}/mode for that. It is an ownership marker, not a permission.

Identifying the member. By email, the way members are addressed throughout this API. The address must belong to an existing member of the workspace; an unknown address answers 404 rather than creating anyone.

Who can call it. A workspace API token, or a per-user JWT holding loop.conversations.assign. JWTs only reach conversations in their active queues (404 otherwise).

PUT

api

conversations

{uuid}

assign

curl --request PUT \
  --url https://{subdomain}.mihu.ai/api/v1/conversations/{uuid}/assign \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "user_email": "jane@example.com"
}
'

{
  "success": true,
  "message": "Conversation assigned",
  "data": {
    "uuid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "assigned_to": {
      "name": "Jane Doe",
      "email": "jsmith@example.com"
    }
  }
}

Authorizations

Authorization

string

header

required

Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"

Path Parameters

uuid

string<uuid>

required

Body

application/json

user_email

string<email> | null

required

The member taking the conversation, or null to unassign. The key must be present even when null.

Example:

"jane@example.com"

Response

Conversation assigned or unassigned

success

boolean

Example:

true

message

string

Example:

"Conversation assigned"

data

object

Show child attributes

API Documentation

API Reference

Hand a conversation to a specific operator

Authorizations

Path Parameters

Body

Response