remove-ticket-tags

dci remove-ticket-tags ticketId

Removes one or more tags from an existing support request. The operation is surgical — only the tags listed in the request are removed; tags not listed are preserved. Removing a tag that is not present is a successful no-op.

For customers, the system applies the same customer_tag/ namespace mapping as on add, so a customer who added my_tag (stored as customer_tag/my_tag) can remove it by sending my_tag.

Request

Content-Type: application/json

Schema

{
  "type": "object",
  "description": "Request body for adding (POST) or removing (DELETE) tags on a support\nrequest. The operation is surgical — only the tags listed are affected;\nany other tags on the ticket are preserved.\n",
  "required": [
    "tags"
  ],
  "properties": {
    "tags": {
      "type": "array",
      "minItems": 1,
      "maxItems": 50,
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 80
      },
      "description": "List of tags to add or remove. Customer-submitted tags are auto-prefixed with `customer_tag/`."
    }
  }
}

Output

OK - Tags removed (or already absent).

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Field	Type	Description
applied_tags	array of string	The tags that were stored on (POST) or removed from (DELETE) the ticket.

Raw JSON schema

{
  "type": "object",
  "description": "Response body echoing the tags the operation actually acted on, after\nserver-side transformation (trim + lowercase + customer namespace prefix\nwhere applicable).\n",
  "properties": {
    "applied_tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The tags that were stored on (POST) or removed from (DELETE) the ticket."
    }
  }
}

Errors

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP status	Exit code	Error code	Meaning
400	30	VALIDATION_ERROR	The arguments or request body were rejected. Review the command's flags and payload.
401	10	AUTHENTICATION_FAILED	Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
403	11	PERMISSION_DENIED	The DoiT user or the active customer context does not have access.
404	20	RESOURCE_NOT_FOUND	The requested resource does not exist. Check the identifier argument.

Aliases: id-of-ticket-tags-remove