errors.issues.get

Read an issue with its 14-day hourly counts and tag distribution

GET /errors/api/issues/{issueId}IAM errors:ListIssuesRead

Request syntax

GET /errors/api/issues/{issueId}

Path parameters

  • issueIdRequired

    string

    Constraints: 1-80 chars, /^(\d+|[A-Za-z0-9][A-Za-z0-9-]*-[0-9A-Za-z]+)$/

Response

200 with { issue, project, tags }: `issue` as `list` describes it, its `sparkline` 14 days of hourly counts; `project` the project without keys; `tags` per tag key its total and top 5 values with counts, over the issue’s latest 1000 events. 404 when the issue does not exist, a short id names another project, or you may not read the project’s issues.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow errors:ListIssues on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud errors issues get issueId

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_errors_issues_get.