Support Inbox

Assign a support conversation

curl -X POST https://api.subscriby.net/v1/support/conversations/$CONVERSATION_ID/assign \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"assigned_to_user_id": "'"$TEAM_USER_ID"'"}'

Hands the thread to a team member. assigned_to_user_id must be present: omitting the key is refused, and sending null is how you clear an assignment. Answers 200 with the thread.

post/v1/support/conversations/{conversation}/assign

Request

  • Base URL: https://api.subscriby.net
  • URL: https://api.subscriby.net/v1/support/conversations/{conversation}/assign
  • Auth: HTTP bearer

Path parameters

conversationstring uuid required

The thread, resolved by the route binder.

Headers

Idempotency-Keystring uuid required

A key unique to this operation, such as a fresh UUID. The same key replays the original 2xx response for 24 hours (with Idempotent-Replay: true), so a retry after a timeout never repeats the write; the same key with a different body is refused with 409.

Request body

assigned_to_user_idstring uuid required

The team member to hand the thread to, by user id. The key must be present: omitting it is refused, while sending null clears the assignment.

Response

The thread, reassigned.

Example response

{
  "data": {
    "id": "9e042b6f-5d81-4c37-a920-7b3e18cf6d45",
    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
    "subscriber_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80",
    "member_name": "Jane Doe",
    "channel": "telegram",
    "status": "open",
    "unread_count": 2,
    "last_message_at": "2026-08-20T10:05:00Z",
    "last_inbound_at": "2026-08-20T10:05:00Z",
    "created_at": "2026-08-20T10:05:00Z",
    "updated_at": "2026-08-20T10:05:00Z"
  }
}

Changes

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