Skip to main content
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, newest first. Use it to triage a queue, or narrow it to the statuses you care about.

tickets show

Returns one ticket in full, including its description and the agent, customer, group and tags it is associated with.

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.

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.

Required arguments

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

tickets comments list

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

Required arguments

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

tickets comments show

Returns one comment on a ticket.

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.

Required arguments

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

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 gets that agent’s saved signature appended.

Required arguments

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