get-ticket

dci get-ticket <ticketId>

Returns the details of a single support request by its ID.

• ticketId — The unique identifier of the support request.

Examples

# Show one support request.
dci get-ticket <ticket-id>

# The full record as JSON, including `tags` and `platform_info`.
dci get-ticket <ticket-id> --output json

# Only the fields you need.
dci get-ticket <ticket-id> --fields id,status,severity,tags,urlUI --output json

Output

OK - Support request details returned.

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
id	integer (int64)	Ticket ID.
subject	string	The subject of the ticket.
description	string	The body of the initial ticket message.
requester	string	Email address of the ticket requester.
severity	string	Ticket severity. One of: "low", "normal", "high", "urgent".
platform	string	Platform of the ticket. One of: "doit", "google_cloud_platform", "amazon_web_services", "microsoft_azure".
product	string	Ticket product.
platform_info	string	The cloud asset identifier(s) the requester selected on the support form's asset-selector control — typically the GCP project ID, AWS account ID, Azure subscription ID, or equivalent. May contain multiple identifiers as a comma-separated list (no spaces) when the requester selected more than one asset, e.g. "111111111111,222222222222". Empty string when the ticket has no asset value (e.g. older tickets or tickets opened through paths that bypass the form selector).
status	string	Ticket status.
createTime	integer (int64)	The time when this ticket was created, in milliseconds since the epoch.
updateTime	integer (int64)	The time when this ticket was last updated, in milliseconds since the epoch.
urlUI	string	Link to the ticket in DoiT console.
is_public	boolean	Whether the ticket is public.
tags	array of string	Ticket tags, filtered by caller type. DoiT employee (doer) callers receive the full tag set verbatim, including internal namespaces (e.g. tier/*, synapse_*). Customer callers receive only tags under the customer_tag/ namespace, with that prefix stripped (e.g. a tag added as billing reads back as billing). Always present; empty array when the caller has no visible tags.

Raw JSON schema

{
  "type": "object",
  "description": "Detailed information about a single support ticket.",
  "properties": {
    "id": {
      "type": "integer",
      "description": "Ticket ID.",
      "format": "int64"
    },
    "subject": {
      "type": "string",
      "description": "The subject of the ticket."
    },
    "description": {
      "type": "string",
      "description": "The body of the initial ticket message."
    },
    "requester": {
      "type": "string",
      "description": "Email address of the ticket requester."
    },
    "severity": {
      "type": "string",
      "description": "Ticket severity.",
      "enum": [
        "low",
        "normal",
        "high",
        "urgent"
      ]
    },
    "platform": {
      "type": "string",
      "description": "Platform of the ticket.",
      "enum": [
        "doit",
        "google_cloud_platform",
        "amazon_web_services",
        "microsoft_azure"
      ]
    },
    "product": {
      "type": "string",
      "description": "Ticket product."
    },
    "platform_info": {
      "type": "string",
      "description": "The cloud asset identifier(s) the requester selected on the support\nform's asset-selector control — typically the GCP project ID, AWS\naccount ID, Azure subscription ID, or equivalent. May contain\nmultiple identifiers as a comma-separated list (no spaces) when the\nrequester selected more than one asset, e.g.\n\"111111111111,222222222222\". Empty string when the ticket has no\nasset value (e.g. older tickets or tickets opened through paths that\nbypass the form selector).",
      "example": "cmp-playground"
    },
    "status": {
      "type": "string",
      "description": "Ticket status."
    },
    "createTime": {
      "type": "integer",
      "description": "The time when this ticket was created, in milliseconds since the epoch.",
      "format": "int64"
    },
    "updateTime": {
      "type": "integer",
      "description": "The time when this ticket was last updated, in milliseconds since the epoch.",
      "format": "int64"
    },
    "urlUI": {
      "type": "string",
      "description": "Link to the ticket in DoiT console."
    },
    "is_public": {
      "type": "boolean",
      "description": "Whether the ticket is public."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ticket tags, filtered by caller type. DoiT employee (doer) callers\nreceive the full tag set verbatim, including internal namespaces\n(e.g. `tier/*`, `synapse_*`). Customer callers receive only tags\nunder the `customer_tag/` namespace, with that prefix stripped\n(e.g. a tag added as `billing` reads back as `billing`). Always\npresent; empty array when the caller has no visible tags."
    }
  }
}

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 to exit code mapping

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.
502, 503	40	API_SERVER_ERROR	The API failed to process the request. Retryable; contact DoiT support if it persists.

Related

• list-tickets — List requests
• list-ticket-comments — List request comments
• list-ticket-tags — List tags on a support request
• update-ticket — Update a request
• API reference: GET /support/v1/tickets/{ticketId}

Aliases: id-of-ticket-get