ConnectCloud Developers

Move a wrongly assigned entry to another item (desk:write)

POST /api/desk/v1/items/{ref}/entries/{entryId}/move

Module: Desk · operationId: moveItemEntry · Tag: Activity · Auth: access token (Authorization: Bearer <accessToken>)

Parameters

Name In Type Required Description
ref path string yes Item id or number
entryId path string yes

Request body

application/json (required)

  • targetId (string, required)

Example:

{
  "targetId": "#4"
}

Responses

  • 200 Moved (application/json)

Fields of the 200 answer:

  • aiGenerated (boolean): The text was written with AI help
  • authorKind (string): external: a third party who answered an internal mail (the entry is internal) (one of agent, requester, system, ai, rule, external)
  • authorName (string): Name of the author
  • authorRef (string): Login (e-mail) of the author
  • automated (boolean): Written by a rule or service; never counts as a first response
  • body (string): Markdown
  • channel (string): Where the entry came from (one of ui, mail, portal, api)
  • createdAt (string (date-time)): When the entry was written
  • editedAt (string (date-time)): When the entry was last edited
  • id (string): Id of the entry
  • itemId (string): Item the entry belongs to
  • kind (string): comment, email_in, email_out or system
  • mail (object): Mail of email_in and email_out entries: direction, from, to, cc, subject, deliveryState (draft, queued, sent, delivered, deferred, bounced, failed, suppressed), recipientStates, attachments
    • inReplyToEntryId (string): Outgoing mails: the mail entry of the ticket it answers; a draft keeps it when it is saved or sent without inReplyToEntryId
    • includeChain (boolean): Sent mails: whether the earlier mails of the ticket went out below the text
    • mainText (string): Received mails: the text without quoted history, signature, closing and legal footer; missing when nothing was cut or the entry was edited. body stays the full text.
    • thirdParty (boolean): An internal mail to or from third parties (suppliers, …; sent with visibility internal or answering one). An internal mail without it – a customer mail a merge or move hid – still belongs to the customer's thread.
    • trimMethod (string): How mainText was found: rules on the text, or the AI for a long mail (settings.mail.aiTrim) (one of heuristic, ai)
  • mailNote (string): why no mail was sent for a public comment (work_type: the ticket type has the work focus, comments on it are never mailed) (one of no_mailbox, no_recipient, mail_unavailable, work_type)
  • movedFromId (string): Item the entry was moved from
  • visibility (string): internal: only staff see it; public: the requester sees it too (one of internal, public)

Example 200 answer:

{
  "aiGenerated": false,
  "authorKind": "agent",
  "authorName": "Lukas Wimmer",
  "authorRef": "lukas.wimmer@muster-it.example",
  "automated": false,
  "body": "Controller zeigt AP-207 mit ständigen Neustarts (PoE-Budget am Switch im Technikraum 2. OG überschritten). AP-201 läuft stabil.",
  "channel": "ui",
  "createdAt": "2026-11-17T08:40:00Z",
  "id": "1b8c9d0e-2f3a-4b4c-9d6e-8f9a0b1c2d03",
  "itemId": "4a1b2c3d-5e6f-4a7b-8c9d-1e2f3a4b5c01",
  "kind": "comment",
  "visibility": "internal"
}

Example request

curl -X POST 'https://api.mbcom.cloud/api/desk/v1/items/string/entries/string/move' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"targetId":"#4"}'

View as Markdown · Interactive reference · OpenAPI