tickets

Tickets are the central work item in NeetoDesk. For fields and response details, see the API reference.

Sample output on this page is shown as the --json envelope, which is reproducible. Pretty tables depend on your terminal width. See Output formats.

Everywhere a ticket ID is taken, the CLI accepts either the ticket’s UUID or its workspace-scoped number, so neetodesk tickets show 1042 and neetodesk tickets show 0f1e4c9a-6d3b-4f92-8a71-25b0c8d4e6f3 do the same thing. The number is the one shown in the web app, and is usually the easier of the two to type.

tickets list

Lists the tickets you can access. Use it to triage a queue, or narrow it to the statuses you care about with a comma-separated --status.

neetodesk tickets list --status open,pending --page-size 25

Flag	Type	Default	Description
`--page`	`int`	`0`	Page number
`--page-size`	`int`	`0`	Items per page (max 100)
`--status`	`string`		Filter by status (comma-separated, e.g. open,pending)

{
  "data": [
    {
      "id": "0f1e4c9a-6d3b-4f92-8a71-25b0c8d4e6f3",
      "number": 1042,
      "subject": "Refund not received",
      "description": "The card was charged twice on 2 August.",
      "priority": "high",
      "status": "open",
      "category": "Billing",
      "sub_category_one": null,
      "sub_category_two": null,
      "created_at": "2026-08-03T09:14:22.000Z",
      "updated_at": "2026-08-03T11:02:41.000Z",
      "external_id": null,
      "source": null,
      "group": "Payments",
      "tags": ["refund"],
      "assignee": {
        "id": "7b2c1d40-5e6f-4a81-9c23-0d4e5f6a7b8c",
        "name": "Oliver Smith",
        "email": "oliver.smith@example.com"
      },
      "customer": {
        "id": "c4d5e6f7-8a9b-40c1-b2d3-e4f5a6b7c8d9",
        "name": "Sam Smith",
        "email": "customer@example.com",
        "phone_numbers": []
      },
      "fields": []
    }
  ],
  "breadcrumbs": [
    { "label": "Show", "command": "neetodesk tickets show <id>" },
    { "label": "Update", "command": "neetodesk tickets update <id>" }
  ],
  "pagination": {
    "total_records": 137,
    "total_pages": 6,
    "current_page_number": 1,
    "page_size": 25
  }
}

assignee and customer are left out when the ticket has none, and fields lists the custom ticket fields as field_name and field_value pairs.

tickets show

Returns one ticket in full, including its description and the agent, customer, group and tags it is associated with. The record has the same fields as a tickets list entry and sits under a ticket key in data.

neetodesk tickets show 1042

Required arguments

<id> - the ticket’s number or UUID.

tickets create

Opens a ticket on behalf of a customer, identified by their email address. The description becomes the ticket’s first comment. If no customer with that email exists, one is created.

neetodesk tickets create \
  --email customer@example.com \
  --subject "Refund not received" \
  --description "The card was charged twice on 2 August." \
  --priority high \
  --assignee-email oliver.smith@example.com

Flag	Type	Required	Description
`--agent-id`	`string`		Agent ID to assign
`--assignee-email`	`string`		Agent email to assign
`--category`	`string`		Ticket category
`--description`	`string`	Yes	Ticket description
`--email`	`string`	Yes	Customer email
`--group-id`	`string`		Group ID to assign
`--name`	`string`		Customer name
`--priority`	`string`		Ticket priority (low, medium, high, urgent)
`--status`	`string`		Ticket status
`--subject`	`string`	Yes	Ticket subject

The response carries only the new ticket’s identifiers and its URL in the web app. With --quiet just the id is printed.

{
  "data": {
    "ticket": {
      "id": "0f1e4c9a-6d3b-4f92-8a71-25b0c8d4e6f3",
      "number": 1042,
      "url": "https://acme.neetodesk.com/admin/tickets/1042"
    }
  },
  "breadcrumbs": [
    { "label": "Show", "command": "neetodesk tickets show <id>" }
  ]
}

tickets update

Changes a ticket’s subject, description, status, priority, category, assignee or group. Pass only the flags you want to change; the rest are left as they are. The updated ticket comes back in full under a ticket key in data.

neetodesk tickets update 1042 --status resolved --priority low

Required arguments

<id> - the ticket’s number or UUID.

Flag	Type	Description
`--agent-id`	`string`	Agent ID to assign
`--assignee-email`	`string`	Agent email to assign
`--category`	`string`	Ticket category
`--description`	`string`	Ticket description
`--group-id`	`string`	Group ID to assign
`--priority`	`string`	Ticket priority
`--status`	`string`	Ticket status
`--subject`	`string`	Ticket subject

