メインコンテンツへスキップ

list-tickets 

dci list-tickets [flags]

Returns a list of all historical requests that your account has access to. Tickets are returned in reverse chronological order by default.

CLI default view

dci list-tickets presents a curated table by default:

  • Columns: subject (a clickable link to the ticket in the DoiT console in interactive terminals), status, severity, and updated (UTC) (from updateTime).
  • In interactive tables, updated (UTC) renders in your local timezone and is titled updated (local); machine formats, agent mode, and --utc keep UTC — see Timestamps and timezones.
  • --output json and explicit -C/--fields selections return the raw fields documented below.

Examples​

# Your most recent support requests, newest first.
dci list-tickets
# Urgent and high-severity tickets only (same key twice is OR; different keys are AND).
dci list-tickets --filter "severity:urgent|severity:high"
# Tickets created on or after 1 August 2026 00:00 UTC (epoch milliseconds), twenty per page.
dci list-tickets --min-creation-time 1785542400000 --max-results 20
# Every page as JSON, for scripts.
dci list-tickets --all --output json

Flags​

FlagTypeDefaultExampleDescription
--max-resultsinteger (int64)100The maximum number of results to return in a single page. Leverage the page tokens to iterate through the entire collection.
--page-tokenstringPage token, returned by a previous call, to request the next page of results
--filterstringAn expression for filtering the results of the request. The syntax is key:[<value>]. e.g: "severity:normal". Multiple filters can be connected using a pipe |. Note that using different keys in the same filter results in “AND,” while using the same key multiple times in the same filter results in “OR”.
--min-creation-timestringMin value for tickets creation time, in milliseconds since the POSIX epoch. If set, only tickets created after or at this timestamp are returned.
--max-creation-timestringMax value for tickets creation time, in milliseconds since the POSIX epoch. If set, only tickets created before or at this timestamp are returned.

Every command also accepts the CLI-wide flags for output shaping — see Output formats and Table output options.

Output​

OK - List of historical requests returned.

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

FieldTypeDescription
pageTokenstringPage token, returned by a previous call, to request the next page of results.
rowCountinteger (int64)Tickets rows count
ticketsarray of object
tickets[].createTimeinteger (int64)The time when this ticket was created, in milliseconds since the epoch.
tickets[].idinteger (int64)Ticket ID (e.g., "33234").
tickets[].is_publicbooleanWhether the ticket is public.
tickets[].platformstringPlatform of the ticket. One of: "doit", "google_cloud_platform", "amazon_web_services", "microsoft_azure".
tickets[].productstringTicket product.
tickets[].requesterstringThe ticket requester in the form of [email protected]
tickets[].severitystringTicket severity.
tickets[].statusstringTicket status.
tickets[].subjectstringThe subject of the ticket.
tickets[].updateTimeinteger (int64)The time when this ticket was last updated, in milliseconds since the epoch.
tickets[].urlUIstringLink to the report in DoiT console.
tickets[].tagsarray of stringTicket 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. Always present; empty array when the caller has no visible tags.
Raw JSON schema
{
  "type": "object",
  "description": "List of support tickets.",
  "properties": {
    "pageToken": {
      "type": "string",
      "description": "Page token, returned by a previous call, to request the next page of results."
    },
    "rowCount": {
      "type": "integer",
      "description": "Tickets rows count",
      "format": "int64"
    },
    "tickets": {
      "type": "array",
      "items": {
        "type": "object",
        "description": "Summary information about a support ticket.",
        "properties": {
          "createTime": {
            "type": "integer",
            "description": "The time when this ticket was created, in milliseconds since the epoch.",
            "format": "int64"
          },
          "id": {
            "type": "integer",
            "description": "Ticket ID (e.g., \"33234\").",
            "format": "int64"
          },
          "is_public": {
            "type": "boolean",
            "description": "Whether the ticket is public."
          },
          "platform": {
            "type": "string",
            "description": "Platform of the ticket.",
            "enum": [
              "doit",
              "google_cloud_platform",
              "amazon_web_services",
              "microsoft_azure"
            ]
          },
          "product": {
            "type": "string",
            "description": "Ticket product."
          },
          "requester": {
            "type": "string",
            "description": "The ticket requester in the form of [email protected]"
          },
          "severity": {
            "type": "string",
            "description": "Ticket severity."
          },
          "status": {
            "type": "string",
            "description": "Ticket status."
          },
          "subject": {
            "type": "string",
            "description": "The subject of the ticket."
          },
          "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 report in DoiT console."
          },
          "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.\nAlways present; 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 statusExit codeError codeMeaning
40030VALIDATION_ERRORThe arguments or request body were rejected. Review the command's flags and payload.
40110AUTHENTICATION_FAILEDNot signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
40311PERMISSION_DENIEDThe DoiT user or the active customer context does not have access.
40420RESOURCE_NOT_FOUNDThe requested resource does not exist. Check the identifier argument.
502, 50340API_SERVER_ERRORThe API failed to process the request. Retryable; contact DoiT support if it persists.

Aliases: id-of-tickets