{
  "data": {
    "ticket": {
      "id": "0f1e4c9a-6d3b-4f92-8a71-25b0c8d4e6f3",
      "number": 1042,
      "subject": "Refund not received",
      "description": "The card was charged twice on 2 August.",
      "priority": "low",
      "status": "resolved",
      "category": "Billing",
      "sub_category_one": null,
      "sub_category_two": null,
      "created_at": "2026-08-03T09:14:22.000Z",
      "updated_at": "2026-08-03T11:02:41.000Z",
      "external_id": null,
      "source": null,
      "group": "Payments",
      "tags": ["refund"],
      "assignee": {
        "id": "7b2c1d40-5e6f-4a81-9c23-0d4e5f6a7b8c",
        "name": "Oliver Smith",
        "email": "oliver.smith@example.com"
      },
      "customer": {
        "id": "c4d5e6f7-8a9b-40c1-b2d3-e4f5a6b7c8d9",
        "name": "Sam Smith",
        "email": "customer@example.com",
        "phone_numbers": []
      },
      "fields": []
    }
  }
}

tickets comments list

Lists a ticket’s comments in the order they were added, each with its type, author and body.

neetodesk tickets comments list 1042

Required arguments

<ticket-id> - the ticket’s number or UUID.

Flag	Type	Required	Default	Description
`--page`	`int`		`0`	Page number
`--page-size`	`int`		`0`	Items per page (max 100)

{
  "data": [
    {
      "id": "3a9d7e21-4b8c-4d15-9e73-6f2a1b0c8d94",
      "created_at": "2026-08-03T11:02:41.000Z",
      "comment_type": "reply",
      "content": "<p>We have issued the refund.</p>",
      "author": {
        "id": "7b2c1d40-5e6f-4a81-9c23-0d4e5f6a7b8c",
        "name": "Oliver Smith",
        "email": "oliver.smith@example.com",
        "type": "agent"
      },
      "attachments": []
    }
  ],
  "breadcrumbs": [
    { "label": "Show", "command": "neetodesk tickets comments show 1042 <comment-id>" }
  ],
  "pagination": {
    "total_records": 3,
    "total_pages": 1,
    "current_page_number": 1,
    "page_size": 30
  }
}

A comment the system wrote has an author of type system with no id or email. Each entry in attachments carries the file’s id, filename and url.

tickets comments show

Returns one comment on a ticket, under a comment key in data.

neetodesk tickets comments show 1042 3a9d7e21-4b8c-4d15-9e73-6f2a1b0c8d94

Required arguments

<ticket-id> - the ticket’s number or UUID.
<comment-id> - the comment’s UUID.

tickets comments create

Adds a comment to a ticket. A reply is published on the ticket where the customer reads it; a note stays internal to the workspace. The comment is attributed to you, the signed-in user. The new comment comes back under a comment key in data, and --quiet prints just its id.

neetodesk tickets comments create 1042 \
  --content "<p>We have issued the refund.</p>" \
  --comment-type reply

Required arguments

<ticket-id> - the ticket’s number or UUID.

Flag	Type	Required	Default	Description
`--comment-type`	`string`		`reply`	Comment type: reply or note
`--content`	`string`	Yes		Comment content (HTML)

tickets drafts create

Saves an unsent draft on a ticket, replacing whichever draft the ticket already holds of that type. A reply drafted for an agent, named with --author-email, gets that agent’s saved signature appended.

neetodesk tickets drafts create 1042 \
  --content "<p>Checking with the payments team.</p>" \
  --author-email oliver.smith@example.com

Required arguments

<ticket-id> - the ticket’s number or UUID.

Flag	Type	Required	Default	Description
`--author-email`	`string`			Author agent email
`--comment-type`	`string`		`reply`	Draft type: reply or note
`--content`	`string`	Yes		Draft content (HTML)

{
  "data": {
    "draft": {
      "id": "5e6f7a8b-9c0d-4e1f-a2b3-c4d5e6f7a8b9",
      "comment_type": "reply",
      "created_at": "2026-08-03T11:20:05.000Z",
      "updated_at": "2026-08-03T11:20:05.000Z",
      "content": "<p>Checking with the payments team.</p>"
    }
  }
}

The CLI can write drafts but not read them back.

Getting Started

Commands

tickets list

tickets show

Required arguments

tickets create

tickets update

Required arguments

tickets comments list

Required arguments

tickets comments show

Required arguments

tickets comments create

Required arguments

tickets drafts create

Required arguments

​tickets list

​tickets show

​Required arguments

​tickets create

​tickets update

​Required arguments

​tickets comments list

​Required arguments

​tickets comments show

​Required arguments

​tickets comments create

​Required arguments

​tickets drafts create

​Required arguments

tickets list

tickets show

Required arguments

tickets create

tickets update

Required arguments

tickets comments list

Required arguments

tickets comments show

Required arguments

tickets comments create

Required arguments

tickets drafts create

Required arguments